v2 conversion issues, db won't update

Yes, we disable to default cron and set up a custom cron to help with site performance. We can reset that for the update.

Please don’t tell me I have too many plugins, that is not your place. Of those plugins, less than 100 are active (others are off and on, as needed), and we use selective script loading functionality to reduce the plugin stack load and any impact on performance.

And it’s not like we’re on shared hosting, so we account for the plugin stack via server and cache settings as well.

Lastly, I don’t have “unnecessary plugins” – if they were unnecessary, they wouldn’t be there. I could just as soon say the five WPGeo Directory plugins were unnecessary. But we want them, so they are necessary, and they are there.

I had already deactivated the WPGD custom plugin I had created for customizations.

I’ll recreate a staging site and run it again. We’ll see what happens.

Thank you for your reply. I appreciate the support we get from WPGD, and that is why I just re-subscribed for another year. But please try not to pontificate in the provision of support. Thanks.

Hey Alex,

I get what you are saying, but my point was I didn’t need someone to tell me I “had too many plugins” and imply some “weren’t necessary” – that wasn’t helpful.

And while I understand that I can run the conversion on staging without other plugins, I need to do this as a test run on staging with all the same plugins that are on the live site so when I try it on the production site I know what to expect.

Interestingly, after I logged out and came back to it the next day, the database conversion was completed.

But I expected it to reset the same pages I had for v1 and reset the same default location, and neither of those things happened.

I thought I had kept up on the blog posts about this conversion, but I may need to go read some more. I’ll continue to leave the live site on v1 until I get a better feel for how all these changes impact my expectations.

Thanks.