phpicalendar-devel

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

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

Hello,

I've had issues assigning apache basic auth to allow particular users to 
load particular calendars.  The filename didn't transport properly and 
thus creating a '.ics' file instead of ex. 'engineering.ics' or 
'management.ics'.

I've added the following function to publish.php.


function retUser() {
        if( $_SERVER['PHP_AUTH_USER'] )
                return $_SERVER['PHP_AUTH_USER'];
        else
                return $_SERVER['REMOTE_USER'];
}


and I've modified the follow line of code

                if($dataout = 
fopen($calendar_path.$calendar_name.'.ics','w+')){

to..

                if($dataout = fopen($calendar_path.retUser().'.ics','w+')){


Now its working great.

Thoughts?

Regards,

Blake

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

[Wesley M. <we...@we...>]

Hi Blake,

That change seems to make it do something completely different than  
before.... But if that is what works for you I don't see any problem.  
It doesn't seem like something that should get merged into the  
repository though.

Regards,
Wes

Quoting Blake Cornell <bl...@re...>:

> Hello,
>
> I've had issues assigning apache basic auth to allow particular users to
> load particular calendars.  The filename didn't transport properly and
> thus creating a '.ics' file instead of ex. 'engineering.ics' or
> 'management.ics'.
>
> I've added the following function to publish.php.
>
>
> function retUser() {
>         if( $_SERVER['PHP_AUTH_USER'] )
>                 return $_SERVER['PHP_AUTH_USER'];
>         else
>                 return $_SERVER['REMOTE_USER'];
> }
>
>
> and I've modified the follow line of code
>
>                 if($dataout =
> fopen($calendar_path.$calendar_name.'.ics','w+')){
>
> to..
>
>                 if($dataout = fopen($calendar_path.retUser().'.ics','w+')){
>
>
> Now its working great.
>
> Thoughts?
>
> Regards,
>
> Blake
>
> -------------------------------------------------------------------------
> 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
>



-- 
Wesley Miaw
http://www.wesman.net/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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

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

Hey Wes,

As far as committing it to the svn repo, the only feasible way to do 
that would be via a new config var with an if switch at the proper 
location.  It wouldn't require much yet would offer the additional 
option.  I would describe it in a PRD as `Adhere Calendar Name to User 
Name`.  In the least, I figure I offer up my experience.

Is there another way to allow multiple users authenticated write to user 
specific files within the same directory?  I know there is the sub 
directory way thats described in the wiki.

Do you think this added logic can perform more to current specifications 
rather then simply hacking the publish code?

Thanks,

Blake


Wesley Miaw wrote:
> Hi Blake,
>
> That change seems to make it do something completely different than  
> before.... But if that is what works for you I don't see any problem.  
> It doesn't seem like something that should get merged into the  
> repository though.
>
> Regards,
> Wes
>
> Quoting Blake Cornell <bl...@re...>:
>
>   
>> Hello,
>>
>> I've had issues assigning apache basic auth to allow particular users to
>> load particular calendars.  The filename didn't transport properly and
>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>> 'management.ics'.
>>
>> I've added the following function to publish.php.
>>
>>
>> function retUser() {
>>         if( $_SERVER['PHP_AUTH_USER'] )
>>                 return $_SERVER['PHP_AUTH_USER'];
>>         else
>>                 return $_SERVER['REMOTE_USER'];
>> }
>>
>>
>> and I've modified the follow line of code
>>
>>                 if($dataout =
>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>
>> to..
>>
>>                 if($dataout = fopen($calendar_path.retUser().'.ics','w+')){
>>
>>
>> Now its working great.
>>
>> Thoughts?
>>
>> Regards,
>>
>> Blake
>>
>> -------------------------------------------------------------------------
>> 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
>>
>>     
>
>
>
>   

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

[Jim Hu <ji...@ta...>]

Did someone just volunteer to migrate the cvs to svn?  ;)

Seriously, I would be in favor... but I haven't figured out how to use  
the sourceforge svn - I'm barely learning how to work with a local svn  
repository.

JH

On Feb 21, 2008, at 8:35 AM, Blake Cornell wrote:

> Hey Wes,
>
> As far as committing it to the svn repo, the only feasible way to do
> that would be via a new config var with an if switch at the proper
> location.  It wouldn't require much yet would offer the additional
> option.  I would describe it in a PRD as `Adhere Calendar Name to User
> Name`.  In the least, I figure I offer up my experience.
>
> Is there another way to allow multiple users authenticated write to  
> user
> specific files within the same directory?  I know there is the sub
> directory way thats described in the wiki.
>
> Do you think this added logic can perform more to current  
> specifications
> rather then simply hacking the publish code?
>
> Thanks,
>
> Blake
>
>
> Wesley Miaw wrote:
>> Hi Blake,
>>
>> That change seems to make it do something completely different than
>> before.... But if that is what works for you I don't see any problem.
>> It doesn't seem like something that should get merged into the
>> repository though.
>>
>> Regards,
>> Wes
>>
>> Quoting Blake Cornell <bl...@re...>:
>>
>>
>>> Hello,
>>>
>>> I've had issues assigning apache basic auth to allow particular  
>>> users to
>>> load particular calendars.  The filename didn't transport properly  
>>> and
>>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>>> 'management.ics'.
>>>
>>> I've added the following function to publish.php.
>>>
>>>
>>> function retUser() {
>>>        if( $_SERVER['PHP_AUTH_USER'] )
>>>                return $_SERVER['PHP_AUTH_USER'];
>>>        else
>>>                return $_SERVER['REMOTE_USER'];
>>> }
>>>
>>>
>>> and I've modified the follow line of code
>>>
>>>                if($dataout =
>>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>>
>>> to..
>>>
>>>                if($dataout =  
>>> fopen($calendar_path.retUser().'.ics','w+')){
>>>
>>>
>>> Now its working great.
>>>
>>> Thoughts?
>>>
>>> Regards,
>>>
>>> Blake
>>>
>>> -------------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> 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

=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054

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

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

HA!

My over cite regarding the svn vs cvs discussion.  SVN is nice although 
not for the timid.  Its an ideal free dev environment.

-Blake

Jim Hu wrote:
> Did someone just volunteer to migrate the cvs to svn?  ;)
>
> Seriously, I would be in favor... but I haven't figured out how to use 
> the sourceforge svn - I'm barely learning how to work with a local svn 
> repository.
>
> JH
>
> On Feb 21, 2008, at 8:35 AM, Blake Cornell wrote:
>
>> Hey Wes,
>>
>> As far as committing it to the svn repo, the only feasible way to do
>> that would be via a new config var with an if switch at the proper
>> location.  It wouldn't require much yet would offer the additional
>> option.  I would describe it in a PRD as `Adhere Calendar Name to User
>> Name`.  In the least, I figure I offer up my experience.
>>
>> Is there another way to allow multiple users authenticated write to user
>> specific files within the same directory?  I know there is the sub
>> directory way thats described in the wiki.
>>
>> Do you think this added logic can perform more to current specifications
>> rather then simply hacking the publish code?
>>
>> Thanks,
>>
>> Blake
>>
>>
>> Wesley Miaw wrote:
>>> Hi Blake,
>>>
>>> That change seems to make it do something completely different than  
>>> before.... But if that is what works for you I don't see any problem.  
>>> It doesn't seem like something that should get merged into the  
>>> repository though.
>>>
>>> Regards,
>>> Wes
>>>
>>> Quoting Blake Cornell <bl...@re... 
>>> <mailto:bl...@re...>>:
>>>
>>>
>>>> Hello,
>>>>
>>>> I've had issues assigning apache basic auth to allow particular 
>>>> users to
>>>> load particular calendars.  The filename didn't transport properly and
>>>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>>>> 'management.ics'.
>>>>
>>>> I've added the following function to publish.php.
>>>>
>>>>
>>>> function retUser() {
>>>>        if( $_SERVER['PHP_AUTH_USER'] )
>>>>                return $_SERVER['PHP_AUTH_USER'];
>>>>        else
>>>>                return $_SERVER['REMOTE_USER'];
>>>> }
>>>>
>>>>
>>>> and I've modified the follow line of code
>>>>
>>>>                if($dataout =
>>>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>>>
>>>> to..
>>>>
>>>>                if($dataout = 
>>>> fopen($calendar_path.retUser().'.ics','w+')){
>>>>
>>>>
>>>> Now its working great.
>>>>
>>>> Thoughts?
>>>>
>>>> Regards,
>>>>
>>>> Blake
>>>>
>>>> -------------------------------------------------------------------------
>>>> 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... 
>>>> <mailto:Php...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>> -------------------------------------------------------------------------
>> 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
>
> =====================================
>
> Jim Hu
>
> Associate Professor
>
> Dept. of Biochemistry and Biophysics
>
> 2128 TAMU
>
> Texas A&M Univ.
>
> College Station, TX 77843-2128
>
> 979-862-4054
>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> 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
>   

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

[Tony | \Zearin\ <ze...@us...>]

Blake Cornell wrote:
> HA!
>
> My over cite regarding the svn vs cvs discussion.  SVN is nice although 
> not for the timid.  Its an ideal free dev environment.
>
> -Blake
>   
Has anyone checked out the new version control system called Bazaar 
<http://bazaar-vcs.org>?

It's from the people who made Ubuntu.  They also have an excellent open 
source software hosting setup called Launchpad <https://launchpad.net>, 
which accepts brand new projects or can mirror existing projects hosted 
elsewhere (including SourceForge). 

It's *extremely* usable.  Might take the anxiety out of trying out new 
systems (like SF's SVN for one). :)

-- Tony

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

[Wesley M. <we...@we...>]

Hi,

I thought all the SF stuff automatically got moved over to SVN a while  
back. Guess I didn't pay much attention.

Blake, would it make some sense to try and build out a "default"  
calendar file setting for users via the configuration file? I think it  
might already be implicitly defined through the calendars you're  
supposed to be able to see when you authenticate. Maybe the first  
calendar indicated in the list.

The only reason I'm thinking of it along these lines instead of  
specifically to username is choosing the default calendar makes things  
a little more flexible and is likely to apply to more deployments.

I don't think publish.php is that integrated with the rest of the  
authentication stuff, but I haven't looked at it myself as I never  
used it. If it isn't integrated, perhaps it should be. And then some  
things would be gained.

I'm not entirely sure about the write permissions though....

Later,
Wes

Quoting Jim Hu <ji...@ta...>:

> Did someone just volunteer to migrate the cvs to svn?  ;)
>
> Seriously, I would be in favor... but I haven't figured out how to use
> the sourceforge svn - I'm barely learning how to work with a local svn
> repository.
>
> JH
>
> On Feb 21, 2008, at 8:35 AM, Blake Cornell wrote:
>
>> Hey Wes,
>>
>> As far as committing it to the svn repo, the only feasible way to do
>> that would be via a new config var with an if switch at the proper
>> location.  It wouldn't require much yet would offer the additional
>> option.  I would describe it in a PRD as `Adhere Calendar Name to User
>> Name`.  In the least, I figure I offer up my experience.
>>
>> Is there another way to allow multiple users authenticated write to  user
>> specific files within the same directory?  I know there is the sub
>> directory way thats described in the wiki.
>>
>> Do you think this added logic can perform more to current  specifications
>> rather then simply hacking the publish code?
>>
>> Thanks,
>>
>> Blake
>>
>>
>> Wesley Miaw wrote:
>>> Hi Blake,
>>>
>>> That change seems to make it do something completely different than
>>> before.... But if that is what works for you I don't see any problem.
>>> It doesn't seem like something that should get merged into the
>>> repository though.
>>>
>>> Regards,
>>> Wes
>>>
>>> Quoting Blake Cornell <bl...@re...>:
>>>
>>>
>>>> Hello,
>>>>
>>>> I've had issues assigning apache basic auth to allow particular  users to
>>>> load particular calendars.  The filename didn't transport properly  and
>>>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>>>> 'management.ics'.
>>>>
>>>> I've added the following function to publish.php.
>>>>
>>>>
>>>> function retUser() {
>>>>       if( $_SERVER['PHP_AUTH_USER'] )
>>>>               return $_SERVER['PHP_AUTH_USER'];
>>>>       else
>>>>               return $_SERVER['REMOTE_USER'];
>>>> }
>>>>
>>>>
>>>> and I've modified the follow line of code
>>>>
>>>>               if($dataout =
>>>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>>>
>>>> to..
>>>>
>>>>               if($dataout =  fopen($calendar_path.retUser().'.ics','w+')){
>>>>
>>>>
>>>> Now its working great.
>>>>
>>>> Thoughts?
>>>>
>>>> Regards,
>>>>
>>>> Blake
>>>>
>>>> -------------------------------------------------------------------------
>>>> 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
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>> -------------------------------------------------------------------------
>> 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
>
> =====================================
> Jim Hu
> Associate Professor
> Dept. of Biochemistry and Biophysics
> 2128 TAMU
> Texas A&M Univ.
> College Station, TX 77843-2128
> 979-862-4054



-- 
Wesley Miaw
http://www.wesman.net/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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

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

Hey Wes,

I believe your speaking of the apache_map config variable.  That is 
likely the current way to do what I'm doing.  It also allows multiple 
files per user.

Currently, I'm allowing all calendars to be viewable by 
non-authenticated users.  Only authenticated users can write to their 
user names calendar.  Seems similar although subtly different.

publish.php seems to be somewhat segmented to me, FYI.

Thoughts?

-Blake

Wesley Miaw wrote:
> Hi,
>
> I thought all the SF stuff automatically got moved over to SVN a while  
> back. Guess I didn't pay much attention.
>
> Blake, would it make some sense to try and build out a "default"  
> calendar file setting for users via the configuration file? I think it  
> might already be implicitly defined through the calendars you're  
> supposed to be able to see when you authenticate. Maybe the first  
> calendar indicated in the list.
>
> The only reason I'm thinking of it along these lines instead of  
> specifically to username is choosing the default calendar makes things  
> a little more flexible and is likely to apply to more deployments.
>
> I don't think publish.php is that integrated with the rest of the  
> authentication stuff, but I haven't looked at it myself as I never  
> used it. If it isn't integrated, perhaps it should be. And then some  
> things would be gained.
>
> I'm not entirely sure about the write permissions though....
>
> Later,
> Wes
>
> Quoting Jim Hu <ji...@ta...>:
>
>   
>> Did someone just volunteer to migrate the cvs to svn?  ;)
>>
>> Seriously, I would be in favor... but I haven't figured out how to use
>> the sourceforge svn - I'm barely learning how to work with a local svn
>> repository.
>>
>> JH
>>
>> On Feb 21, 2008, at 8:35 AM, Blake Cornell wrote:
>>
>>     
>>> Hey Wes,
>>>
>>> As far as committing it to the svn repo, the only feasible way to do
>>> that would be via a new config var with an if switch at the proper
>>> location.  It wouldn't require much yet would offer the additional
>>> option.  I would describe it in a PRD as `Adhere Calendar Name to User
>>> Name`.  In the least, I figure I offer up my experience.
>>>
>>> Is there another way to allow multiple users authenticated write to  user
>>> specific files within the same directory?  I know there is the sub
>>> directory way thats described in the wiki.
>>>
>>> Do you think this added logic can perform more to current  specifications
>>> rather then simply hacking the publish code?
>>>
>>> Thanks,
>>>
>>> Blake
>>>
>>>
>>> Wesley Miaw wrote:
>>>       
>>>> Hi Blake,
>>>>
>>>> That change seems to make it do something completely different than
>>>> before.... But if that is what works for you I don't see any problem.
>>>> It doesn't seem like something that should get merged into the
>>>> repository though.
>>>>
>>>> Regards,
>>>> Wes
>>>>
>>>> Quoting Blake Cornell <bl...@re...>:
>>>>
>>>>
>>>>         
>>>>> Hello,
>>>>>
>>>>> I've had issues assigning apache basic auth to allow particular  users to
>>>>> load particular calendars.  The filename didn't transport properly  and
>>>>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>>>>> 'management.ics'.
>>>>>
>>>>> I've added the following function to publish.php.
>>>>>
>>>>>
>>>>> function retUser() {
>>>>>       if( $_SERVER['PHP_AUTH_USER'] )
>>>>>               return $_SERVER['PHP_AUTH_USER'];
>>>>>       else
>>>>>               return $_SERVER['REMOTE_USER'];
>>>>> }
>>>>>
>>>>>
>>>>> and I've modified the follow line of code
>>>>>
>>>>>               if($dataout =
>>>>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>>>>
>>>>> to..
>>>>>
>>>>>               if($dataout =  fopen($calendar_path.retUser().'.ics','w+')){
>>>>>
>>>>>
>>>>> Now its working great.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Blake
>>>>>
>>>>> -------------------------------------------------------------------------
>>>>> 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
>>>>>
>>>>>
>>>>>           
>>>>
>>>>
>>>>         
>>> -------------------------------------------------------------------------
>>> 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
>>>       
>> =====================================
>> Jim Hu
>> Associate Professor
>> Dept. of Biochemistry and Biophysics
>> 2128 TAMU
>> Texas A&M Univ.
>> College Station, TX 77843-2128
>> 979-862-4054
>>     
>
>
>
>   

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

[Wesley M. <we...@we...>]

Hi Blake,

Hm, that is a subtle difference. Is there not some combination of  
username/everyone calendar list configuration that lets you let  
everyone (authenticated or not) see all calendars, but also associates  
a specific user with a specific calendar? I think if calendars aren't  
in the blacklist, but are in the main list, there's no restriction  
anyway?

I've been pretty inactive in PHP iCalendar since I stopped using it so  
much and have started working on different projects, which is why a  
lot of my suggestions are in the form of questions. I'm just an  
annoying unsolicited advisor now.

Quoting Blake Cornell <bl...@re...>:

> Hey Wes,
>
> I believe your speaking of the apache_map config variable.  That is
> likely the current way to do what I'm doing.  It also allows multiple
> files per user.
>
> Currently, I'm allowing all calendars to be viewable by
> non-authenticated users.  Only authenticated users can write to their
> user names calendar.  Seems similar although subtly different.
>
> publish.php seems to be somewhat segmented to me, FYI.
>
> Thoughts?
>
> -Blake
>
> Wesley Miaw wrote:
>> Hi,
>>
>> I thought all the SF stuff automatically got moved over to SVN a while
>> back. Guess I didn't pay much attention.
>>
>> Blake, would it make some sense to try and build out a "default"
>> calendar file setting for users via the configuration file? I think it
>> might already be implicitly defined through the calendars you're
>> supposed to be able to see when you authenticate. Maybe the first
>> calendar indicated in the list.
>>
>> The only reason I'm thinking of it along these lines instead of
>> specifically to username is choosing the default calendar makes things
>> a little more flexible and is likely to apply to more deployments.
>>
>> I don't think publish.php is that integrated with the rest of the
>> authentication stuff, but I haven't looked at it myself as I never
>> used it. If it isn't integrated, perhaps it should be. And then some
>> things would be gained.
>>
>> I'm not entirely sure about the write permissions though....
>>
>> Later,
>> Wes
>>
>> Quoting Jim Hu <ji...@ta...>:
>>
>>
>>> Did someone just volunteer to migrate the cvs to svn?  ;)
>>>
>>> Seriously, I would be in favor... but I haven't figured out how to use
>>> the sourceforge svn - I'm barely learning how to work with a local svn
>>> repository.
>>>
>>> JH
>>>
>>> On Feb 21, 2008, at 8:35 AM, Blake Cornell wrote:
>>>
>>>
>>>> Hey Wes,
>>>>
>>>> As far as committing it to the svn repo, the only feasible way to do
>>>> that would be via a new config var with an if switch at the proper
>>>> location.  It wouldn't require much yet would offer the additional
>>>> option.  I would describe it in a PRD as `Adhere Calendar Name to User
>>>> Name`.  In the least, I figure I offer up my experience.
>>>>
>>>> Is there another way to allow multiple users authenticated write to  user
>>>> specific files within the same directory?  I know there is the sub
>>>> directory way thats described in the wiki.
>>>>
>>>> Do you think this added logic can perform more to current  specifications
>>>> rather then simply hacking the publish code?
>>>>
>>>> Thanks,
>>>>
>>>> Blake
>>>>
>>>>
>>>> Wesley Miaw wrote:
>>>>
>>>>> Hi Blake,
>>>>>
>>>>> That change seems to make it do something completely different than
>>>>> before.... But if that is what works for you I don't see any problem.
>>>>> It doesn't seem like something that should get merged into the
>>>>> repository though.
>>>>>
>>>>> Regards,
>>>>> Wes
>>>>>
>>>>> Quoting Blake Cornell <bl...@re...>:
>>>>>
>>>>>
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I've had issues assigning apache basic auth to allow particular  
>>>>>>   users to
>>>>>> load particular calendars.  The filename didn't transport properly  and
>>>>>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>>>>>> 'management.ics'.
>>>>>>
>>>>>> I've added the following function to publish.php.
>>>>>>
>>>>>>
>>>>>> function retUser() {
>>>>>>       if( $_SERVER['PHP_AUTH_USER'] )
>>>>>>               return $_SERVER['PHP_AUTH_USER'];
>>>>>>       else
>>>>>>               return $_SERVER['REMOTE_USER'];
>>>>>> }
>>>>>>
>>>>>>
>>>>>> and I've modified the follow line of code
>>>>>>
>>>>>>               if($dataout =
>>>>>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>>>>>
>>>>>> to..
>>>>>>
>>>>>>               if($dataout =    
>>>>>> fopen($calendar_path.retUser().'.ics','w+')){
>>>>>>
>>>>>>
>>>>>> Now its working great.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Blake
>>>>>>
>>>>>> -------------------------------------------------------------------------
>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> -------------------------------------------------------------------------
>>>> 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
>>>>
>>> =====================================
>>> Jim Hu
>>> Associate Professor
>>> Dept. of Biochemistry and Biophysics
>>> 2128 TAMU
>>> Texas A&M Univ.
>>> College Station, TX 77843-2128
>>> 979-862-4054
>>>
>>
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> 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
>



-- 
Wesley Miaw
http://www.wesman.net/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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

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

Wes,

NICE!!!  I'm trying to gain consensus for best practices.  You've been 
quite helpful so keep being the 'annoying unsolicited adviser' even 
though I inquired initially.

This was my dilemma, in short:

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).

Regardless, what projects are you devoting yourself too?

Thanks,

Blake

Also, as far as being unsolicited... You were responding to my inquiry, 
so your simply

Wesley Miaw wrote:
> Hi Blake,
>
> Hm, that is a subtle difference. Is there not some combination of  
> username/everyone calendar list configuration that lets you let  
> everyone (authenticated or not) see all calendars, but also associates  
> a specific user with a specific calendar? I think if calendars aren't  
> in the blacklist, but are in the main list, there's no restriction  
> anyway?
>
> I've been pretty inactive in PHP iCalendar since I stopped using it so  
> much and have started working on different projects, which is why a  
> lot of my suggestions are in the form of questions. I'm just an  
> annoying unsolicited advisor now.
>
> Quoting Blake Cornell <bl...@re...>:
>
>   
>> Hey Wes,
>>
>> I believe your speaking of the apache_map config variable.  That is
>> likely the current way to do what I'm doing.  It also allows multiple
>> files per user.
>>
>> Currently, I'm allowing all calendars to be viewable by
>> non-authenticated users.  Only authenticated users can write to their
>> user names calendar.  Seems similar although subtly different.
>>
>> publish.php seems to be somewhat segmented to me, FYI.
>>
>> Thoughts?
>>
>> -Blake
>>
>> Wesley Miaw wrote:
>>     
>>> Hi,
>>>
>>> I thought all the SF stuff automatically got moved over to SVN a while
>>> back. Guess I didn't pay much attention.
>>>
>>> Blake, would it make some sense to try and build out a "default"
>>> calendar file setting for users via the configuration file? I think it
>>> might already be implicitly defined through the calendars you're
>>> supposed to be able to see when you authenticate. Maybe the first
>>> calendar indicated in the list.
>>>
>>> The only reason I'm thinking of it along these lines instead of
>>> specifically to username is choosing the default calendar makes things
>>> a little more flexible and is likely to apply to more deployments.
>>>
>>> I don't think publish.php is that integrated with the rest of the
>>> authentication stuff, but I haven't looked at it myself as I never
>>> used it. If it isn't integrated, perhaps it should be. And then some
>>> things would be gained.
>>>
>>> I'm not entirely sure about the write permissions though....
>>>
>>> Later,
>>> Wes
>>>
>>> Quoting Jim Hu <ji...@ta...>:
>>>
>>>
>>>       
>>>> Did someone just volunteer to migrate the cvs to svn?  ;)
>>>>
>>>> Seriously, I would be in favor... but I haven't figured out how to use
>>>> the sourceforge svn - I'm barely learning how to work with a local svn
>>>> repository.
>>>>
>>>> JH
>>>>
>>>> On Feb 21, 2008, at 8:35 AM, Blake Cornell wrote:
>>>>
>>>>
>>>>         
>>>>> Hey Wes,
>>>>>
>>>>> As far as committing it to the svn repo, the only feasible way to do
>>>>> that would be via a new config var with an if switch at the proper
>>>>> location.  It wouldn't require much yet would offer the additional
>>>>> option.  I would describe it in a PRD as `Adhere Calendar Name to User
>>>>> Name`.  In the least, I figure I offer up my experience.
>>>>>
>>>>> Is there another way to allow multiple users authenticated write to  user
>>>>> specific files within the same directory?  I know there is the sub
>>>>> directory way thats described in the wiki.
>>>>>
>>>>> Do you think this added logic can perform more to current  specifications
>>>>> rather then simply hacking the publish code?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Blake
>>>>>
>>>>>
>>>>> Wesley Miaw wrote:
>>>>>
>>>>>           
>>>>>> Hi Blake,
>>>>>>
>>>>>> That change seems to make it do something completely different than
>>>>>> before.... But if that is what works for you I don't see any problem.
>>>>>> It doesn't seem like something that should get merged into the
>>>>>> repository though.
>>>>>>
>>>>>> Regards,
>>>>>> Wes
>>>>>>
>>>>>> Quoting Blake Cornell <bl...@re...>:
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> Hello,
>>>>>>>
>>>>>>> I've had issues assigning apache basic auth to allow particular  
>>>>>>>   users to
>>>>>>> load particular calendars.  The filename didn't transport properly  and
>>>>>>> thus creating a '.ics' file instead of ex. 'engineering.ics' or
>>>>>>> 'management.ics'.
>>>>>>>
>>>>>>> I've added the following function to publish.php.
>>>>>>>
>>>>>>>
>>>>>>> function retUser() {
>>>>>>>       if( $_SERVER['PHP_AUTH_USER'] )
>>>>>>>               return $_SERVER['PHP_AUTH_USER'];
>>>>>>>       else
>>>>>>>               return $_SERVER['REMOTE_USER'];
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> and I've modified the follow line of code
>>>>>>>
>>>>>>>               if($dataout =
>>>>>>> fopen($calendar_path.$calendar_name.'.ics','w+')){
>>>>>>>
>>>>>>> to..
>>>>>>>
>>>>>>>               if($dataout =    
>>>>>>> fopen($calendar_path.retUser().'.ics','w+')){
>>>>>>>
>>>>>>>
>>>>>>> Now its working great.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Blake
>>>>>>>
>>>>>>> -------------------------------------------------------------------------
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>>
>>>>>>             
>>>>> -------------------------------------------------------------------------
>>>>> 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
>>>>>
>>>>>           
>>>> =====================================
>>>> Jim Hu
>>>> Associate Professor
>>>> Dept. of Biochemistry and Biophysics
>>>> 2128 TAMU
>>>> Texas A&M Univ.
>>>> College Station, TX 77843-2128
>>>> 979-862-4054
>>>>
>>>>         
>>>
>>>
>>>       
>> -------------------------------------------------------------------------
>> 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
>>
>>     
>
>
>
>   

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

[Jo R. <jr...@ne...>]

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.

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness

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

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

Hey Jo,

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.
>
>   

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

[Jo R. <jr...@ne...>]

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

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness

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
>>     
>
>   

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

[Jo R. <jr...@ne...>]

No patches attached?  (I don't have the original e-mail around any more)

On Mar 5, 2008, at 1:02 PM, Blake Cornell wrote:
> 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
>>>
>>
>>
>
> --- config.inc.php	2008-03-05 15:58:31.000000000 -0500
> +++ config.inc-dist.php	2007-02-16 01:34:10.000000000 -0500
> @@ -99,5 +99,4 @@
>  $apache_map['user3'] = array('');			// given any login/logout  
> options. Calendar names not include the .ics suffix.
>  $apache_map['user4'] = array('');			// Example: $apache_map 
> ['username'] = array('Calendar1', 'Calendar2');
>  // add more lines as necessary
> -$lock_cal_auth_user = '1';      // renames apache authenticated  
> users to publish calendars by their username only
>  ?>
> --- publish.php	2007-05-18 16:46:32.000000000 -0400
> +++ publish.php.1	2008-03-05 15:56:45.000000000 -0500
> @@ -211,7 +211,13 @@
>  		}
>
>  		// write to file
> -		if($dataout = fopen($calendar_path.$calendar_name.'.ics','w+')){
> +		$curCal = '';
> +		if($lock_cal_auth_user == '1') {
> +			$curCal = $calendar_path.retUser();
> +		}else{
> +			$curCal = $calendar_path.$calendar_name;
> +		}
> +		if($dataout = fopen($curCal.'.ics','w+')){
>  			fputs($dataout, $data, strlen($data) );
>  			@fclose($dataout);
>  		}else{
> @@ -261,4 +267,12 @@
>  		fputs($logfile, $logline, strlen($logline) );
>  	}
>  }
> +
> +function retUser() {
> +	if($_SERVER['PHP_AUTH_USER'] ) {
> +		return $_SERVER['PHP_AUTH_USER'];
> +	}else{
> +		return $_SERVER['REMOTE_USER'];
> +	}
> +}
>  ?>
> ---------------------------------------------------------------------- 
> ---
> 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

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness

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

[Jo R. <jr...@ne...>]

On Feb 21, 2008, at 9:58 AM, Wesley Miaw wrote:
> I don't think publish.php is that integrated with the rest of the
> authentication stuff, but I haven't looked at it myself as I never
> used it. If it isn't integrated, perhaps it should be. And then some
> things would be gained.

It is completely separate.  When I took it over it was "unsupported",  
and Jim and I did some work to make it work more seamlessly with the  
main code.

However, it can't use the main system's authentication because it  
needs to support things the main auth code doesn't, and the main auth  
code is too tightly intertwined to separate cleanly enough to fix.   
Search back and you'll find my comments back when I first tried to do  
this.

In short, the entire auth system needs to be modularized (the entire  
codebase, actually) before pulling these together is possible.   
That's why the push towards a redesign for v3.

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness

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

[Jo R. <jr...@ne...>]

As the current maintainer of publish.php, there is no possible way I  
could implement this patch.  Forcing a given login to always  
overwrite the same file is completely backwards to me.  It would also  
destroy functionality that many of us use.  I, for instance, upload 5  
different calendars under my single login.

I'd be happy to solve your difficulty in some other way, if you'd  
explain the nature of the problem you're having.

On Feb 20, 2008, at 9:15 AM, Blake Cornell wrote:
> I've had issues assigning apache basic auth to allow particular  
> users to
> load particular calendars.  The filename didn't transport properly and
> thus creating a '.ics' file instead of ex. 'engineering.ics' or
> 'management.ics'.
>
> I've added the following function to publish.php.
>
>
> function retUser() {
>         if( $_SERVER['PHP_AUTH_USER'] )
>                 return $_SERVER['PHP_AUTH_USER'];
>         else
>                 return $_SERVER['REMOTE_USER'];
> }
>
>
> and I've modified the follow line of code
>
>                 if($dataout =
> fopen($calendar_path.$calendar_name.'.ics','w+')){
>
> to..
>
>                 if($dataout = fopen($calendar_path.retUser 
> ().'.ics','w+')){
>
>
> Now its working great.
>
> Thoughts?
>
> Regards,
>
> Blake
>
> ---------------------------------------------------------------------- 
> ---
> 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

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness