Upgrade from 6.x-1.x to 6.x-2.x brokenness

Likewise, rolled back to previous version!

Same here. rolled back too.

Fixed in 6.x-2.4 -- sorry. Been a lot of rapid changes these past couple of days while I was consolidating the 6.x and 7.x branches.

Same here

What version of the Mail MIME and Mail System modules are you using?

same here... in the latest dev version:

PHP Fatal error: Interface 'MailSystemInterface' not found in /home/site/public_html/sites/all/modules/htmlmail/htmlmail.mail.inc on line 19

Try this patch, or grab the latest dev version (updating now.)

Same error. Seems that the 2.x version adds dependencies that weren't there before. I deleted the htmlmail folder so I could access the site again, installed and enabled Mail System, Mail MIME, and Echo, then installed and enabled htmlmail. Everything is back to normal.

Okay, I need to add an update hook that prints an intelligent error message if someone updates from 6x.-1.x to 6.x-2.x and doesn't install prerequisites.

Fixed in 6.x-2.5. If you upgrade from 6.x-1.x to 6.x-2.x without first installing and enabling dependencies, HTML Mail will warn about the missing dependencies, disable itself, and redirect to the module page.

Version bump. 6.x-2.5 had a syntax error, sigh.

Same here! rolled back to htmlmail 6.x-1.7......

.. why all the new dependencies? 1.7 version was working fine?

The dependencies in the 2.x branch provide features and flexibility lacking in the 1.x branch:

Echo (39 lines)

-- Lets you use any one of 859 themes to format your messages.

Emogrifier (261 lines)

-- Including emogrifier in the 1.x branch violated drupal policy. For the 2.x branch, I moved the Drupal wrapper code to a separate module and used the Libraries API to reference the emogrifier.php file. This is the currently-recommended way to handle such dependencies.

Mail System (281 lines)

-- This is a backport of the Drupal-7 mail system, which lets multiple email-sending modules co-exist within the same site. Want to use Mime Mail for some messages and HTML Mail for others? Support this patch.

Mail Mime (379 lines)

-- Auto-downloads, includes, and provides Drupal-friendly wrappers for the excellent PEAR Mail_mime package. This allows HTMLMail to gracefully coexist with other modules that may generate MIME attachments before invoking the drupal_mail() function. The fix is to parse the message body for MIME attachments before adding additional formatting. As an added bonus, any referenced image files are auto-included as inline attachments. so the recipient never has to answer a scary Do you want to enable remote content? question. This also resolves issues such as:

• #1094524: HTML Mail module is incompatible with Contact Attach module.
• #760272: HTML Mail module breaks email body
• #799704: html_mail breaks email sent using mass_contact module

Additional features of the 2.x branch

-- You can specify a pre-theme and post-theme filter to make additional modifications to the message body. This lets you integrate HTML Mail with your choice of 241 filter modules.

All of the above helps distinguish HTML Mail from the competition.

Another version bump.

This is not working.

jddell -- you'll have to be a bit more specific, if you want my help fixing things.

#22: My question exactly. It seems that a security release was chosen simply to force people to upgrade to 2.x. If so, that's a really bad idea.

I don't know where this "security release" idea is coming from.

It's just that I'm not willing to support the 6.x-1.x/7.x-1.x branches any longer, so I unchecked their "Supported" checkbox on the project's "Administer releases" page.

Maybe the 1.x-branch can stay "alive" without dependencies?

+1

This is REALLY DISRUPTIVE update. It should have nicely converted my existing template, but that's gone. After reverting, I get dire warnings from Drupal about using unsupported modules.

I'm sorry about the "dire warnings", but you can always disable the update module if they bother you that much.

The 6.x-1.x branch has been unsupported for quite some time, really. Neither Chris Herberte nor I want to support it. If you want to support it, ask for maintainer access.

I can always fork the 6.x-2.x/7.x-2.x branch off to a separate module.

On a separate note, I don't see how it's possible for a module upgrade to rewrite your template files. Can you point me to an example of another module that rewrites template files? i'd like to look at the code.

The 6.x-2.9 release removes the dependency on Echo and MailMIME.

Same here! rolled back to htmlmail 6.x-1.7 our site use smtp auth module and has system fully functional php-pear installation

thanks

Interesting. I'll re-test the upgrade path. Works fine, btw, if you disable htmlmail, upgrade, then re-enable htmlmail. The redirects are to the admin/buildmodules page so you can do the re-enable bit.

Fixed in 6.x-2.11 -- at least it works for me in testing.

Okay, I'll let you in on the super-secret link at the bottom of the project page. It looks like this:

View all releases

There. Now you have access to the old, unsupported versions. Problem solved.

I will say it again.

If you or anyone else wants to support the 6.x-1.x version, contact Chris Herberte and ask for maintainer access.

Then you can mark it "supported" and start responding to support requests.

(waiting... waiting ... waiting...)

(I hear crickets.)

(very, very quiet crickets.)

So? You don't want to be the new maintainer of the 6.x-1.x branch? Me neither. I don't use that code and never have.

I submitted a bunch of patches to the 7.x branch and eventually created the 6.x-2.x (NOTE: That's a MAJOR VERSION NUMBER BUMP which traditionally means NEW FEATURES) so that I could have the same code running on 6.x and on 7.x.

Once I had functional code on both 6.x-2.x and 7.x-2.x, I went back to the project page and unchecked the "Supported" box next to the 6.x-1.x and 7.x-1.x versions. That is a public declaration that I don't want to maintain/fix/support/patch/upload/download/look at the old version any more. You don't like that? Sorry. Pay me a salary and I might reconsider.

What? You don't like the new version? Feel free to keep using the old one; I couldn't delete it from drupal.org even if I wanted to.

What? You don't like my attitude? Feel free to switch to Mime Mail which has five times as many users and is currently supported on 6.x.

According to Drupal policy, this project shouldn't even exist -- it should have merged with Mime Mail ages ago.

See Dave Reid's response to #1120214: Request to make upgrade a "Recommended Upgrade Vs Security Upgrade"

I modified the html module info file in order not to get the warnings, so it's not called as in "available updates" at all... Will also have to consider mime mail, thought this module worked perfectly .. till now.

By template, I mean the settings I had set in the "current" version. I had a header and footer. It seems that there's no place for those settings and I have to create a xxx.php.tpl file. Correct?

@sterndata -- Yes, I was trying to trim down the number of redundant controls and didn't see the need for both.

I cant work html mail with Mail MIME there is not a guide to put pear in my site.
I have apatch php php my admin.
I want to use this module but there is not a guide how i can but pear in my site and what to i have to enter in pear

Make the effort to but same guides

I've got it working on my production system now, with only one problem (that I've worked around). Our default theme is in sites/all/themes/ghb2. I put an edited version of htmlmail.tpl.php there, but it wasn't getting used. I copied that file into sites/all/modules/htmlmail and it is used. I can live with this; I just added it to my notes on things to watch for when updating modules.

@sterndata -- thanks for the feedback. Also see #1121894: Template files should go in the HTMLMail-specific theme directory..

See #1150140: Allow through-the-web editing of templates.

Anyone who is still looking for a clean upgrade from HTML Mail 6.x-1.3 to HTML Mail 6.x-2.x should subscribe to #1150140: Allow through-the-web editing of templates.