Tribble Posted October 9, 2024 Share Posted October 9, 2024 Hi, I want to start using the Customer Follow-up module that comes free with Prestashop, but it's going to backdate all the emails to everyone who's ever had an abandoned cart etc. I assume the system must store the date the cron was last run, so can I go into cPanel and manually edit the date to a more sensible one? If so, how? Thanks. Link to comment Share on other sites More sharing options...
Knowband Plugins Posted October 10, 2024 Share Posted October 10, 2024 Hi, Look for a table called ps_configuration (or {your_prefix}_configuration if you use a different table prefix). In this table, search for entries related to the Customer Follow-up module. This may include entries like: PS_FOLLOWUP_LAST_EXECUTION Once you locate the entry, edit the date to your desired starting date. For example, you might want to set it to yesterday’s date so that only recent events are captured. Make sure the date format matches what’s already in the database (typically YYYY-MM-DD HH:MM:SS). Link to comment Share on other sites More sharing options...
NordicDesigner Posted October 11, 2024 Share Posted October 11, 2024 22 hours ago, Knowband Plugins said: Hi, Look for a table called ps_configuration (or {your_prefix}_configuration if you use a different table prefix). In this table, search for entries related to the Customer Follow-up module. This may include entries like: PS_FOLLOWUP_LAST_EXECUTION Once you locate the entry, edit the date to your desired starting date. For example, you might want to set it to yesterday’s date so that only recent events are captured. Make sure the date format matches what’s already in the database (typically YYYY-MM-DD HH:MM:SS). The advice is spot on. Editing the date in the ps_configuration table under PS_FOLLOWUP_LAST_EXECUTION should help you control when the cron job considers the start date for sending follow-up emails. Just make sure you're careful with the date format (usually YYYY-MM-DD HH:MM:SS), as database changes can sometimes cause unexpected issues if done incorrectly. Before you make any changes, I’d recommend creating a backup of your database, just in case something goes wrong. This way, you can easily revert to the previous state if needed. Also, you might want to test this change on a staging environment before applying it to your live site, especially if you have a large customer base - just to ensure everything works as expected without flooding customers with emails they shouldn’t receive. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now