Timeline disappeared after Update to WP 4.6

Hey Frank,

I am taking a look into the issue. Let me get back to you when I can find some additional information.

Thanks,
Evan

I’m also experiencing the same issue.

Timeline disappeared after Update to WP 4.6

Please help!

Please paste your servers error log here for inspection. I also need a link to your site where you are having issue.

I have not encountered this issue on any of the installs I have the plugin running on, so I don’t know why this would be happening. As you can see, on our documentation site – things have been running smoothly

https://www.wp-timelineexpress.com/examples/post-types-add-on/
https://www.wp-timelineexpress.com/examples/basic-timeline/

I would recommend trying to go through the following debug steps, and reporting back here with your findings:

1) Switch themes to a default bundled, and updated theme (TwentySixteen works). Once activated, re-test. If you are still facing issues move on to step 2.

2) Debug ALL of your plugins (with the default TwentySixteen theme active), except for Timeline Express. Re-test.

Generally speaking, one of those two steps will at least help narrow the issue down to a plugin or a theme.

Finally, can you share your setup and how you are using the plugin? I will need to see if I can replicate things, to figure out how to patch them. The more details you can provide us the better.

Thank you,
Evan

Thank you for taking care, Evan.

You can find the page where the timeline doesn’t show up (even if it’s in the HTML source) at https://www.tvm-capital.com/about-us/

The Chrome and Safari consoles are reporting a “RangeError: Maximum call stack size exceeded.”, suggesting a conflict between jQuery and timeline-express.min.js

Pointing to jQuery on line 48:

camelCase: function(a) {
            return a.replace(p, "ms-").replace(q, r)
        },

I’ve to admit that my JavaScript knowledge is too limited to debug recursive calls.

I’ve replicated the website on a different server with a fresh WP install with the same custom child theme and plugins and settings – and the timline works there. Weird.

I am having exactly the same issue. The page containing the short code displays a very very long and blank. The console shows the error reported above. I’ll post any further diagnostic information I find. My site is fairly old and has been upgraded periodically as wordpress and plugins have.

Installed on WP4.6.
Adding a bunch of items was a pain. (Do you even try it to use in a real world?)
Then it worked for an hour.
I tried to style it a bit (FAQ) and now I having the same issue.
Putting changes back did not help.
“Maximum call stack size exceeded” in js console.
There’s no php errors on server’s side.

“Maximum call stack size exceeded” in js console – means that there was a javascript error somewhere.

It’s possible that it’s an issue with the new collision detection.

I am taking a look into things. I have not encountered this issue, so it’s hard for me to pin point exactly where it’s coming from. Having access to a site with the issue would make it much easier to debug and patch things up.

Thanks,
Evan

Hi Evan,

I followed the instructions on debugging JavaScript errors described at https://codex.www.ads-software.com/Using_Your_Browser_to_Diagnose_JavaScript_Errors using firefox to reveal a ‘too much recursion’ error.

The text of the error is …

JQMIGRATE: Migrate is installed with logging active, version 1.4.1 jquery-migrate.js:23:2
JQMIGRATE: jQuery.fn.load() is deprecated jquery-migrate.js:45:4
console.trace(): jquery-migrate.js:47
migrateWarn() jquery-migrate.js:47
jQuery.fn[name]() jquery-migrate.js:560
<anonymous> frontend.js:115

too much recursion
fa()
jquery.js:2
jQuery.find()
jquery-migrate.js:290
.find()
jquery.js:2
jQuery.fn.find()
jquery-migrate.js:677
n.fn.init()
jquery.js:2
jQuery.fn.init()
jquery-migrate.js:241
n()
jquery.js:2
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
.each()
jquery.js:2
n.prototype.each()
jquery.js:2
check_collisions()
timeline-express.min.js:1
check_collisions/<()
timeline-express.min.js:1
jquery.js:2:6868

I found a solution for my two installations: In the plugin settings: “Date visibility” should be set to “Visible” otherwise it will not only hide the date next to the icon but the whole timline. Seems to be a bug.

Hope this helps.

Thanks Frank, that fix did not work on my site.

Its a problem with your plugin, its a javascript error:

“Uncaught RangeError: Maximum call stack size exceeded”

Please fix.

I cannot replicate the issue on my end. As stated in a previous response, that’s something that will need to happen before I can fix anything. The plugin is working on my end with TwentySixteen. I am not running into recursion problems. It would also be helpful if you can share a link to your site where you are having issues.

Thank you,
Evan

In the previous release I added a check for collision detection so the containers will fall closer together on the timeline, instead of having such large gaps.

There is a recursive function that adds a top margin to overlapping containers and re-checks. It sounds like the containers are not being altered properly, and the recursion is continually running.

When I have overlapping containers, I am not running into that issue- as the containers are properly adjusted in the timeline, and things are initialized.

How many announcements do you have on your site? That would probably help narrow it down.

Thank you,
Evan

Hi Evan,

my site only has 5 announcements.

I’ve sent you the link to the page via your web site contact form.

Thanks

I’m just going to chime in here too – same issue as above, and same workaround worked for me – making the dates visible again makes everything come back. I’ll add custom CSS to remove the dates for now, as I don’t want them showing.