On manual cron run from status report page, I either get a the following error (followed by a cron success message):

Missing argument 2 for ejournal_invoke_extensions(), called in /var/www/html/aapcjournal.com/modules/ejournal/ejournal.module on line 342 and defined in /var/www/html/aapcjournal.com/modules/ejournal/ejournal.module on line 3581.

Or, more often, the cron action page returns no data to the browser and the following warning is logged:

Cron run exceeded the time limit and was aborted.

This error was never encountered until the e-journal module (5.x-1.x dated 12 Nov 2007) was installed. Most e-journal functions seem to work fairly correctly (except as to be noted in other issue posts).

Drupal/site config info:

Configuration file:
Protected
Cron maintenance tasks:
Last run 58 min 5 sec ago

Database schema:
Up to date
File system:
Writable (private download method)
GD library:
bundled (2.0.28 compatible)
MySQL database:
5.0.27
PHP:
5.1.6
Unicode library:
PHP Mbstring Extension
Web server:
Apache/2.2.6 (Fedora)

Comments

higherform’s picture

higherform commented

Please see also my ejournal_log table support request, as it is possible this bug is related to that problem.

Thanks.

romca’s picture

romca commented
Status: Active » Postponed (maintainer needs more info)

Thanks for info, the cron function is not used often (how useful is it for you? - the automatic publication)
I have fixed it, it was the cron function calling other ejournal plugins without argument - i simply removed it, because for cron, plugins can implement their own hook. Yet, there remained one call, when issue gets published (but this should not create the troubles you describe). I have experienced sth similar only when there was a bug in the access module settings (fixed long time ago)
Could you please get the fresh files from the CVS and tell me if the problem persists?

higherform’s picture

higherform commented

Update from 5.x datestamped 24 NOV 07... man cron run without errors this time. (note I did also complete the adjustments to ejournal_log table, so it could be either "fix" in play here).

The site this module is configured on is still pre-launch... we probably will not need to do manual cron very often, but we are using it a bit while we refine some internal site search stuff.

Thanks for the quick work on these bugs/features. Will report anything else I stumble upon.

romca’s picture

romca commented
Status: Postponed (maintainer needs more info) » Closed (fixed)