Yes it does, I made sure it did, because I have a “custom” database, I mean, it’s not wp_, but yes I made sure it corresponded
Hello, do you have any idea ? It’s been a while now…
I tried to uninstall the plugin and reinstall the new version, to make sure I can set my expiration dates. But even like this there is a configuration problem… There is no solution ? I can’t uninstall, I can’t update, the plugin doesn’t work with this version (2.9.0) and I can’t change it, what can I do ?
Edit : It works with posts for version 2.9.0, but not for my CPT anymore
-
This reply was modified 2 years, 6 months ago by
nitneuq22.
Hi !
I actually have no clue on how to solve this problem. I can’t update, downgrade the version, it works on 2.9.0 but only for posts, whereas I also need it for my CPT, so how is it possible to solve it, especially when it’s not the only website I’m facing this issue with…
Can someone share at least a trail with me ? I thought about deleting corresponding lines in database, to completely recreate the structure, but I’m not used to the plugin so I don’t really know what cell or line to modify.
It seems that there is an incompatibility between the old structure (2.9.0) and the new structure. The plugin can’t transfer the informations from the old to the new, maybe it can help to have these informations.
@nitneuq22 I appreciate your patience. Could you please try this beta package and once again click “Fix Database” button on Setting?
https://1drv.ms/u/s!AsIYGyKS9Y3YpADhhcAg4gzt2Rye?e=sn91dx
Hi ! I tried on the clone I made, and it worked. But then I tried on the “real” website, but still doesn’t work. I’m quite sure there is a problem transfering data from the old structure to the new, but I can’t figure out why the “Fix Database” option doesn’t work. I assume it creates database tables ?
@nitneuq22 Yes, that button attempts to create a database. More specifically, it tries to execute this SQL command.
CREATE TABLE wp_ppfuture_actions_args (
id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT,
cron_action_id bigint(20) UNSIGNED NOT NULL,
post_id bigint(20) UNSIGNED NOT NULL,
enabled tinyint(1) NOT NULL DEFAULT '0',
scheduled_date datetime NOT NULL,
created_at datetime NOT NULL,
args varchar(250) NOT NULL,
PRIMARY KEY (id),
KEY post_id (post_id, id),
KEY enabled_post_id (post_id, enabled, id),
KEY cron_action_id (cron_action_id, id),
KEY enabled_cron_action_id (cron_action_id, enabled, id)
);
Can you try to run above SQL command manually?
I modified the command to match the prefix of my database, it successfully created the table, and the plugin has no longer database structure problems. The thing is, now, when I try to add an expiration date, I tested one minute later but it didn’t work. I suppose it solved the issue at 90% for the new version, but it still doesn’t work, the wished actions aren’t done
When I go to the database, it successfully created the actions like this : ‘{“expireType”:”private”,”category”:[],”categoryTaxonomy”:””,”date”:1701331440}’
But they are not taken when the time has come to make them private (I don’t really know if what I’m saying is english sorry about that)
Edit : It seems to work, I was using the beta version you sent me, and it didn’t work. Now that I have created the table in the database, I put the 3.1.3 stable version and it worked
-
This reply was modified 2 years, 6 months ago by nitneuq22.
@nitneuq22 Does that mean all your issues are resolved now?
Well… I was on another website, to update the version of the plugin, and I realized that there is the issue I described with the beta version… Everything looks fine, the date is displayed, but when I try to set a date like in 2 minutes, well, 2 minutes later the post is still published.
So it is solved for one of the websites, but not the other one
@nitneuq22 How about using the latest version just like what you did on your other website?
I already tried the beta version, the 3.1.3 version and 3.1.0 version, and the issue is still here unfortunately
No worries. As it’s no longer related to the current topic, please open a new thread, and we can continue the discussion there.
Okay then this topic can be marked as solved, I will open a new one, thank you 🙂
-
This reply was modified 2 years, 6 months ago by nitneuq22.
