NYCPHP Meetup

[Chris French]

Well, plugins can't be assigned like modules but they could be assigned a
list of content item id's or probably menu item id's, however it does have
draw backs it the content way it would do that both on the main view, and
category views, and probably even content modules that.

Menu item id's might be less problomatic
 On Jul 27, 2012 10:20 PM, "David Roth" <davidalanroth at gmail.com> wrote:

> This sounds like a good solution. Just curious, would this be a plugin or
> a module? Can you direct which pages you want a plugin to be enabled like a
> module? Might want to do this for more than one page with different
> passwords perhaps? (Sorry if it sounds like I'm creating more work for you.
> :-) )
>
> David Roth
>
> On Sat, Jul 28, 2012 at 1:02 AM, Chris French <contact at chrisfrench.me>wrote:
>
>> My vote would be a content plugin.
>>
>> if what you are trying to do hide a com_content article you could also do
>> the same thing with menu items.
>>
>> You could in the content plugin check for a session variable.if it
>> doesn't check if there are POST items.
>>
>> If so it checks if the post items are the assigned username and password.
>> If so it creates the session and loads the content item if not it either
>> loads a form instead of the content, or it redirects to something else.
>>
>> I would be willing build this plugin for a donation to some charity or
>> something probably take an hour.
>> On Jul 27, 2012 9:36 PM, "David Roth" <davidalanroth at gmail.com> wrote:
>>
>>> My vote would be for .htaccess too. I use it to protect /administrator.
>>> I'm wondering though, with turning on SEO, can that still be used if there
>>> is no real directory to put the .htaccess in? For example, you create a
>>> Joomla Article with an alias of foobaz. So that the URL of
>>> domain.com/foobaz finds the Article. But since there is no actual
>>> directory called foobaz, mot sure if .htaccess would be helpful in this
>>> regard. Or am I overlooking something?
>>>
>>> Maybe something with ACL could be done for a specific page or two? So
>>> that only registered users can access it? But doing that might be too high
>>> of a bar for some users for Kenny's purposes?
>>>
>>> David Roth
>>>
>>> On Fri, Jul 27, 2012 at 11:08 PM, Scott Wolpow <scott at wolpow.com> wrote:
>>>
>>>> .htaccess is a great way
>>>> SW
>>>> On 7/27/2012 9:53 AM, Kenny Berwager wrote:
>>>>
>>>>> Hello Everyone,
>>>>>
>>>>> What is the best way to password protect specific pages in Joomla
>>>>> 2.5.6 without using the default Registration system within Joomla?
>>>>> Since I really don't need to collect user data I'm fine with not using
>>>>> the Registration system of Joomla.
>>>>>
>>>>> I found MosPasswort Joomla plugin but its old.
>>>>>
>>>>> Thanks!
>>>>> Kenny
>>>>>
>>>>>
>>>>>
>>> _______________________________________________
>>> 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
>>>
>>
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/joomla/attachments/20120727/d319c7bd/attachment.html>