DR Yuill-Kirkwood

It has been left to its self for the past week while I have been away and when I have had signal to check it the wp_options table has averaged around 75Mb, and given the information you gave above in that 1-2 transients for every post, page etc and my measurement of individual _transient_wpsso_ lines come in on average of 7Kb per line so worst case scenario is _transient_wpsso_ would be approximately 62Mb. The wp_options where we reset and cleared transient to start again last week was 1.5Mb and now once rebuild has averaged around 75Mb, so wpsso plus any others plus the 1.5mb could be 75Mb but that still leaves the question of now that wp_options are stable at 75mb why was the entire database stable at 40-45mb for the past several years.

The “Optimize Database after Deleting Revisions” is just another plugin that clears out all or expired transient enters and schedules clearing revisions, however, I have installed the alternative suggested above for testing.

I was tempted to change the “plugin_head_cache_exp\”;i:604800; and other expiry timers to shorten them for an experiment but have not had the time today to analyse WPSSO to see if there are a restore default settings if they have been modified directly.

I have reinstalled/activated WPSSO and will let it accumulate enteritis overnight and see where it lands, wp_Options is 5Mb at this time 01:00, with the entire database at 44Mb.

Since I started this query the wp_oprions have grown a further 15mb leaving me no choice for now but to remove the plugin and it’s extras until a later version can correct the issue.

I run the plugin ‘Optimize Database after Deleting Revisions’ after this returning the the entire database back to 40Mb. It stayed stable at 40Mb for 30 minutes so I reinstalled the plugins, it’s about an hour since then and the database has grown to 50Mb the can’t be cleaned automatically without the re removal of the pkugin indicating that there be something new interacting with the previously noted untouched elements of the plugin in a way unintended and needs correction.

The cache status reads as
WPSSO Core Database Transients
Count Expiration
Article Topics: 1 2592000
Buttons HTML: 1797 604800
Head Markup: 5462 604800
Image URL Info: 18 86400
Schema Data: 1841 1209600
Shortened URLs: 0 7776000
Schema Types: 39 2592000
All Transients: 9210
I have run the Clear all caches twice in the past hour and it’s all still there. I have used your plugin for years with no issue and I am certainly not paying for the privilege of not having my database inflated. This has never been an issue before so something in your update is broken unless in an Apple-style you are using this to force people to go Pro. Can you please explain in precise detail how to clear up and fix your mess, as I have no idea what to do with your wpsso_cache_expire_head_array response.

@edanzer Greetings Space Cadets, I have installed your new version at set my site back to ‘SetEnv DEFAULT_PHP_VERSION 70’ and the galleries are loading fine. Then when I checked the PHP Version Info https://transparent-aluminium.net/info.php my hosting provider has put PHP Version 7.0.25 back on all their servers, so my test is invalid ??

@petert2 in addition for editing the .htaccess file for 123-reg(ular-failure) users, edit the .htaccess file in the directory above the public_html directory not within like there article suggests.

So it could be a month or so on 5.6 before we get the fix.

I was able to get it rolled back to PHP Version 5.6.32 but this is just a temporarily fix.

• This reply was modified 6 years, 12 months ago by DR Yuill-Kirkwood.

I am having the same issue since last night, getting server error 500 or We cannot display this gallery message on pages.
example page: https://transparent-aluminium.net/2015/04/06/newcastle-film-comic-con-2015-cosplay/

Downgrading to 4.6.1 post display correctly, there has to be something weird in 4.7

Greetings Space Cadet, I Don’t have any cashing plugins. Its not the browser I have tried Chrome, IE and Safari, across 3 different machines. I tried switching theme to twenty seventeen and twenty fourteen, still the same. The Subscriber emails are coming out correct. I left my computer taking a back up during the night and I am going to try installing the last version of WordPress and see if it has any effect, hopefully it will not mess up the database.

I’m having this issue with all 6 Publicize systems, twitter, Facebook, LinkedIn etc, just stuck in a loop of Error code: -10520 There was a problem creating your connection. Please go back and try again. and The LinkedIn connection could not be made because no account was selected. (when no option was given to select), I’ve tried disconnecting then from the other sides so as to re-link then and nothing works. I have tried working from both wordpress.com side as well as from my sites admin side and just a constant loop.
if it helps my site is https://transparent-aluminium.net/ and hosted on 123-reg

Greetings Space Cadets, what a catastrophe this update is, it killed my entire site, and any NextGEN albums and galleries pages that did eventually load just gave me an error. The only thing that did load where the Chuck Norris photos, because Norris knows no errors.
I’m so pleased that I had just backed up my entire server the day before, I went strait back the previous version.
Updates in the past where a mission to start with every time I had to unlock it to use more memory to limit thumb creation issues and set the thumb dimensions so all my photos did not appear as a 1 pixel column. Then restore my templates to show photo/album descriptions and album descriptions that didn’t appear as a single line of text the ran off screen.
Doing this every update was a pain but 2.0 where to start I have thousands of images over hundreds of galleries I’m not about to spend weeks adjusting all my pages and posts or spend time working out where everything has been moved to or changed.
As I said I was so pleased I had a backup and could simply just delete 2.0 and dump the old nextGEN plugin files back and all was well again.