Errors in log after update Failed opening './themes/engines/phptemplate/phptemplate.engine [#1394410]

include_once() [function.include]: Failed opening './themes/engines/phptemplate/phptemplate.engine' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /home/oursite/html/includes/theme.inc on line 167.

Location http://www.oursite.com/cron.php?cron_key=ourkey

Comments

Comment #1

venusrising commented 4 January 2012 at 23:19

we updated system cron per readme to

wget -O - -q -t 1 http://www.oursite.com/sites/modules/elysia_cron/cron.php?cron_key=ourkey

Cron will run but we now get page not found errors

Comment #2

gotheric commented 4 January 2012 at 23:30

".../sites/modules/..." should be ".../sites/all/modules/..."
(if you used standard drupal directories).

It's very strange that a cron job is tring to inizialize phptemplate.engine, it seems a problem of that module.
Enable elysia cron debug and try to understand what cron job is doing the wrong include (or disable selectively cron jobs to catch it).

Comment #3

venusrising commented 4 January 2012 at 23:39

Also, the new version no longer suggests replacing core cron file with elysia cron file is this still the case or has this truly changed?

Comment #4

gotheric commented 11 January 2012 at 08:18

Elysia Cron never suggested to replace the core cron file, only to call a different cron file in system crontab (sites/all/modules/elysia/cron.php instead of /cron.php).

If you intended that, there are some changes, but the real difference is in "point of view" of the documentation.

Now is said that, about INSTALL STEP A (that don't involve the system crontab change):
"You can stop here if you don't need a great precision over task execution and
you don't have to execute a task more often than once an hour. "

This is true. The elysia cron.php helps in reducing the call overhead in a system with a LOT of cron calls. If you don't have them, it's quite useless.