The data is already automatically deleted. Session rows are removed on a WP Cron job.
-Chris
I also got this error
Site details:
WordPress 3.8.1
Easy Digital download 1.9.8
php 5.2.17
mysql 5.1.66
panel DirectAdmin
I got the plugin updates, but does not work
Please help …
Error:
<strong>Warning</strong>: Cannot modify header information - headers already sent by (output started at /home/site/domains/site.ir/public_html/wp-includes/functions.php:2769) in/home/site/domains/site.ir/public_html/wp-content/plugins/easy-digital-downloads/includes/libraries/class-wp-session.php on line 124
Hi there,
For those who are still having problems, please open a ticket on our support forums at easydigitaldownloads.com/support so we can work through this with you without everyone on this topic getting notified for every comment.
Thanks!
-Chris
These session rows are still being created despite the “cron job”
Session rows will always be created. The cron job simply deletes expired session rows.
Yes, but at the rate of 3000-odd per hour?
I also got this error
Site details:
WordPress 3.8.1
Easy Digital download 1.9.8
php 5.2.17
mysql 5.1.66
panel DirectAdmin
I got the plugin updates, but does not work
Please help …
Error:
Warning: Cannot modify header information – headers already sent by (output started at /home/site/domains/site.ir/public_html/wp-includes/functions.php:2769) in/home/site/domains/site.ir/public_html/wp-content/plugins/easy-digital-downloads/includes/libraries/class-wp-session.php on line 124
please Help…
wait answer .
@sadhaka Are you using the User History extension? If so, deactivate it. Turns out it has a bug that causes an enormous number of session rows to be created. The developer is working on a fix.
@esiwordpress Where does the error show for you?
Pippin – no I’m not using that extension.
hi
When I activate the plugin I get this error shows
I can not activate any plugin
Please help …
Pippin, switching to PHP sessions using the EDD_USE_PHP_SESSIONS method outlined in your link does seem to have stopped my PHP errors. Also there do not seem to be any more _wp_session or _wp_session_expires rows being created and needing cleanup in my wp_options table.
Should this ‘PHP sessions’ method be therefore kept going indefinitely?
Does it have any disadvantages when compared to the default behaviour of using WP_Session?
Yes continue to use it. We don’t enable it by default because a lot of hosts do not support PHP sessions.
Since your host supports it, I’d definitely use PHP sessions. It will be faster.
Thanks Pippin. I’ll continue to use the PHP sessions method. Case solved for me then I hope.
