Hikashop Orders Automatic Cancel Plugin problem

Hi,

I just discovered that this plugin is not doing its job.
When I check the plugin settings I see two values:

Period: 864000
Last update: 1379237943

Which means 864000 = 240 hours = 10 days. After 10 days when an orde ris still on status created, it should be cancelled.
1379237943 ( Unix timestamp) decoded into human time is: Sun, 15 Sep 2013 09:39:03 GMT, which is approx. two days ago.

The cron works fine, otherwise we wouldn;t have this time stamp. But still all orders that are longer for 10 days are still on status created. They are NOT cancelled.

Of course the plugin is enabled.

What could be wrong?

Kind regards,
Maurice

Hi,

Thanks to see the report via the menu Configuration > Cron, Report tab.
And give us the potentially returned error.

Hi Xavier,

I did what you suggested but it gives me an error:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 127066863 bytes) in /home2/repdon/public_html/trancewerk.nl/administrator/components/com_hikashop/controllers/config.php on line 270

So I checked via FTP and saw the file is over 127 Mb. Well, that's too big and most probably the reason for this error.

Could that be the problem in the first place? Due to this too big size, the cron script fails to load the file and crashes, so it cannot continue it's work?

I've downloaded the file and opened it. There are no errors. The last couple of lines are:

******************************************************************************************************************************************************
******************** 17 september 2013 00:36 ********************
HikaShop opgevraagd op 17 september 2013 00:36

******************************************************************************************************************************************************
******************** 17 september 2013 00:37 ********************
HikaShop opgevraagd op 17 september 2013 00:37

******************************************************************************************************************************************************
******************** 17 september 2013 00:38 ********************
HikaShop opgevraagd op 17 september 2013 00:38

******************************************************************************************************************************************************
******************** 17 september 2013 00:39 ********************
HikaShop opgevraagd op 17 september 2013 00:39

******************************************************************************************************************************************************

This is Dutch and it says: Hikashop is called on $date.

As you can see we have a 1 minute cron job, Every one minute the cron is triggered. This results in many entries.

But the fact that the file is updated untill the last events, assumes that the entries are appended to the file without the cron script failing.

Any ideas?

I have deleted this file from the cron settings page so that the cron task can start with a new empty file. Let's see whats going to happen.

Maybe it's an idea to build in a filesize check and when that level is exceeded, a new log file is automatically created?


Kind regards,
Maurice

After deleting the file, a new file was created. I can open this this file in the backend now. So that seems okay.

When I looked in the big file, after I downloaded it with FTP, I saw this:

******************************************************************************************************************************************************
******************** 15 mei 2013 20:25 ********************
HikaShop opgevraagd op 15 mei 2013 20:25
---- Details ----
Orders checked

******************************************************************************************************************************************************
******************** 18 mei 2013 11:33 ********************
HikaShop opgevraagd op 18 mei 2013 11:33
---- Details ----
Orders checked
Wisselkoersen succesvol bijgewerkt

******************************************************************************************************************************************************
******************** 18 mei 2013 11:34 ********************
HikaShop opgevraagd op 18 mei 2013 11:34

******************************************************************************************************************************************************
******************** 18 mei 2013 11:35 ********************
HikaShop opgevraagd op 18 mei 2013 11:35

******************************************************************************************************************************************************
******************** 25 mei 2013 17:43 ********************
HikaShop opgevraagd op 25 mei 2013 17:43
---- Details ----
Wisselkoersen succesvol bijgewerkt

******************************************************************************************************************************************************
******************** 25 mei 2013 17:45 ********************
HikaShop opgevraagd op 25 mei 2013 17:45

******************************************************************************************************************************************************
******************** 25 mei 2013 17:46 ********************
HikaShop opgevraagd op 25 mei 2013 17:46

******************************************************************************************************************************************************
******************** 25 mei 2013 17:47 ********************
HikaShop opgevraagd op 25 mei 2013 17:47


So after 18 mei 2013 11:33, there are no "Orders checked" entries anymore.
In the new file, that was just created, this line is also missing.
I have some old orders still with a status of 'created', that are older than 10 days. I expect them to be put on 'cancelled', but it still does not work.

Maurice

P.S.: The unix timestamp in the order cancel plugin, that tells the last time the plugin was called, is still the same.
So it appears the cron job itself is called correctly, but it doesn't call this plugin anymore.

Have you changed the parameters of the options "Cancelled order statuses" and "Default order status" in Configuration > Main > Order ?

The plugin has not been updated since april 2013 and the code added was:

		if(!empty($plugin->params['last_cron_update']) && $plugin->params['last_cron_update']+$plugin->params['period']>time()){
			//skipping auto cancel
			return true;
		}
		//update the time
		$plugin->params['last_cron_update']=time();
		$pluginsClass->save($plugin);

Hi Xavier,

No, we haven't touched those settings but I dicovered something else.

On May 15th we received our SSL certificate and on May 18th we installed it. The complete site runs on SSL since that time.
It appears that around the same time the functionality stopped.

How can we troubleshoot this?

Maurice

Hi Nicolas,

No, no redirections for the cron url. We have our own cron service and as you check the logfile you can see that it IS called every minute, however there are some gaps.

Still when the file IS called, the action that it should do is not done. It says:

HikaShop opgevraagd op 18 mei 2013 11:34 (Hikashop called on may 18, 2013 11:34)
HikaShop opgevraagd op 18 mei 2013 11:35 (Hikashop called on may 18, 2013 11:35)

So Hikashop IS called but it not doing its job. So I wonder why?

Maurice