Hey @marios-alexandrou
Can you try sending in a support ticket but don’t add the error message in the body of the ticket. Most likely our systems are blocking the form because of the SQL contents of the message.
You can put that error message in a text file and upload it in the Attachments field when submitting the support ticket.
Our team will take a look at this report as soon as we can!
Hey @marios-alexandrou
Just as an update please check that your website is running on PHP 8.0.
It isn’t running PHP 8.0. Is that now a requirement? I’ve been delaying the upgrade while some plugins I use catch up.
Hey @marios-alexandrou
Can you please contact us via the support form here https://easydigitaldownloads.com/support/ so that we can investigate?
The only time we have seen this is if the site was on PHP 8.1 but WordPress does not support that version at this time but PHP 8.0 works just fine.
Hi,
This error is most likely caused by the notifications table creation query failing during the EDD update on older versions of MySQL (under 5.6? my test system is 5.5.68) due to CURRENT_TIMESTAMP() being an unsupported default value for the date_created and date_updated columns.
The notifications functionality looks introduced in EDD 2.11.4.
To complicate matters, changing the columns types to timestamp is insufficient, since older MySQL will now complain with:
Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
Since I see EDD does set default values in the code for these two columns, I removed the default SQL value for both columns and that allowed me to manually resolve the error by creating the table manually with:
CREATE TABLE __TABLENAME__ (
id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT,
remote_id bigint(20) UNSIGNED DEFAULT NULL,
title text NOT NULL,
content longtext NOT NULL,
buttons longtext DEFAULT NULL,
type varchar(64) NOT NULL,
conditions longtext DEFAULT NULL,
start datetime DEFAULT NULL,
end datetime DEFAULT NULL,
dismissed tinyint(1) UNSIGNED NOT NULL DEFAULT 0,
date_created timestamp NOT NULL,
date_updated timestamp NOT NULL,
PRIMARY KEY (id),
KEY dismissed_start_end (dismissed, start, end)
) DEFAULT CHARACTER SET __$wpdb->charset__ COLLATE __$wpdb->collate__;
Update the table name, charset and collation with those valid on your server.
I can’t say if the table structure change has any effect on the dashboard functionality (I haven’t noticed anything terribly broken so far, though).
