from my point of view everything should be removed, but keep site manager for local site.
the few users that use it should migrate to "local" site by copying all files locally and launching some sql queries (if they use remote sites they shoudl be able to launch one or 2 sql queries)

plg wrote:

I don't exactly see the advantage of keeping the site manager if we remove remote sites. Do you want to manager several local sites?
Anyway, we'll need a tutorial to convert a remote site into a local site.

I won't be using sites anymore, but maybe someone does ? I will remove everything except site manager, then up to you if we remove site manager

I have changed some labels on the site manager, see [Subversion] r15659

Now I have to include the "remote sites feature removed" in the release notes.

I also have to check what happens when you upgrade a Piwigo 2.3 to Piwigo 2.4 if it contains a remote site : how to prevent users to upgrade if they have a remote site.

I have implemented the downgrade to 2.3.4 in case a remote site is detected, [Subversion] r15680

I admit I don't really like it, but for now I think it's the best solution to avoid angry users with a 2.4.0 not working because they have a remote site.