peterhsbi

Fair enough ??

But I think we can agree that it is a bit more than just ironic that of all themes I could have tested, I chose Storefront – assuming it to be the gold standard for WooCommerce compatibility – and managing to pull another rabbit out of the hat instead.
I’ll pass it on to Astra. Or – I might actually look into placing that default cookie myself. Should be within reach of my coding-foo. ??

Hi,
thanks for getting back to me so quickly.

I did some more digging – including testing on Storefront theme.

Unfortunately I can’t confirm your evaluation. The unwanted behaviour seems to originate from the missing cookie(s) on page load. After first page load three new cookies get generated when putting an item into the cart. I assume they get modified when deleting the item again. In any case – once the item is empty again the three cookies are still there and the cart behaves like expected and shows a “Cart is empty message” instead of nothing (Storefront theme) or a part of the message border (Astra theme).

So it looks like the answer would be to generate the appropriate cookie(s) on first page load to solve the issue.

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.

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

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 JP,

works a treat. Even better than before. Shariff didn’t show previously on the topics overview page. Always thought that was on purpose.

Cheers ??

Cool ??

That does sound like a plan. Cheers!

Only one problem I need to fix before your solution then. I ended up having to split up buddypress/bbpress and the blog because of bucket loads of plugin incompatabilities and go multisite. And of course bbpress ended up with buddypress on mainsite while the blog ended up on a subsite.
“Broadcast” plugin seems to be the most likely contender to fix that by creating clones of the posts on the respective other site and then use rewrite engine in htaccess to make sure users always get redirected to the original and the clones are only for internal use by widgets and the likes. Only visible draw back at the moment: the bbpress add-on for “Broadcast” is a bit pricy. Bit of a creative mess the whole thing. ??

• This reply was modified 7 years, 5 months ago by peterhsbi.

What can I say.
Apart from sweet and can’t wait ??

Hi there.
I have the same problem. Tabs Responsive is overwriting my theme’s bootstrap files causing problems. At least with the toggled menu.

Are there any updates on that issue?

Cheers,
Peter

Unfortunately there isn’t a free version. I am in contact with Kleo’s developers too. Maybe the two of you could get in touch.

Alternatively: If I set up a testing environment with access to WP admin for you, will that work or do you need access to Kleo’s codes too? Then I need to figure out a way so you can have ftp access too I suppose.