emogrifier breaks functionality

I put the emogrifier.php file back into place and removed the '@' symbol from these two lines (on my file it's 272,273)

    $inliner = new Emogrifier($html, $css);
    $content = $inliner->emogrify();

Unfortunately the result is the same, blankness.

I'm pretty sure the VR errors are either related to saving the newsletter node unpublished and not having the call to the VR module ever get made again or one of the possibilities you've mentioned. I haven't tried it much so I don't know if there's a pattern there. I know while I'm having these problems with the emogrifier.php file the node probably isn't finishing it's publish routine and that's why the VR portion doesn't work.

I just looked at my Vertical Response account and see that none of the test nodes have actually resulted in drafts or campaigns, so it's not sending the information through the API as I expected.

I have tried including a css file through the content/node-type/newsletter advanced form, the file is the theme file at sites/all/themes/mytheme/css/main.css and I've tried it with no css file checked and the result is the same. My theme is a subtheme using the 960gs base theme.

There are no entries related to the enews module at reports/dblog.

For these tests I've only been typing in "test" to the body field and not adding any classes or styles. I am using the wysiwyg module with FCKEditor and the Full HTML input filter.

It occurred to me that when I first tried testing this out I didn't have an active API enabled VR account and got some odd errors as a result. I also didn't have the emogrifier.php file in place when I first activated the enews module. Could having the modules enabled and used without everything in place be a cause for this? Is there something I can look for in the database that would be an indicator that the module didn't get set up right from the beginning?

Thanks - looking at the module earlier I wondered about the paths to the emogrifier file but didn't change anything since I was trying to follow your instructions.

Changing the path on lines 247, 248 seems to fix the issue:

  if (file_exists($path . 'sites/all/modules/enews/emogrifier/emogrifier.php')) {
    include_once($path . 'sites/all/modules/enews/emogrifier/emogrifier.php');

I'll play around with it a bit more in the next couple of days to see if I can break it again, but for now I think that was it.

- David

This:

<?php
$path = drupal_get_path('module', 'enews');
print $path;
?>

returns this:

sites/all/modules/enews

I also tried changing lines 247 and 248 to be

  if (file_exists('sites/all/modules/enews/emogrifier/emogrifier.php')) {
    include_once('sites/all/modules/enews/emogrifier/emogrifier.php');

And that breaks it.

So despite how little sense it seems to make to me it actually wants the $path in there even though it would seem to return a non-existant path to the file.

I ran the patch and things seemed to be broken as before, taking out the leading slash on the path to emogrifier brings it back to sort of working but it's not including a stylesheet so I think in this case "working" means that it can't find the file and does everything except the emogrifier part which is kind of the same as if the file doesn't exist.

No watchdog errors are logged.

Could it be something is missing in my php build?
I just did a quick test using a different server and sub-theme but the same base theme and everything worked as expected.

I'll try to reduce the variables later today to see if I can figure out if it's a module conflict or something in the server configuration, let me know if you have any ideas for things to look for.

thanks!

That's it!
I needed to install php-xml which provides php-dom

Thanks for all your help!!!