|
Susan McLean
|
September 6, 2014 at 8:08 pm
So I just looked over this thread https://eventespresso.com/topic/wp_options-table-overloaded-by-event-espresso-more-than-300k-lines/ that had the exact same problem my client’s site is having (they also use the Shopp plugin). My client’s site is running EEv 3.1.36.5.P and WP version 3.9.2. What I’m trying to understand is why would Christian say it’s the Shopp plugin doing this when it clearly says in the “Option Value” field content such as “espresso_session|a:3:{s:2:”id”;s:50:”f8v91446dul9ln6mj8f1lur141-540bb99fcc5321.61079308″;s:17:”events_in_session”;s:0:””;s:11:”grand_total”;s:0:””;}”. Is Event Expresso not inserting these rows in the wp_options table? Why would Shopp use the words “espresso” in their value information. Also, I’ve noticed that if I refresh my db view, the number of row count for the wp_options table continues to go up so it acts like it might be a process that is stuck and can’t terminate itself.
Please let me know if you need anymore information to help solve this mystery. I wanted to attach a screenshot of the wp_options table, but could not find out how to do that for this ticket.
|
|
Nasa
|
September 6, 2014 at 9:57 pm
I’m seeing the same thing. I don’t have Shopp installed.
|
|
Dean
|
September 8, 2014 at 4:54 am
Hi,
What Christian and Josh are discussing is that Shopp (at least the version he was using at that point), was saving ALL session data to the options table, regardless of whether that session data was from Shopp or a different plugin.
What should be happening is Shopp saves its own data and ignores other plugins session data.
Is your version of Shopp up to date?
I have no idea if Shopp resolved this issue or not as their changelog doesn’t list changes in 1.3.5, but if you are running an older version then its worthwhile updating.
@Nasa, If you aren’t running Shopp then it is possible that another plugin is doing something similar.
|
|
Susan McLean
|
September 10, 2014 at 12:40 pm
I did just now update the Shopp plugin to 1.3.5 which is their latest and just came out last week sometime. I just flushed the wp_options table which had built up over 78K rows since late last week (it’s back down to about 688 rows). The rows I flushed all had this prefix to it php_session. I will monitor the table for the next few days to see if anymore of these particular rows are appended to the table. What action do you suggest if they do continue to be appended to the table? It seems to me that it has to be EE related (since the value for each row generally either has a number or expresso_sessionla:3:{s:2:”id”;s:50: etc etc}), but I guess I could be wrong.
|
|
Josh
|
September 10, 2014 at 1:03 pm
Hi Susan,
It is related to EE in that EE starts a session (which is necessary for the registration process), but nowhere in Event Espresso 3’s code does it tell WP to record the session in the options table.
That’s where Shopp comes in. You’ll find a function in Shopp’s core/library/Session.php file that tells WP to make a new record in the options table for every time a session gets started, regardless of which plugin starts the session.
Since the session is started by Event Espresso, its name is in the session, but again, Event Espresso 3 does not initiate recording the session in the options table.
I just checked and can verify that the current version of Shopp still records the session variables into the wp_options table. Looking over the changeset in the latest version, it looks like they’ve made a few tweaks to how it records these, and also how it deletes them:
https://plugins.trac.wordpress.org/changeset/970959/shopp/trunk/core/library/Session.php
The changelog for version 1.3.5 of Shopp has an improvement item that’s listed as “Fixed native PHP Session storage and cleanup”. I do not know what exactly was fixed here, so I recommend contacting Shopp support and ask them if they can elaborate on what was fixed and if there are plans to make it so Shopp doesn’t store session data that Shopp doesn’t need (like EE session data).
|
|
Susan McLean
|
September 11, 2014 at 6:57 am
Wow Josh, you explained that beautifully and very in depth…thank you so much! I will definitely take this issue up with the Shopp plugin authors. That’s so strange that a plugin would do that for every other plugin in addition to it’s own. Anyway, thanks again for your help 😀
|
|
Josh
|
September 11, 2014 at 8:31 am
You’re welcome.
|
