View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0015425||phpList 3 application||General||public||24-03-10 03:47||23-05-12 13:48|
|Target Version||Fixed in Version||2.11.7|
|Summary||0015425: Active lists not displayed on preferences page|
|Description||A number of forum reports mentioned that active lists were not displayed on the preferences page of a user and instead got this error message: |
"Sorry there are currently no newsletters available"
For more details, see:
A possible fix, which seems to work at least for some, was suggested in this post: http://forums.phplist.com/viewtopic.php?p=66937#p66937
|Additional Information||The issue is not widely reported on the forum. System info is missing in the forum reports.|
Could not reproduce this issue on my system.
|Tags||No tags attached.|
that sounds more like a config issue:
1. user is related to a subscribe page
2. subscribe page is not set to list any lists
only without subscribe pages will phpList list all "active" lists. When subscribe pages are in effect, it will use the ones set on the subscribe page.
does that sound like a possible cause for it?
||How is a user related to a subscribe page? Is there a way to see or change what Subscribe Page a user is related to?|
when viewing the user, there's a value for "Which page was used to subscribe"
if it's empty, it'll use the default page
I am seeing the same problem. I did a clean install of 2.10.5 using Plesk on a CentOS 5 VPS. I disabled all the existing lists, created a new list, made it active and added a user. I did a test mailing but was still in 'test mode'.
I then decided to upgrade to 2.10.12, replacing all files, updating the new configuration file and retaining the 2.10.5 database. The database update was successful. When I logged out and accessed the list as a user wishing to subscribe, I got the message 'Sorry there are currently no newsletters available'. Activating another mailing list did not change the symptoms.
When I applied the update to index.php from http://forums.phplist.com/viewtopic.php?p=66937#p63078, a new subscriber was able to see both lists. Making the test list inactive caused users to be added to the remaining list without having to select it.
I got 3,4,5,6 when I dumped $data["lists"] around line 512 of index.php. Assuming these numbers relate to the list numbers, the two lists that were active at the time were 1 and 7.
As a test, I activated lists 1, 3 and 7. With the update to index.php in place, all three lists appeared. With a stock index.php, I was automatically subscribed to list 3. $data["lists"] was still showing 3,4,5,6.
It will be at least another week before this phplist will go live, so I can do simple debugging if that will help.
Further testing showed that my problem was a 'user error'. I had not associated the new mailing list with any subscribe pages. Once I had done that, I was able to subscribe using the original index.php code.
The instructions relating to the linkage between mailing lists and subscribe pages could be clearer.
yes, I guess it's not very intuitive how it works, and it should be addressed either in documenting more clearly, or updating the way it works, adding eg a message about it.
Confirm Michiel's #0051035 statemente: it is not a bug, it just works, but the UI allows the list admin to generate this weird result.
My steps: created a list, let it "inactive", created a subscribe page, checked that list.
Result: visiting the subscribe page, it tries to expose the selected list, but is told that the same is inactive. As the page is left with no active lists, the corresponding message appears.
- Either in subscribe page's create/edit inform the admin that lists selected here "will be made active", repeating the concept in list's create/edit form.
- Or limit selectable lists (in subscribe page's create/edit) to those that are active.
I've updated the subscribe page editing, to only show public lists. http://phplist.svn.sourceforge.net/phplist/?rev=3252&view=rev
That still doesn't entirely resolve it, but it'll help.
Things may still go wrong if:
1. you have a list A public
2. edit a subscribe page and add A to the page
3. make A not public
So, it may be necessary to disallow making lists inactive when they are used in subscribe pages.