Converting call from application_top to autoloader! Auction Cron Job

I've got most of the other suggextions done, but the code change for application_top was wipe from the email.

How do I convert this from application_top to autoloader!

if (AUCTION_CRON_ENABLE == '0') {
  require(DIR_WS_CLASSES . 'class.productauction.php');
  productAuction::checkAuctionStatuses();
  }
```The way it was used is to check date and time for any closed auctions then process them if true.  The switch is to allow for a CRON Job and not do a check on each page load.  I've setup the config.auction.php in the auto_loaders folder like so...

$autoLoadConfig[0][] = array('autoType'=>'class',
'loadFile'=> 'class.productauction.php');

$autoLoadConfig[170][] = array('autoType'=>'classInstantiate',
'className'=>'productauction',
'objectName'=>'checkAuctionStatuses');

Also, Is their another way to do the switch?

OK.... fiddled around with it enough for it to work...

$autoLoadConfig[0][] = array('autoType'=>'class',
                                'loadFile'=> 'class.productauction.php');
                                
   $autoLoadConfig[170][] = array('autoType'=>'classInstantiate',
                                'className'=>'productAuction',
                                'objectName'=>'productAuction');
```  Worked, className and objectName needed to be the same, copying the function in class productAuction from checkAuctionStatuses() to productAuction() worked.  Then I used the CRON switch in productAuction()...  The CRON would call the checkAuctionStatuses()

davewest:

The way it was used is to check date and time for any closed auctions then process them if true. The switch is to allow for a CRON Job and not do a check on each page load.

Also, Is their another way to do the switch?
But ... the way you used the switch previously caused it to operate like this:
a) if run from cron job, then it checked statuses
b) if run by customer click firing application_top, and switch was '0' (which suggests "off"), then it checked statuses.

So, a runs if cron is on, and b runs if cron is off. So, that means it always runs. Thus there's no point for a switch.

DrByte:

But ... the way you used the switch previously caused it to operate like this:
a) if run from cron job, then it checked statuses
b) if run by customer click firing application_top, and switch was '0' (which suggests "off"), then it checked statuses.

So, a runs if cron is on, and b runs if cron is off. So, that means it always runs. Thus there's no point for a switch.
The thought behind the switch was to turn it off if the user could create a CRON Job to run the checks at a set time instead of every page load. Thinking that on a heavy accessed site with lots of auctions, having the checks run on each page load would slow things down. If both are used, then it would double the checks.

I don't use it at all on my site, but I don't have allot of auction items yet.

Then I guess the code should have been checking for the switch == '1' instead of '0'. Of course, that would change the suggestions as well.