Just for anyone else – I’ve rolled back to 10.3.8, same problems, so clearly they’ve applied changes to the actual plugins as well. These arent version based? Next, rollback WP. Aaargh. come on guys.

Your links arent loading Amit. Can you place normal URL’s

Also, it would be really helpful if the update wasn’t full of bugs. We are trying to upgrade templates and none of the images will upload. So fixing the problem is currently impossible.

Hi Vlad. Our web address is Medika.life.

Hi Calum. Thanks for the response. Irrelevant of what the cause may have been people are having huge issues. I can tell you now after days of trying that no amount of optimisation is going to resolve the issue. You have a problem and if Google is responsible for it, that’s a problem you need to address.

In the meantime you have thousands of clients that are freaking out because of their web stats. You guys need to address this. I also see the problem as your old templates are reliant to load on the very scripts that are slowing down the pages.

Not sure how you are going to do this. We are trying to upgrade to a new Pro template but your latest update has broken the image function on the Tagdiv template builder. That’s an issue that needs to be addressed ASAP.

Here’s an indicator of what we are now having to deal with. This page used to rate at 78.

Honestly, I would avoid wasting any more of your time and rather put pressure on tagDiv to sort it out. Until it’s fixed, they are selling an oxcart for a theme, snails could pass it, and they are aware of that. Their entire catalog of older templates that rely on the plugin is effectively useless. You cant use them and if you have, then you have a serious problem. Like we do. Telling us to switch to a Pro theme is an impractical copout.

Be interesting to see how they respond and if they do in fact issue a warning to their new customers about this issue and notify existing customers rather than leave them in the dark and struggling like idiots.

If you’re going to try the rollback I’d only suggest it if you haven’t updated to the latest WordPress. Backup your database and then just rollback. If it bombs, you can often recover by reinstalling the newer version and manually activating the theme plugins from the theme pages.

Fkvs, You can put it on a rocketship, it isn’t going to make the slightest difference, trust me, we have tried pretty much everything. It’s a scripting issue that arose with 10.3.8 and they still haven’t resolved it. It simply kills the page load speed when the page is served and you can minify all you like, move things to the footer, it still sucks.

Some of our pages, the front page included are now taking between 5 and 9s to render, depending on how we optimize. It’s an issue Tagdiv needs to resolve and they’ll have to backtrack to see what they did in the November update that stuffed things up. A solution is possibly trying to roll back to release 10.3.7 but that also now has issues thanks to Woocommerce.

I am also experiencing a massive slow down site-wide since the November update. My site flipped overnight to all our pages failing on Google console, all thanks to the upgrade. This is clearly a development issue on your end guys, please fix it. It’s unfair to expect your customers to resolve this with workarounds and the new update hasn’t addressed it, in fact, it now seems worse.

We have a large site running on Newspaper and we are going to be seriously pissed if we have to take it down to change templates.
How long is this going to take to resolve as it is affecting our rankings on Google and I am sure many of your other customers are wasting time trying to resolve it. Clearly, it’s a known issue you should be advising customers about.
Sorry, but I am seriously pissed off at this point. We have wasted hours trying to optimize code to resolve this. Please let me know when you expect this to be fixed.

The above solution only works if your store’s database has not updated (unlikely). Installing conflicting versions with the store database causes conflicts. In other words, WooCommerce database version: 4.7.0 will only work with WC Version 4.7. You need to have a backup of the store’s older database to roll back to 4.6. Incidentally, I was still on the older version of Newspaper, same issue.

Hi Demi
Thanks but we don’t run a child theme and at the moment we are looking at other themes. The last update they released crashed our WP server and we cannot afford the down time.

So if your megamenu doesn’t work properly can other megamenus be integrated with Newspaper and if so, which are compatible with the theme.

Just in case this got lost yesterday

Thanks for the reply.

Was there a reason you disabled the Ajax Tab on the megamenu options in the composer? This would seem to be the simplest solution, just put the tab back to enable this option if you’ve building a new header using the TD composer.

• This reply was modified 6 years by Robert Turner.

Just to be clear on this, I need to have Ajax load the mega menu contents first rather than after the entire page has loaded.Thanks.

Fixed it by uninstalling WordPress and reinstalling Thanks a lot for the really speedy response

Also just noticed that the Verify theme tab keeps coming back Verified three times now?