It sounds plausible that this is a conflict with another plug-in; given that the latest version has been out for 5 days and downloaded around 16,000 times during those five days, if this was a common problem, I probably would have already heard about it.
A white screen means that there’s a fatal error and you have PHP errors configured not to display on screen. If you have any PHP error logs, it would be helpful for me to know what the error was. If not, see if your host can help you set them up so that you can get that information.
Yeah, I since tried deactivating all the plugins so that I could reactivate them one at a time and found that this plugin popped up a message saying WP to Twitter needs to perform an optional database update. It may take a few minutes. Ran the update and it runs out of memory Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 82 bytes) in /var/zpanel/hostdata/zadmin/public_html/lrr_isolary_com/wp-includes/wp-db.php on line 2258 We have a huge db associated with this site. If I were to reinstall the plugin would it still need to go through the database to update it?
We’re upgrading from version 2.8.4 to 3.1.4
You only need to run the update if you’re likely to republish old posts and want to retain the old short URL; the only thing that’s changing in that update is how the old short URL for your posts was stored.
If you have a lot of posts, it should have automatically skipped the update cycle on activation – but I’m guessing that it didn’t for you.
There’s also an option on that screen to dismiss the update if you don’t need it.
I went ahead and reinstalled the plugin, it’s the only plugin running on our dev site and also went ahead and bumped up the max memory of php and the migration script seems to be freezing up or just taking long enough to time out when wpt_migrate_url_meta() is called. From my digging, I understand that that function pulls down all of the posts from the database(why not use the sql server) and then runs through variables to see if they have empty values in the database and if the previous variable was empty it deletes the next variable and then continues until $short is not an empty string or it reaches the end of the script. I don’t quite understand what exactly this script is supposed to do but it is what’s failing with my particular install. Again, like I said before we have a very large number of posts (25,000+ posts ~32MB).
If this loop is necessary I would advise:
- pulling one or a handful of posts at a time (setting a limit)
- clearing the posts from memory after the logic has completed on the post
otherwise you might consider running that logic on the fly.
Again I don’t know your code or how it works I’m just offering what I can see as to what’s going on.
In the next version, I’m actually removing the migration – it’s not a very important migration, and it’s been more trouble than it’s worth. But thanks for the comments.
