Extension talk:InteractiveTimeline

Fatal error: Call to undefined method ParserOutput::addJSConfigVars
I've installed this Extension. And the installation went well.

Than when i put in a page the code:

I received an error like this:

"Fatal error: Call to undefined method ParserOutput::addJSConfigVars in /home/dicki/public_html/dickipedia/extensions/InteractiveTimeline/InteractiveTimeline.body.php on line 390"

Any suggestion?

Hope to hear from you. — Preceding unsigned comment added by Dicki smits (talk • contribs) 17:01, 12 August 2014‎ (UTC)
 * What version of MediaWiki are you on? Jackmcbarn (talk) 17:25, 12 August 2014 (UTC)
 * Pull the latest version, and tell me if that fixes it. PHP function calls are case insensitive (but I should have spotted that case error anyway). I've corrected the case, so hopefully that'll do the job for you; thanks for reporting it! --Ishtralimnar (talk) 18:33, 12 August 2014 (UTC)

I am having similar problem after the fix:

PHP Fatal error: Call to undefined method ParserOutput::addJSConfigVars in /data/mediawiki-installation/mediawiki-1.22.6/extensions/InteractiveTimeline/InteractiveTimeline.body.php on line 390
 * You appear to be running MediaWiki 1.22.6. The addJsConfigVars function was only added to ParserOutput in 1.23, so that call will fail on MW<1.23. I will look into whether it can be made to work with 1.22.x --Ishtralimnar (talk) 13:34, 9 September 2014 (UTC)
 * I have just created a new testing branch that should (in theory) work with the 1.22.x versions of MediaWiki. Please try the following:

and tell me if it fixes the problem for you. --Ishtralimnar (talk) 20:59, 9 September 2014 (UTC)


 * Ishtralimnar, 1.22.x branch appears to render timelines correctly now but the version page is being cutoff after showing the example timeline, only about half of my extensions show on that page with InteractiveTimeline enabled. --Shillmeyer (talk) 22:57, 15 October 2014 (UTC)
 * I've pushed out a slight change that should fix that, please update and tell me if it works for you. --Ishtralimnar (talk) 00:49, 16 October 2014 (UTC)

Parameters "min" and "max" not working in this extension
Firstly, big thanks for this useful extension! Very nice and clear view. Now i made little additions for own purposes: support "group" and "className" in event fields. But can't doing with endless moving in past and future dates :( 'min' and 'max' options not working instead on original examples. I'm played with any datetime format in this options too. What's wrong? Help, please!

Issue
I'm create this issue in extension's github repo with more details.
 * I've updated the git repository with v1.2 that incorporates the fix for the Date options, and rolls the 1.22 compatibility fixes into master so there should be no need to use the REL122_COMPAT branch anymore. --Ishtralimnar (talk) 23:35, 19 January 2015 (UTC)

Don't working on 1.28
Hi, I'm trying to install this extension but every time I get an error: --Azot944 (talk) 00:35, 4 January 2017 (UTC)
 * Thanks for the heads-up, I'll look into it as soon as I can - possibly tomorrow. --Ishtralimnar (talk) 00:43, 4 January 2017 (UTC)
 * I'm unable to replicate this with the 1.28 stable release. Please can you confirm that you've explicitly checked out the 1.27 or 1.28 branch and initialised the submodule (`git checkout REL1_28 && git submodule update --init`)? The error behaviour you describe above could be caused by missing the CHAP Timeline library --Ishtralimnar (talk) 13:00, 4 January 2017 (UTC)
 * Thank you for your response :) I'm using shared hosting provider and I don't have no possibility to use command line. But I have instaled this extension on local server (XAMPP) and I have still this error. Although sometimes it works. Here (https://justpaste(dot)it/1252n) u have error log from browser console and git commands. Example --Azot944 (talk) 16:48, 6 January 2017 (UTC)
 * Sorry about the delay in replying! Okay, yeah, under shared hosting with no command line, this'll be trickier. I've created a zip file for you to try available here: https://www.starforge.co.uk/media/InteractiveTimeline.zip [14MB] That file includes both the extension and the chap-links-library dependency set up for you. Download that, unpack it, and then upload the InteractiveTimeline directory to your extension/ directory on your hoster. Then put  at the end of your LocalSettings.php and in theory it should work. --Ishtralimnar (talk) 13:57, 12 January 2017 (UTC)
 * Still the same errors in browser console :( --Azot944 (talk) 17:02, 12 January 2017 (UTC)
 * I finally managed to replicate this on a live system and worked out what was probably causing it - if you're still interested in using this extension, please give it a try now. Sorry it has taken me so long! --Ishtralimnar (talk) 12:10, 26 April 2017 (UTC)

Styling timeline
Hi there, is it possible to add style to the bars (at least color) and differenciate bars from points? Thank you. --Gborgonovo (talk) 10:03, 23 June 2017 (UTC)
 * The overall style of the Timeline elements is determined by the CHAP Timeline library itself, but it does provide some styling ability (see here); I'll look at adding a facility to add extra style settings to the extension tag, and see what I can get to work. I can definitely extend the event definition syntax to let you explicitly select "box", "range", "dot", or "floatingRange" for each event, too.


 * As a short-term thing, note you can include html and wiki text in your events, so you can do some limited styling inside the markers at the moment:
 * --Ishtralimnar (talk) 10:38, 23 June 2017 (UTC)
 * --Ishtralimnar (talk) 10:38, 23 June 2017 (UTC)

BC
How to mark years BC? I try for example "-0600-01-01" (for 600 year B.C.), but it don't work. --46.211.119.238 17:53, 1 March 2019 (UTC)
 * In theory, as the extension uses javascript's Date constructor to convert from ISO8601 to a date object, you could try using "-000600-01-01" (apparently the parser allows BC dates if you use two extra leading zeros) but the ISO8601 validator code I include in the InteractiveTimeline.body.php will prevent negatives getting through.


 * I should be able to make the validator detect negative dates, and add the appropriate padding zeros for you. However, I'd expect this to cause problems - everything I've found so far while looking this up has noted that date calculations that far back are going to be wrong. I'll keep digging, and I need to upgrade this extension to use the improved vis.js timeline anyway, so I will look to see whether there's a better alternative. --Ishtralimnar (talk) 20:35, 1 March 2019 (UTC)