Automatic Status - cron to update automatic status
Posted: 19 Oct 2018, 00:14
Hi Sergey,
I have to raise this issue again! Last time we thought it has been solved and, as a matter of fact, Ruko's autostatus.php did work correctly to update all records after you implemented the fix. Today I have tested the Automtic status fields for updating text in filters when using the OR conditions. Please see different posting.
For getting the testing done, I have added a new item in autostatus list with sort position 1 (to move it on top of list) and did add filter with the OR condition. As a result, I can confirm that the OR conditon works with text (like 'red'|'blue'|'green' when editing and saving a given record.
In the next steep, to get back to working conditions, I deleted that entry in list including all filters. Ever since, the autostaus.php cron does not update any records. This issue happened before and has been solved. However, we have the same problem again. After this happened, I updated to 2.3.1 ... same results.
Please look at this problem, I have been so closed to get the system to something that could be released ...
Thank you. Best Pepe
I have to raise this issue again! Last time we thought it has been solved and, as a matter of fact, Ruko's autostatus.php did work correctly to update all records after you implemented the fix. Today I have tested the Automtic status fields for updating text in filters when using the OR conditions. Please see different posting.
For getting the testing done, I have added a new item in autostatus list with sort position 1 (to move it on top of list) and did add filter with the OR condition. As a result, I can confirm that the OR conditon works with text (like 'red'|'blue'|'green' when editing and saving a given record.
In the next steep, to get back to working conditions, I deleted that entry in list including all filters. Ever since, the autostaus.php cron does not update any records. This issue happened before and has been solved. However, we have the same problem again. After this happened, I updated to 2.3.1 ... same results.
Please look at this problem, I have been so closed to get the system to something that could be released ...
Thank you. Best Pepe