NYCPHP Meetup

[Helvécio da Silva]

Hello Ellen,

I suggest you create TWO sets of the SAME menu. One to be displayed when
the user is logged out and the other when logged in.

The logged out version of the menu would have all its menu itens pointing
to a single article telling the use they cannot see that content until they
login, plus offering the possibility to register in a more user friendly
environment. I feel the current proccess is not much user-friendly. Or you
can have a separate article for each menu item with similar content, still
pointing to the option of logging in.

The logged in version of the menu would have the actual menu itens.

Hope this helps.

Best regards,

2012/9/10 Ellen Rothwax <ellen.rothwax at gmail.com>

> I have a strange situation I am hoping someone can help. I have a
> situation where I want to give viewing access to a certain section/pages
> only to a particular group of viewers. I want the public to see the
> navigation to those pages, but not have access to them unless they have
> requested permission, in which case they will be added as a user in that
> group.So when they do navigate to the page, there is a system message "You
> are not authorized..." That is how it should be.
>
> The problem is that in Firefox and IE, if the user logs in, navigates to
> the restricted page and then logs out,  they can't navigate back to the
> restricted page again while logged out.The log in module is set to redirect
> on log out to the default page, which is the Home page, which it does on
> log out. But if you click on the menu item to navigate to the restricted
> page again, instead of seeing the page with the system message "You are not
> authorized...", it defaults to the Home page.This is confusing to the user
> since they were able to navigate there before. If they happened to be on a
> different page (not the restricted one) when they logged out, they will
> have no problem navigating back to the restricted page and seeing the
> system message "You are not authorized...".
>
> In Chrome and Safari, I don't have the problem. If I clear the cache, it's
> fine, too, but I can't expect visitors to know to clear their browser cache.
>
> I am experiencing this on 2 different sites, both 2.5.6. One site also has
> K2, so I tried using it's login module instead of Joomla core, but it made
> no difference. I also tried using BTLogin module, and again, no difference.
> Anyone have any insight?
>
>
> --
>
> <http://www.ebrwebsitedesigns.com>
> Ellen Rothwax
> Web Design and Development
> *Don’t say you can’t afford a website. . .you can’t afford not to have
> one.
> *www.ebrwebsitedesigns.com*
> *(P) 203 572-5756*
> *
>
> _______________________________________________
> New York PHP SIG: Joomla! Mailing List
> http://lists.nyphp.org/mailman/listinfo/joomla
>
> NYPHPCon 2006 Presentations Online
> http://www.nyphpcon.com
>
> Show Your Participation in New York PHP
> http://www.nyphp.org/show_participation.php
>



-- 
Helvecio "Elvis" da Silva
Rio de Janeiro - Brasil - helvecio.rj at gmail.com
http://www.helvecio.com - http://blog.helvecio.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/joomla/attachments/20120910/c3c3ffd8/attachment.html>