Change newsletter/* menu paths to simplenews/*

Do anonymous users have subscribe newsletters permission?

whats the URL like?

hmm i have no clue as to what could cause this behavior:/
any entries in reports recent logs (dblog) ?

sorry,no idea whats causing this.maybe another module you are using?

Yes simplenews could be the cause, since it has a menu entry newsletter/confirm just like newsletter module does.
Simplenews should use simplenews/confirm instead.
Thus i am sending this to simplenews issue queue

We prefer to state "Simplenews conflicts Newsletter module".
First simplenews was first to "allocate" the /newsletter/ module namespace.

Then, simplenews provides concepts like "Newsletter" and not a "Simplenews". We decided during name cleanups to confirm this previous name also.
Also if we once will implement an entity for the Newsletter, the entity will have a name like "Newsletter" and not "Simplenews"...

Even if you think this might be wrong and a namespace in the URL should be prefixed with the module name, we won't be able to do that. Beta level guarantees API stability and the callback URL is an API relevant thing. We won't break millions of already sent links.

I still vote for a merge of those modules and i also don't see a reason to use both at the same time.

Agreed on most points but

Also if we once will implement an entity for the Newsletter, the entity will have a name like "Newsletter" and not "Simplenews"

Module's name and URL here in d.o was and is the namespace.It is the best practice to use your module's namespace to avoid incompatibilities like these.

First simplenews was first to "allocate" the /newsletter/ module namespace.

It was the wrong thing to do and still is.Just because it happened doesnt make it right:)

That said, i agree, no point to break existing links and API (especially when its highly unlikely for one to use these 2 modules together), but it should be noted as a thing to fix in the future.I would say "postponed" is the right status here

Agreed with postponed, we might look into this later. I am not sure if the namespacing rules apply to menu paths like they do to function names but I also agree that newsletter doesn't belong to us just because we were here first.

And yes, would be wrong to change it now and break all existing links and integrations.

I will add a point to the known problems section.

No, there isn't.

Why would you want to use both modules at the same time anyway, that makes no sense?

See http://drupal.org/project/simplenews_scheduler for recurring newsletters and inserting views can for example be done in the templates.

great, we can come back to this and fix it once the 2.x-dev branch opens:)

Im not sure how different the module is for Drupal 6, but I submitted a patch for the D6 version here: http://drupal.org/node/1801300
- I have tested it, and it seems to be working just fine.

Reopening in 7.x-2.x.
We can discuss now about a new naming scheme.

Suppose someone installed both Simplenews and Newsletter and then they uninstall both.

How do they go about deleting this menu entry "newsletter/confirm" so they can start over with a fresh install? Thanks.

Fixed in 4.x by #3392981: Final tidy up of subscription routes