Thank you!

And no…. still messed up

I upgraded my PHP before installing and now the site is broken… going to try and go back to 12.5.1

Has this fix worked for anyone? Everyone? I returned to 11.4.2 so that AIOSEO would work properly.

I have the same issue. This is what AIOSEO wrote me:

Our dev team investigated this further and we found that this error is coming from a plugin called “tagDiv Composer” which is pre-installed with the Newspaper theme from tagDiv.

Their plugin is using Vue in development mode and this is causing issues not only with AIOSEO but with any plugin that uses Vue Router. This seems to be a problem with their latest version and downgrading your theme to an older version should fix the issue.

Please reach out to your theme author (tagDiv) here and let them know that their plugin is breaking your site. They should be able to fix this from their end.

——

I reinstalled version 11.4.2 which works fine until TAGDIV comes up with a fix or update

I went back to 11.4.2 and everything seems to be working ok for me
Hopefully this will be fixed soon

I just received this from AIOSEO

Thanks for reporting this and I’m really sorry that you’re facing this issue.

Our dev team investigated this further and we found that this error is coming from a plugin called “tagDiv Composer” which is pre-installed with the Newspaper theme from tagDiv.

Their plugin is using Vue in development mode and this is causing issues not only with AIOSEO but with any plugin that uses Vue Router. This seems to be a problem with their latest version and downgrading your theme to an older version should fix the issue.

Please reach out to your theme author (tagDiv) here and let them know that their plugin is breaking your site. They should be able to fix this from their end.

In the meanwhile, we are trying to figure out a workaround for this so that it can be avoided in our future releases.

I’d like to assure you that this is not something caused by AIOSEO or something that can be fixed from our end, but it’s definitely affecting our plugin and breaking your site.

Let us know if their developers have any questions for our engineering team and we would be able to connect them.

The update deleted the prebuilt theme we were using as well. You can see the screenshots of my before and after above.

I reverted back to 3.9.1 Hopefully this gets fixed soon… very excited to try the new version especially with the CSS Analyzer Tool

Site with 10.4 and default prebuilt theme
https://opticaljournal.com/Newspaper/Newspaper-10.4b.jpg

Site as restored with backup to 10.3.9.1
https://opticaljournal.com/Newspaper/restored29Mar21b.jpg

• This reply was modified 5 years by dnf67.

The update broke my site BIG TIME. The prebuilt theme was gone as were all the tweaks made to the layout. The iframe code we use for advertising blocks in the widgets was gone. Out logos were gone.

I was able to restore the website back to yesterday’s backup…

Thank you for your reply. So we cannot change the order of what stories appear in what blocks?

I would love to be able to adjust the width of my page. In the boxed format, things run off into the margins. I would love to be able to add another 60 pixels or so

it would be nice have the option to set a floor across the board, such as 100 on every post…

thank you all… embarrassing Tuesday afternoon madness

You must have missed the sentence where I said I reverted to a backup version of the website. I am using 9.1 where you screenshot, not 9.2.2. 9.2.2 killed all my feature images. I did not want a broken site while you folks were on holiday.

I updated to 9.2.2 last week thinking the week between Christmas and New Years was a good time to do this sort of work. Upon installing 9.2.2 all of the feature images disappeared on the front page. They were of course where they were when you opened the individual post, but not under any category index or on the front page layout. I commented on someone else’s post about having the same issue they were but noticed you folks were taking a well deserved holiday, so I reverted to the backup from the night before as I didn’t want to have a broken looking site for a week. I tried turning off plugins to no avail. I also cleared the SiteGround cache to no avail. How do we correct this issue and will it be better addressed in the next release, or???

Thank you!

Two sites (two licenses… only one was changed and changed back)

https://opticalvisionresources.com/ (changed)
https://theopticalvisionsite.com/

Thanks again

I just updated and have the same issue
https://opticalvisionresources.com/

watching… excited to upgrade, but will hold off for a few days

Do we have to delete WPBakery with the new update? It’s not that I love it, I am just used to it and use it with so many other sites. I have found it easy to build pages here with it.

Thank you Bogan. We write the content for both sites. As I mentioned, they are sister sites. I just thought it might be fun to help build traffic between them. I appreciate your answer and will look for other ways of possibly making it happen.

Almost all of my other websites use Visual Composer. It is what I am used to and most comfortable with. I use both TagDiv and Visual Composer simultaneously and make any changes in layout in VC.

“Good news everyone” says, Professor Farnsworth…Being a bit frustrated with my recent update experiences I decided I would go back to version 8.6, so I reuploaded the older version via FTP and the older version of TagDiv composer as well. The issues with the wp_booster errors continued to exist, so I figured I might as well have them with the newest version of the theme instead of an older one. I reuploaded 8.7.2 and TD Composer 2.1 and everything seems to be working OK.

I am still holding off upgrading on my other website until I am convinced everything works smoothly as it should

Cross your fingers…

With trepidation this morning I uploaded the newest version (8.7.2), cleared the cache and turned on TagDiv Composer without breaking the site… YAY! However, when I went in to create a post, got nothing in the entry field until I turned TagDiv Composer back off. Major Bummer… I thought it was all fixed, but alas… no. And without TagDiv Composer turned on, I am back to getting wp_booster errors… This sucks 🙁

• This reply was modified 8 years by dnf67.

I too upgraded to 8.7. I use both WP Bakery and TD Composer. The site worked fine from the front end, but the entire dashboard was gone… nothing but a white screen. Only by deactivating TD-Composer were we able to get into the back end of the website.