not picking up category/type newsletter

Yes, identical problem with a container and category configured properly for newsletter content creation.

Same with me - I have 1 newsletter created, but can not send mails out (even if the category is highlighted properly, when go to a draft message to send it). I can send on the other hand a test message, which arrives with 2 strange parts:
1) A subject starts with [Unassigned newsletter] before the e-mail subject defined
2) At the end, it says "-- Footer will be appended here"... I presume here should be something else (even if I can not find any footer in configuration of this module...)

I've looked a bit into MySQL tables and found out that nid for this message is nid=169, term id for my newsletter tid=61 and a vocabulary id for it is vid=12. Despite of that, there is tid=0 in a sn_newsletters table (nid=169 as expected). Setting it to 61 doesn't help, the same error message is displayed when setting message to be send and trying to save the node (also the value of tid ir reversed back to 0).

By the way, I've deactivated all subscribers but 2 of (my) e-mail addresses (just to test the first message). Could this anyhow crash the system? And, it is extremely annoying inactivating subscribers at the second page, as the screen always displayed the first page after any such action! Now imagine to go 10 times first back to the second page to continue with a next subscriber... Argh.

I've got the category module running, turned on the taxonomy wrapper before installing simplenews, have the legacy module on, and simplenews up and running. I can create a newsletter that both tests and publishes, but I get the same "unassigned newsletter" in the header, and an "n/a" on the newsletter page under the "drafts" tab.

The usual box for selecting which newsletter does not appear on the node edit page, and selecting the appropriate newsletter as a category, in either or both places lower on the page, does not fix the problem.

I hope this information is helpful.

Okay, it's the next morning, and I'd swear I've done nothing in the meantime except log out of the site and log back in again, but now it's acting a little differently.

The difference is that the email it sends out to subscribers now has the right name [Today's News] in the brackets for the newsletter, and it now lists, on the newsletter page under the "newsletters" tab, both the name of the newsletter [Today's News], and the name of the issue [Test Mailing] that was sent--as separage newsletters.

On the "sent" page, there are four options in the drop-down filter list, which produce the following results (intended to be read as a table):

Filter Option:___________Title:____________Newsletter:

all newsletters_____________Test Mailing__________n/a

n/a_______________________No newsletters available_____

Today's News_____________Test Mailing __________n/a

Test Mailing________________No newsletters available_____

On the subscriptions tab, I get options for both, as though they were separate newsletters.

On the settings page I get tabs for both, as though they were separate newsletters.

They both produced blocks.

So, they are being treated as separate newsletters everywhere except when the issue is sent out, and, to some extent, on the "sent" page.

I'm guessing that this still has some bearing on the original issue, and that this bizarre (to me) behaviour is meaningful to someone who knows how the module works.

I hope it's useful.

I have no explanation for this, but here's my final report.

I deleted all the Newsletters that I had previously created, and all the issues as well.

I set up a completely new newsletter, and created two new issues as a test.

Everything works fine this time--with one exception. When Simplenews lists the issues on the sent items tab, it lists the Newsletter for each issue as "n/a".

However, it does know that they are issues of the appropriate newsletter, because it filters for them correctly under the newsletter name, and it doesn't show them when I select "n/a" as the filter.

It does seem to be a bug, but not an important one...

Thanks for a great module, by the way. It really does the job.