Re: [PHPiCalendar-DEV] publish.php with basic auth, write to user specific calendar..

[Blake C. <bl...@re...>]

Hey Jo,

I believe I made the patches correctly.  Let me know if this is correct.

This patch only has the on/off functionality, it does not have the 
granularity for a per user functionality.

Thanks,

Blake

Jo Rhett wrote:
> I'm sorry, I overlooked that option.  Yes, I could make an if/then  
> around a variable to support this behavior, no problem.  Right now  
> publish.php doesn't (yet, I think) read the main configuration file,  
> so it would have to be edited in the publish script itself.
>    (I have a version that does, but I'm pretty sure it's not  
> published/release-quality yet)
>
> If you send me a patch with this functionality in an if/then, I'd be  
> fine integrating it.
>
> On Mar 4, 2008, at 7:02 AM, Blake Cornell wrote:
>   
>> Luckily for me hacking in this functionality was quick and easy.   
>> Since
>> phpIcal had everything I was looking for except that, well, simply,  
>> now
>> it has everything I need.
>>
>> I've yet to check out your previous comments regarding re-working the
>> authentication system, but yet agree that it would take quite a bit of
>> planning and implementing.  I looked into it before I got your  
>> response.
>>
>> I'm unsure of the development schedule for this project but do plan on
>> implementing this feature version by version for myself (I expect  
>> it to
>> take less then 15 minutes).  I've already added a global variable to
>> switch this functionality on and off.  If this feature were to ever be
>> 'supported', it would have to allow global and user specific  
>> hooks.  In
>> all, its not my call to do this or not.
>>
>> In the least, thanks for your input.
>>
>> -Blake
>>
>>
>> Jo Rhett wrote:
>>     
>>> On Feb 21, 2008, at 10:56 AM, Blake Cornell wrote:
>>>
>>>       
>>>> User engineering has a calendar called managment.  User management
>>>> has a
>>>> calendar called engineering (don't ask me how this would happen,  
>>>> users
>>>> are supposed to do things like this).  They both are allowed to post
>>>> their calendars.  Little do they know, they can't overwrite each
>>>> others
>>>> calendars cause they are locked to publish calendars as their user
>>>> name.  It allows me a greater piece of mind for the admin (me).
>>>>
>>>>         
>>> The real, honest answer is: phpIcalendar was never intended to solve
>>> this problem, and will require an extensive rewrite to do so.
>>>
>>> You can hack around this problem by having all of the calendars be in
>>> subfolders, and limit the write access to each subfolder using apache
>>> controls.
>>>
>>> But yes, it's a hack.
>>>
>>>
>>>       
>> ---------------------------------------------------------------------- 
>> ---
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>>     
>
>