phpicalendar-devel — Mailing list for PHP iCalendar Developers

Re: [PHPiCalendar-DEV] I'm bowing out from the forums.

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

OK, after some back and forth with the vBulletin support folks, the  
problem on the bbs is fixed.  It turns out that it's a cache problem -  
when you log in and goes back to that URL, the browser may try to use  
a cached copy that has the login form instead of the new version that  
redirects to the edit form.  The fix is to force no caching via the  
html headers.  I hope this doesn't make server load go up too much.

I hope Jo will come back - I really need help dealing with publish  
support requests!

Jim


On Mar 13, 2008, at 4:50 PM, Jo Rhett wrote:

> I'm sorry, but I'm not going to play with the forums any more.  You  
> go,
> it says you aren't logged in.  You log in, it says thank you, then  
> puts
> you back on the login page.
>
> This means that every time I go, I have to use the search to find the
> original thread to reply to it.
>
> It's a stupid, easily reproducable bug.  Fix it, and I'll play in the
> forums again.
>
> -------- Original Message --------
> Subject: Reply to thread 'A small utility to upload iCal calendars'
> Date: Thu, 13 Mar 2008 16:29:59 -0500 (CDT)
> From: phpicalendar Forums <php...@gm...>
> To: jr...@ne...
>
> Dear jorhett,
>
> blizzard has just replied to a thread you have subscribed to  
> entitled -
> A small utility to upload iCal calendars - in the Publish/Subscribe
> problems forum of phpicalendar Forums.
>
> This thread is located at:
> http://phpicalendar.org/forums/showthread.php?t=1216&goto=newpost
>
> Here is the message that has just been posted:
> ***************
> Hi there,
>
> I'd really like to get this program working, but I cannot seem to make
> that work for "Managed Users" in 10.3.9.
>
> I keep adding the application to their allowed list, and it shows up
> checked, yet when I try to open it, the Finder says not allowed,  
> contact
> your administrator.
>
> Any ideas?
>
> Cheers!
> ***************
>
>
> There may also be other replies, but you will not receive any more
> notifications until you visit the forum again.
>
> All the best,
> phpicalendar Forums
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Unsubscription information:
>
> To unsubscribe from this thread, please visit this page:
> http://phpicalendar.org/forums/subscription.php?do=removesubscription&type=thread&subscriptionid=102&auth=27ceab68cd587a5932dddf14aa750b81
>
> To unsubscribe from ALL threads, please visit this page:
> http://phpicalendar.org/forums/subscription.php?do=viewsubscription&folderid=all
>
> -------------------------------------------------------------------------
> 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] I'm bowing out from the forums.

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

Jo,

I'm really sorry about this.  I've posted a request for help on  
vbulletin.org's forum.  Yes, it's simple and reproducible, but I  
understand the vBulletin codebase even less than our own for  
phpicalendar.  I have noticed that the login works if you ignore the  
form and login using the fields in the upper right corner.  If I don't  
get help from the vBulletin people, I'll see if I can disable the  
nonworking form somehow.

Jim

On Mar 13, 2008, at 4:50 PM, Jo Rhett wrote:

> I'm sorry, but I'm not going to play with the forums any more.  You  
> go,
> it says you aren't logged in.  You log in, it says thank you, then  
> puts
> you back on the login page.
>
> This means that every time I go, I have to use the search to find the
> original thread to reply to it.
>
> It's a stupid, easily reproducable bug.  Fix it, and I'll play in the
> forums again.
>
> -------- Original Message --------
> Subject: Reply to thread 'A small utility to upload iCal calendars'
> Date: Thu, 13 Mar 2008 16:29:59 -0500 (CDT)
> From: phpicalendar Forums <php...@gm...>
> To: jr...@ne...
>
> Dear jorhett,
>
> blizzard has just replied to a thread you have subscribed to  
> entitled -
> A small utility to upload iCal calendars - in the Publish/Subscribe
> problems forum of phpicalendar Forums.
>
> This thread is located at:
> http://phpicalendar.org/forums/showthread.php?t=1216&goto=newpost
>
> Here is the message that has just been posted:
> ***************
> Hi there,
>
> I'd really like to get this program working, but I cannot seem to make
> that work for "Managed Users" in 10.3.9.
>
> I keep adding the application to their allowed list, and it shows up
> checked, yet when I try to open it, the Finder says not allowed,  
> contact
> your administrator.
>
> Any ideas?
>
> Cheers!
> ***************
>
>
> There may also be other replies, but you will not receive any more
> notifications until you visit the forum again.
>
> All the best,
> phpicalendar Forums
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Unsubscription information:
>
> To unsubscribe from this thread, please visit this page:
> http://phpicalendar.org/forums/subscription.php?do=removesubscription&type=thread&subscriptionid=102&auth=27ceab68cd587a5932dddf14aa750b81
>
> To unsubscribe from ALL threads, please visit this page:
> http://phpicalendar.org/forums/subscription.php?do=viewsubscription&folderid=all
>
> -------------------------------------------------------------------------
> 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

[PHPiCalendar-DEV] I'm bowing out from the forums.

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

I'm sorry, but I'm not going to play with the forums any more.  You go, 
it says you aren't logged in.  You log in, it says thank you, then puts 
you back on the login page.

This means that every time I go, I have to use the search to find the 
original thread to reply to it.

It's a stupid, easily reproducable bug.  Fix it, and I'll play in the 
forums again.

-------- Original Message --------
Subject: Reply to thread 'A small utility to upload iCal calendars'
Date: Thu, 13 Mar 2008 16:29:59 -0500 (CDT)
From: phpicalendar Forums <php...@gm...>
To: jr...@ne...

Dear jorhett,

blizzard has just replied to a thread you have subscribed to entitled - 
A small utility to upload iCal calendars - in the Publish/Subscribe 
problems forum of phpicalendar Forums.

This thread is located at:
http://phpicalendar.org/forums/showthread.php?t=1216&goto=newpost

Here is the message that has just been posted:
***************
Hi there,

I'd really like to get this program working, but I cannot seem to make 
that work for "Managed Users" in 10.3.9.

I keep adding the application to their allowed list, and it shows up 
checked, yet when I try to open it, the Finder says not allowed, contact 
your administrator.

Any ideas?

Cheers!
***************


There may also be other replies, but you will not receive any more 
notifications until you visit the forum again.

All the best,
phpicalendar Forums

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unsubscription information:

To unsubscribe from this thread, please visit this page:
http://phpicalendar.org/forums/subscription.php?do=removesubscription&type=thread&subscriptionid=102&auth=27ceab68cd587a5932dddf14aa750b81

To unsubscribe from ALL threads, please visit this page:
http://phpicalendar.org/forums/subscription.php?do=viewsubscription&folderid=all

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

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

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,

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

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

[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

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

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

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,

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

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

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

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

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

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

[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] Fwd: phpicalendar Forums Contact Us Form - Viewing multiple-day events in one long bar

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

Start off by redoing the existing templates so they use div's and  
span's instead of table elements, I guess. Hardest part will be  
rearranging the hierarchy of things, which is going to be the most  
important when getting things like multi-day events, maybe. I was  
thinking about that a little and I think you'd have to treat  
multi-week events as one event "div" per week....

Quoting "Tony | \"Zearin\"" <ze...@us...>:

> Jo Rhett wrote:
>> On Feb 8, 2008, at 9:31 PM, Wesley Miaw wrote:
>>
>>> Moving to pure CSS actually simplifies things a great deal....
>>>
>>
>> I'd like to see this.  The number of browsers which can't support    
>> this are few.
>>
>
> Hear, here! :)
>
> I would be very happy to help in this regard.  I'm quite comfy with
> CSS. Anyone recommend a good starting point?
>
> -- Z



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

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

Re: [PHPiCalendar-DEV] Fwd: phpicalendar Forums Contact Us Form - Viewing multiple-day events in one long bar

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

Jo Rhett wrote:
> On Feb 8, 2008, at 9:31 PM, Wesley Miaw wrote:
>   
>> Moving to pure CSS actually simplifies things a great deal....
>>     
>
> I'd like to see this.  The number of browsers which can't support  
> this are few.
>   

Hear, here! :)

I would be very happy to help in this regard.  I'm quite comfy with CSS. 

Anyone recommend a good starting point?

-- Z

Re: [PHPiCalendar-DEV] Fwd: phpicalendar Forums Contact Us Form - Viewing multiple-day events in one long bar

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

On Feb 8, 2008, at 9:31 PM, Wesley Miaw wrote:
> Moving to pure CSS actually simplifies things a great deal....

I'd like to see this.  The number of browsers which can't support  
this are few.

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

Re: [PHPiCalendar-DEV] Fwd: phpicalendar Forums Contact Us Form - Viewing multiple-day events in one long bar

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

Hi Jim,

I'm not sure post-processing would work, but I thought briefly about  
doing multi-column td's. However that won't work in the monthly view,  
where you don't really have that "aligned cell" structure for  
individual events. (Well, it might, but I think it'd look ugly.) And  
you'd want it to be consistent across all the different views.

Moving to pure CSS actually simplifies things a great deal....

Later,
Wes

On Feb 8, 2008, at 7:19 PM, Jim Hu wrote:

> Hi Wes.
>
> On Feb 8, 2008, at 7:23 PM, Wesley Miaw wrote:
>
>> Hi Jim,
>>
>> It's been a long time since I looked at the code base, but I think  
>> the
>> issue is events are rendered as discrete elements, and that includes
>> multi-day events. The current Calendar abstraction would need to be
>> used differently so you didn't try rendering each day's events
>> independently, I think. And to actually make it look good, you'd have
>> to switch over to CSS instead of using tables.
>
> I was wondering if we could post-process the table segment with the  
> all-day events to join multiple cells into a colspan.
> My recollection is that this runs into a problem with how a series  
> of multi-day events are tiled within the region.
>
> But yes, definitely not a minor change or I suspect someone would  
> have submitted code to do it.
>
> Jim
>
>
>>
>>
>> Not a minor change, in my opinion.
>>
>> Later,
>> Wes
>>
>> Quoting Jim Hu <ji...@ta...>:
>>
>>> Anyone know how to do this?  I think it would be useful.  The part
>>> about Outlook is irrelevant, IMO.
>>>
>>> Begin forwarded message:
>>>
>>>> From: "Marc Hoffman @ phpicalendar Forums"
>>>> <mho...@mo... >
>>>> Date: February 8, 2008 3:25:54 PM CST
>>>> To: php...@gm...
>>>> Subject: phpicalendar Forums Contact Us Form - Viewing multiple-day
>>>> events in one long bar
>>>>
>>>> The following message was sent to you via the phpicalendar Forums
>>>> Contact Us form by Marc Hoffman.
>>>>
>>>> --------------------------------
>>>>
>>>> Dear PHPiCalendar Development Team...
>>>>
>>>> We are sharing calendars via Outlook 2007 to PHPicalendar. We can
>>>> get the calendars published. However, for all-day events spanning
>>>> multiple days, Outlook shows these events as a solid bar spanning
>>>> the days in question. When the calendar is published to
>>>> PHPiCalendar, the solid bar is broken up into multiple segments.
>>>> Users in our departments frequently print off calendars, and when
>>>> the events are truncated in this way, people cannot print the
>>>> calendar as a whole.
>>>>
>>>> Is there a way to show these items as solid bars that can be
>>>> printed  and read in "one shot" instead of having to click each  
>>>> day?
>>>>
>>>> Thanks in advance!
>>>>
>>>> Marc
>>>>
>>>> --------------------------------
>>>>
>>>> Referring Page: http://phpicalendar.net/forums/forumdisplay.php? 
>>>> f=48
>>>> IP Address: 207.91.61.52
>>>> User Name: Unregistered
>>>> User ID: 0
>>>
>>> =====================================
>>> 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.
>>
>>
>> -------------------------------------------------------------------------
>> 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
we...@we...

Re: [PHPiCalendar-DEV] Fwd: phpicalendar Forums Contact Us Form - Viewing multiple-day events in one long bar

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

Hi Wes.

On Feb 8, 2008, at 7:23 PM, Wesley Miaw wrote:

> Hi Jim,
>
> It's been a long time since I looked at the code base, but I think the
> issue is events are rendered as discrete elements, and that includes
> multi-day events. The current Calendar abstraction would need to be
> used differently so you didn't try rendering each day's events
> independently, I think. And to actually make it look good, you'd have
> to switch over to CSS instead of using tables.

I was wondering if we could post-process the table segment with the  
all-day events to join multiple cells into a colspan.
My recollection is that this runs into a problem with how a series of  
multi-day events are tiled within the region.

But yes, definitely not a minor change or I suspect someone would have  
submitted code to do it.

Jim


>
>
> Not a minor change, in my opinion.
>
> Later,
> Wes
>
> Quoting Jim Hu <ji...@ta...>:
>
>> Anyone know how to do this?  I think it would be useful.  The part
>> about Outlook is irrelevant, IMO.
>>
>> Begin forwarded message:
>>
>>> From: "Marc Hoffman @ phpicalendar Forums"
>>> <mho...@mo... >
>>> Date: February 8, 2008 3:25:54 PM CST
>>> To: php...@gm...
>>> Subject: phpicalendar Forums Contact Us Form - Viewing multiple-day
>>>  events in one long bar
>>>
>>> The following message was sent to you via the phpicalendar Forums
>>> Contact Us form by Marc Hoffman.
>>>
>>> --------------------------------
>>>
>>> Dear PHPiCalendar Development Team...
>>>
>>> We are sharing calendars via Outlook 2007 to PHPicalendar. We can
>>> get the calendars published. However, for all-day events spanning
>>> multiple days, Outlook shows these events as a solid bar spanning
>>> the days in question. When the calendar is published to
>>> PHPiCalendar, the solid bar is broken up into multiple segments.
>>> Users in our departments frequently print off calendars, and when
>>> the events are truncated in this way, people cannot print the
>>> calendar as a whole.
>>>
>>> Is there a way to show these items as solid bars that can be
>>> printed  and read in "one shot" instead of having to click each day?
>>>
>>> Thanks in advance!
>>>
>>> Marc
>>>
>>> --------------------------------
>>>
>>> Referring Page: http://phpicalendar.net/forums/forumdisplay.php?f=48
>>> IP Address: 207.91.61.52
>>> User Name: Unregistered
>>> User ID: 0
>>
>> =====================================
>> 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.
>
>
> -------------------------------------------------------------------------
> 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