whenever my drupal site tries to run a cronjob, i get an error in my apache error log as follows,

[Tue Nov 24 23:28:31 2009] [error] [client 64.141.5.41] PHP Fatal error: Class 'DOMDocument' not found in /var/www/main/modules/wowarmory/wowarmory.inc on line 134, referer: http://portal.va7paq.ca/?q=admin/settings/supercron

this is an issue as wowarmory is unable to grab any info from the armory itself, and running the cron manually for wowarmory just sticks at a blank white php page. i had the module working fine a few weeks back on a debian server, i recently migrated all my stuff to a CentOS server and did a fresh drupal install, and now this is no longer working, with the default drupal Cron, or with supercron...
any help offered will be greatly appreciated.
Cheers,
Tyler

Comments

nhdriver4’s picture

Priority: Critical » Normal

My guess right off the top of my head would be that the DOM is not being populated. Make sure that the curl module is enabled in your php.ini. Change that, restart apache and let me know how that works for you.

wolf87ca’s picture

Status: Active » Closed (fixed)

Hey,
shortly after i posted that i went digging around a bit more and discovered i had forgotten to install the php-xml module, installed it restarted apache and she worked fine... yeah, my first intuition was php-curl, but i remember specifically installing it, in any case its all fixed.
Thanks Though :)
Cheers,
Tyler

pauligree’s picture

Installing php-xml resolved for me too

ravi shankar karnati’s picture

How an i install the PHP-xml module ?
can u briefly explain? thanks in advance...

ravi shankar karnati’s picture

How can i install the PHP-xml module ?
can u briefly explain? thanks in advance...

darrellduane’s picture

On Fedora 16, I installed php-xml by doing the following on the command line:

yum -y install php-xml php-devel

I'm not sure if php-devel is required but it may be and can't hurt. Then I had to edit my php.ini file and add the line:

extension=dom.so

I added this line in the section where it talks about extensions. I then restarted the apache web server and this error went away.