View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000151 | BwPostman | Newsletters Frontend | public | 2026-02-13 10:24 | 2026-02-16 06:07 |
| Reporter | laoneo | Assigned To | Romana | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Summary | 0000151: Empty Newsletter in frontend | ||||
| Description | When I open the newsletters list in the front end and click on a newsletter, then it shows an empty one. When I add the following code to the file /administrator/components/com_bwpostman/src/Table/SendmailcontentTable.php after line 371, then it works: $query->order('id desc'); Looks like it renders the newsletter with the first revision and not the last one. | ||||
| Tags | No tags attached. | ||||
|
|
Every time a new test newsletter is sent a new entry is made in the table #__bwpostman_sendmailcontent, so the newsletter view should always pick the last one I would say. |
|
|
You are right, this method only gets the first entry ($db->loadResult()) of this query. But BwPostman only saves one entry per newsletter and mode (HTML and text) so there is no need for an extension of this query. Since many years and versions of BwPostman this works as expected, so if Your table contains more than one entry per newsletter and mode, Your table seems to be corrupt. |
|
|
Everytime I send a test mail, then it saves a new entry in that table. So either there is another bug or then you need my change. Either-way, something is not working right. |
|
|
"Either-way, something is not working right. " That may be ... at Your installation. At my real websites and at all of my test sites, where I do automated or manual tests, it works as expected without Your suggestion, because there is only one entry for HTML version and one entry for text version for a newsletter at this table. Can You confirm this problem at a new fresh installation? |
|
|
Sorry, You are right! Until now I responded from memory, but that failed. Also a test sending creates entries at this table so there indeed can be multiple entries for one newsletter. I thought, the entries from test sending are removed, but that is not the case. My tests couldn't detect this problem, because the content was always the same… There are three possible solutions I can think of, but Yours seems to be the most practical solution. So there will be a new version for BwPostman, but I expect not before the next weekend. Tuesday will bring new versions of Joomla (6.0.3 and 5.4.3) to test and I have to write a newsletter, so it will take time… Thanks for Your reporting and being adamant. |
|
|
If it is only intended to have the latest version in the table, then I would remove the entries in the update script, beside fixing the bug. But if you make a new feature out of it and keep revisions, then you have to expand it to the save operation. But I would not leave broken installations and leave the entries in the table when not needed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-13 10:24 | laoneo | New Issue | |
| 2026-02-13 10:31 | laoneo | Note Added: 0000107 | |
| 2026-02-14 09:25 | Romana | Note Added: 0000108 | |
| 2026-02-14 13:04 | laoneo | Note Added: 0000109 | |
| 2026-02-15 00:02 | Romana | Note Added: 0000110 | |
| 2026-02-15 10:52 | Romana | Note Added: 0000111 | |
| 2026-02-15 10:52 | Romana | Assigned To | => Romana |
| 2026-02-15 10:52 | Romana | Status | new => confirmed |
| 2026-02-15 10:53 | Romana | Status | confirmed => acknowledged |
| 2026-02-15 10:55 | Romana | Reproducibility | have not tried => always |
| 2026-02-16 06:07 | laoneo | Note Added: 0000112 |
