Hi, I realize my situation might be out of the course of ordinary usage, since my problem is tied to my deployment strategy. Still, I have deployed tons of modules using it, and never had a problem until now. I am using capdrupal (find it on github: fantastic) to deploy. If you are not familiar, it's based on capistrano, of RoR fame. Basically, when you deploy, the new code (meaning everything in /sites/all gets replaced from your git repository. It also uses drush to perform many additional necessary steps, which are outside of the scope of this inquiry. Anyway, I installed HTML Mail, (and Mailsystem) and deployed. everything went fine, and the site came up normally. I also use SMTP mail, so I went in to set up a new class, with HTML mail as the formatter, and SMTP mail as the sender. Suddenly, WSOD.

Now, I poked around through the carnage, and as far as I can tell, the site was unable to bootstrap, because it was looking for this new class in some nonsensical path:

/var/www/staging/releases/20140313223735//var/www/staging/shared/sites/default/files/mailsystem/HTMLMailSystem__SmtpMailSystem.mail.inc (note the // before the second "var")

when it should be

/var/www/staging/current/sites/default/files/mailsystem/HTMLMailSystem__SmtpMailSystem.mail.inc

I think, of course, that this results from capistrano's use of symlinks to create a "normal" looking directory (current -> 20140313223735, and current/sites/default -> shared/sites/default) but I'm unsure of why creating a class would break it, unlike any of the many others.

This is a support request, not a bug - I realize it's out of the scope of normal use - but if there is anything unusual, or non-standard about the way this module uses the root path variable that you can tell me that might help me debug this issue, I would appreciate it.

Cheers!

Comments

TR’s picture

Status: Active » Closed (won't fix)
Issue tags: -Additional class