• I started using the module with version 150820. In that version I created some very nice (and complex) html email templates based on other email templates I have used. I have the module configured to send html emails but not to html-ify links because I do that myself in the template code.

    When I updated from that version to version 160106, the new WYSIWYG editor for notification and management messages breaks my code. There is the ability to view the source code, but there doesn’t seem to be the ability to work directly with the source code and bypass the WYSIWYG editor. When I paste in the code I need, the editor seems to overwrite some of my header information and causes the emails to not send as designed. I’ve had the same issue in version 160115 and have had to revert back to the last release prior to incorporation of the new editor feature to get my emails to send correctly.

    Is there a way to bypass the visual editor and work solely with source code and have it saved without having the editor make changes to what is saved? Something like the WordPress post editor with the option to use a visual or text editor would be much better.

    Thanks.

    https://www.ads-software.com/plugins/subscribe-to-comments-reloaded/

Viewing 13 replies - 1 through 13 (of 13 total)
  • singhnsk

    (@singhnsk)

    I’m on the same boat here. Please make some changes.

    singhnsk

    (@singhnsk)

    So, the way I was able to achieve it was to go to database (phpmyadmin) and edit the table there directly.
    Added all my HTML template there and didn’t look back at the plugin options page again. Works fine now!

    LouDB

    (@loudb)

    Same problem here! Just adding my voice to both of yours, hoping it will be heard for a future update ??

    I apologized for the late response.

    So far the editor has an option to view and edit the source code, but on the background is not adding the code as real raw source code.

    There is a plan to migrate this editor to the WP editor instead, so in the mean time you might want to change the code just as @singhnsk says.

    Regards.

    Thanks for the update @reedyseth . We appreciate all the work you’ve done to make this plugins the best one for the purpose of sending comments and new post notifications.
    Looking to see the change implemented in a coming release very soon.

    Thank you @singhnsk,

    We appreciate all the work you’ve done to make this plugins the best one for the purpose of sending comments and new post notifications.

    Some times is hard to keep a free plugin alive.

    Looking to see the change implemented in a coming release very soon.

    I understand @reedyseth. I’ve tried to donate a bit in the past according to what I was able to afford.

    If you’d be looking into this issue, I’d request you to allow us to have the full control over the notification email’s content. Because in the current implementation, even if I update the database directly with my template, the plugin is keen to add its own <head> and <title> section on top of the HTML defined in the database and hence the email is usually not rendered correctly in some mail clients due to duplicate <head> and <title> sections.

    @singhnsk

    I’m glad to inform you that I have done this change. Now you will use the WP edior instead of the current one. It would be nice if you download the code and give a try, also it will be helpful if you report any issue.

    Please download the code from this location

    https://github.com/stcr/subscribe-to-comments-reloaded/archive/master.zip

    You might get the update notice in the plugins section since I haven’t update the version in that code, just ignore it, you can be sure to have the latest code.

    Looking forward for your feedback.

    Now you can follow latest updates on twitter: @SubsReloaded

    Regards and thank you for the donation, every buck is well received.!!

    Hi @reedyseth

    I’ve installed the update from github a while back and it is now PERFECT! All seems done here. The editor now works the way all of us wanted. Styling is not ruined after saving or switching from source code to the WYSIWYG editor.

    This does not concern this post, but here’s one last request from my side which will make the plugin 100% complete for me. The 1-click unsubscribe link (when clicked in the email) takes the person to the regular subscription manager page, although his subscription is removed/disabled after that. Shouldn’t it just say something like “You’re now unsubscribed from these emails.” and end it? Because in the current form, the visitor does not know if he is unsubscribed or not. This doesn’t bother me much though.

    STCR is awesome!
    Thank you

    I’ve installed the update from github a while back and it is now PERFECT! All seems done here. The editor now works the way all of us wanted. Styling is not ruined after saving or switching from source code to the WYSIWYG editor.

    Awesome !

    This does not concern this post, but here’s one last request from my side which will make the plugin 100% complete for me. The 1-click unsubscribe link (when clicked in the email) takes the person to the regular subscription manager page, although his subscription is removed/disabled after that. Shouldn’t it just say something like “You’re now unsubscribed from these emails.”

    Correct that is the normal behavior, would you mind open a issue on GitHub so that I can track it down ?

    Alright. I’ll do that. You can close this topic here provided you have the privilege because it is sorted now.

    As soon as I release the update on WordPress I will close it.

    Regards.!!

    Thread Starter Todd Gibson

    (@oliverands)

    Thanks for making the update! I’ll wait to install until the new version is released.

    Can you leave a comment here when you release it and close this out so I get notified? (Since I’m currently using an old version, my WordPress install won’t show me that the new version has been released.)

    Thanks so much.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘HTML email formatting issues in last two versions’ is closed to new replies.