This bugtracker is kept to provide history on old issues.
|Anonymous | Login | Signup for a new account||2019.02.16 01:08 CET|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003123||Piwigo||authentication||public||2014.08.15 13:15||2014.08.24 18:50|
|Target Version||2.8.0beta1||Fixed in Version|
|Summary||0003123: Allow easier sharing of URL with identification.php?redirect=...|
|Description||To invite a user to a particular page visible without authentication, but with more content when authenticated (e.g. an album with both public and private pictures), one can send a link like|
that will invite the user to login, and then show the content. There are two drawbacks with this approach:
* Currently, one has to build the URL by hand. It would be much easier if the "connect" button available on each page was directing to identification.php?redirect=<the current page> instead of argumentless identification.php. Then, a gallery owner could visit the page to share, click "connect" and copy-paste the URL from the browser's location bar (well, not perfect since one would have to log out to get the "connect" button).
* When identification.php?redirect=<...> is visited by a guest, an error message is displayed "You are not authorized to access the requested page", regardless of whether the content is actually visible or not. It would be better to check whether the page is actually forbidden before showing the error message.
* One could even go further and allow login= and password= GET parameters, and we would get very close to the "share by URL" feature.
|Tags||No tags attached.|
|Database engine and version|
|Web server||Apache 1.3.x|
just link a private page: the user will be redirected to the login page and then after login to page requested. So that already works
Yes, but my point was about pages that are not private, but have more content when authenticated (see the first line of my report).
If I send the link to the page as-is, then people will forget to authenticate and see only the public content.
|oh ok sry I understand much more|
|You should try the Event Cats plugin, which allows login through a link|
Event Cats is not available on piwigo.com, which currently hosts me.
I'm suggesting this only because I think it would be easy to implement, and it would make sense in other flows:
The fact that "connect" forgets the page it's comming from is actually a little annoying anyway. See what Mediawiki does for example, when you click "log in" from any wikipedia page, you get the login page with returnto=<where you came from>, and once you log in, you're back to the page you were visiting.
Doing the same would solve my first point, but it would require the second to be fixed to avoid a spurious error message.
|2014.08.15 13:15||mmoy||New Issue|
|2014.08.15 13:15||mmoy||browser||=> any|
|2014.08.15 13:15||mmoy||Web server||=> Apache 1.3.x|
|2014.08.15 14:03||flop25||Note Added: 0007550|
|2014.08.15 14:06||mmoy||Note Added: 0007551|
|2014.08.15 14:07||flop25||Note Added: 0007552|
|2014.08.15 14:08||flop25||Note Added: 0007553|
|2014.08.15 14:38||mmoy||Note Added: 0007554|
|2014.08.24 18:50||plg||Target Version||=> 2.8.0beta1|
|Copyright © 2000 - 2019 MantisBT Team Contact|