Problem with WordPress 4.9.8

Hello ,

May be It’s Conflicting with other plugin. Please try to deactivate all other plugin one by one and then let me know that which one is conflicting with it.

Thanks

yeah – let’s assume I had done all my due diligence already. ??

I even went so far as to install some old backups that were in a working state and traced the error right back to the WordPress update. From all the testing I have done so far it’s 99% safe to say that the issue is between Tabs Responsive and WordPress 4.9.8

Cheers,
Peter

Hi ,

I checked this Tabs Responsive plugin with WordPress 4.9.8 and i didn’t get any error as you said so may be there is some confliction with your theme.So kindly share your Error page URL and send me your theme download link so that i can check error from my side and can provide you solution accordingly .

Thanks

Hi there and thanks.

This seems to be another one of those weird ones.
When I switched themes to twentyseventeen Tabs Responsive started working again. Looks like this a combo of WordPress 4.9.8, Kleo theme and Tabs Responsive. And for some reason the error takes some time to kick in sometimes after the WP update. But once it’s there it persists.

Let’s leave it at this for now. It looks like I might not need the nested tabs after all. I’ll cross that bridge when I really have to.

Thanks again.
Peter

Hi ,

As we discussed earlier its happening due to theme confliction so hope you got your answer.In future if you have any kind of issue regarding this plugin you can ask freely we are always available to solve your issues .If you are satisfied with this plugin services please rate this plugin.

Thanks

Hi,

as we discussed earlier: this is NOT a problem caused by the theme. Everything was working just fine before the latest WP update. This is a problem caused by the newest WP update, which causes a problem between KLEO and Tabs Responsive.

And if you want to take it a little further: this problem is caused by WP core being way too soft with the hardest restriction for extra code being: “oh, btw, please follow our guide lines, that’s a dear”. Which in essence is caused by how the internet unfortunately has changed the thinking from old school programmer to web developers, who unfortunately tend to have a faible for a total disregard of theoretical IT and all the good coding pratices that were developed up in the second half of the last century. Which quite frankly is a step in the wrong direction.
Now it’s: Release quick, release dirty. As long as it runs inside a browser it’s all good. Why bother creating a solid piece of software that is a real tool and not a toy? We can always patch a hole in our code if somebody complains. Which feeds right back into WP being way too soft inside. Perfect circle of coding hell. And the reason why WP runs into a wall when the projects turn out to be more complex. Instead of developing new ideas eventually you end up spending >80% of your time fixing things that are breaking here and there.

And another bane of coding: not being precise on defining a problem. You have no idea how annoying this can be – which is how you got me started on this rant. It’s always about: see, this is not my fault. My code is good.

Sorry. Had to be said.