Newsletter Builder v2.02 Released!

Hi Jerry,

Thanks for your feedback! Here's some responses:

>1) I've created a number of test newsletters and all of them show in the archive record list, but the
>on-line links all point back to the archive.php file and show the latest newsletter.

For emailed newsletters you can use #archive_url# for the url of your web archive viewer and #message_num# for the message num.

For the newsletter list in your archive viewer, the generated code should add the newsletter number to the end of the url:
<?php foreach ($archivedNewsletters as $record): ?>
<?php $isSelected = ($record['num'] == $latestNewsletter['num']); ?>
<?php if ($isSelected) { print "<b>"; } ?>
<a href="?<?php echo $record['num']; ?>"><?php echo htmlencode($record['subject']) ?></a><br/>
<?php if ($isSelected) { print "</b>"; } ?>
<?php endforeach ?>

Can you let me which one is causing the problems? And if you started with an earlier version you may need to update the generated code for the archive viewer.

>2) When I click on the 'This default newsletter content can be edited under: Newsletter Settings' link in the email,
>I'm taken to: http://thecmsbcookbook.com/?menu=_nlb_settings
>instead of http://thecmsbcookbook.com/cmsAdmin/admin.php?menu=_nlb_settings

That content is just meant to be a hint for developers where to look for settings, you can safely remove it. I've just unlinked it for the next release and left it as text so it's more clear.

>THE QUESTIONS:
>is it possible to send emails directly from the email address field in the 'accounts' database records (or from any other multi-record database)?

No, but it's idea we have on the (long range) radar. For now one workaround would be the manually export the email list from one database and import it through the "Import Emails" menu under plugins. This import feature will only import emails not already in the database, so it's safe to do multiple times, but you would have to do it manually to keep things in sync.

>Is it possible to import and use the code from an external viewer as the body of the newsletter
> (as I've been doing up to now) instead of the code that has been created in the wysiwyg editors
> in the 'Settings' and 'messages' editor?

Not really, but the next release (coming very soon) supports multiple email templates. Email readers can be really picky, so you often need to custom design templates and HTML for them differently than you would for a regular web page.

Also, I noticed some of your cookbook recipes added custom fields, if you add any custom fields to the newsletter schema and then upgrade, they might get removed when the schema's are updated (but won't be removed from MySQL). If that happens just click on section editors, look for the fields with type 'none' and re-add them.

Hope that helps, let me know any other questions. Thanks!