Plugin Contributor
alexgso
(@alexgso)
Hi Mike,
Can you please clarify what you’re using to downgrade and upgrade WordPress? I ask because there are no known issues like the one you’ve described so I suspect the plugin/upgrade system you’re using is indirectly causing this issue.
Thread Starter
Mike
(@mike-nl)
Hi Alex,
The first time we discovered it was after a regular WP upgrade on one of the production sites. The regular upgrade functionality within WordPress is just fine.
The WP setups after that were done with 3 plugins incl. https://wordpress.org/plugins/wp-downgrade. WP downgrade is a beauty that never caused any issue.
-
This reply was modified 4 years, 3 months ago by
Mike.
-
This reply was modified 4 years, 3 months ago by
Mike.
Hi Mike
Thanks for providing further details. Wouldn’t this be a support topic for WP Downgrade? We’ve never had an issue of Page Builder being deactivated during standard WordPress core updates. WP Downgrade isn’t a core method of updating and when run, one of your plugins, Page Builder, isn’t being reactivated. The action causing this is being run from WP Downgrade.
Hi again Mike
I’ve setup a new instance of WordPress using 4.9.3, installed:
Page Builder by SiteOrigin
SiteOrigin Widgets Bundle
Black Studio TinyMCE
WP Downgrade
I’ve set my WP Downgrade WordPress Target Version to 4.9.4 and upgraded via Dashboard > Updates to 4.9.4. All of my plugins mentioned above are activated after the core upgrade to the WordPress Target Version.
I would imagine something else, besides specifically Page Builder is the issue, are you running this using a cron job for example? If you aren’t, it’s worth reaching out to the author of WP Downgrade to see if he has any ideas.
I’d be more than happy to log an issue report on GitHub and deploy resources on this but we’d need something actionable to work on.
Thread Starter
Mike
(@mike-nl)
Hi,
Just returned from a big business trip-
And first, thanks. Our explanations are accurate. We are rescheduling our planning and resources, but this is a topic that requires dedicated attention from everyone including WP and WP Downgrade.
Ciao
-
This reply was modified 4 years, 3 months ago by
Mike.
Unfortunately I don’t have anything new to offer from my last reply. We’re currently unable to recreate the issue you’re describing. If you have a distinct error or warning we can investigate, I’d be happy to log a bug report.
Thread Starter
Mike
(@mike-nl)
just do what we did the first time
install a clean instance with an old WP including your plugin
upgrade WP the standard way
done
-
This reply was modified 4 years, 1 month ago by
Mike.
Plugin Contributor
alexgso
(@alexgso)
Hi mike-nl,
I have just attempted that and was unable to replicate this issue. I feel like this could be a server specific issue you’re facing.