phpwebsite-developers

[Phpwebsite-developers] File Cabinet changes in subversion

[Matthew M. <ma...@tu...>]

Hi all,

I have finally committed the File Cabinet rewrite that has kept me busy
for a while.

My hope is that some of you devs can help test and supply feedback. You
will need to perform a checkout or export from subversion.

Please keep the following in mind:

- It is not finished. Do not use on a production site.
- It is not completely secure - I need to test all the permissions.
- It may not work in all browsers. I have only tested in
  Firefox/Linux so far.
- The update has not been tested. I plan on doing so tomorrow.

If you wish to help, I recommend a fresh install.

If it doesn't work and you can see why, email me and let me know. Check
back with subversion as I will be testing and fixing stuff tomorrow. I
can use feedback on usability and functionality. If you want to help
with the update, try running it and letting me know where it fails. Make
sure you are backing up file,images, and database before performing the
update.

Once I get File Cabinet squared away, I will do the language overhaul
(thanks for the feedback on that by the way).

After that, I will start chopping away on bugs and feature requests.

When the above is complete, we will release 1.2.0.

Thank you,
Matt
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] File Cabinet changes in subversion

[Verdon V. <ve...@gm...>]

Hmm,

So if I have an install done from svn on Friday, that I intend to  
train a client with late this week, is it safe to just svn update  
now, or will I also need to boost something for database changes?

I have to train two different clients late this week in sites using  
phpws 1.x. I'd sure hate train them in something that will be  
completely different next week ;-)

Any advice?
verdon


On 2-Apr-07, at 3:07 PM, Matthew McNaney wrote:

> Hi all,
>
> I have finally committed the File Cabinet rewrite that has kept me  
> busy
> for a while.
>
> My hope is that some of you devs can help test and supply feedback.  
> You
> will need to perform a checkout or export from subversion.
>
> Please keep the following in mind:
>
> - It is not finished. Do not use on a production site.
> - It is not completely secure - I need to test all the permissions.
> - It may not work in all browsers. I have only tested in
>   Firefox/Linux so far.
> - The update has not been tested. I plan on doing so tomorrow.
>
> If you wish to help, I recommend a fresh install.
>
> If it doesn't work and you can see why, email me and let me know.  
> Check
> back with subversion as I will be testing and fixing stuff tomorrow. I
> can use feedback on usability and functionality. If you want to help
> with the update, try running it and letting me know where it fails.  
> Make
> sure you are backing up file,images, and database before performing  
> the
> update.
>
> Once I get File Cabinet squared away, I will do the language overhaul
> (thanks for the feedback on that by the way).
>
> After that, I will start chopping away on bugs and feature requests.
>
> When the above is complete, we will release 1.2.0.
>
> Thank you,
> Matt
> -- 
> Matthew McNaney
> Electronic Student Services
> Appalachian State University
> http://phpwebsite.appstate.edu
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] File Cabinet changes in subversion

[Matthew M. <ma...@tu...>]

Verdon,

Friday is a ways away. If I get good feedback, File Cabinet may be ready
by then.

FC now uses folders instead of trying to get the user to pick
directories to save the images in. I think it is easier to use than the
old method.

Give it a try and let me know what you think. Come Thursday we can talk
about what to do next. :)

Matt

On Mon, 2007-04-02 at 15:46 -0400, Verdon Vaillancourt wrote:
> Hmm,
> 
> So if I have an install done from svn on Friday, that I intend to  
> train a client with late this week, is it safe to just svn update  
> now, or will I also need to boost something for database changes?
> 
> I have to train two different clients late this week in sites using  
> phpws 1.x. I'd sure hate train them in something that will be  
> completely different next week ;-)
> 
> Any advice?
> verdon
> 
> 
> On 2-Apr-07, at 3:07 PM, Matthew McNaney wrote:
> 
> > Hi all,
> >
> > I have finally committed the File Cabinet rewrite that has kept me  
> > busy
> > for a while.
> >
> > My hope is that some of you devs can help test and supply feedback.  
> > You
> > will need to perform a checkout or export from subversion.
> >
> > Please keep the following in mind:
> >
> > - It is not finished. Do not use on a production site.
> > - It is not completely secure - I need to test all the permissions.
> > - It may not work in all browsers. I have only tested in
> >   Firefox/Linux so far.
> > - The update has not been tested. I plan on doing so tomorrow.
> >
> > If you wish to help, I recommend a fresh install.
> >
> > If it doesn't work and you can see why, email me and let me know.  
> > Check
> > back with subversion as I will be testing and fixing stuff tomorrow. I
> > can use feedback on usability and functionality. If you want to help
> > with the update, try running it and letting me know where it fails.  
> > Make
> > sure you are backing up file,images, and database before performing  
> > the
> > update.
> >
> > Once I get File Cabinet squared away, I will do the language overhaul
> > (thanks for the feedback on that by the way).
> >
> > After that, I will start chopping away on bugs and feature requests.
> >
> > When the above is complete, we will release 1.2.0.
> >
> > Thank you,
> > Matt
> > -- 
> > Matthew McNaney
> > Electronic Student Services
> > Appalachian State University
> > http://phpwebsite.appstate.edu
> >
> >
> > ---------------------------------------------------------------------- 
> > ---
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to  
> > share your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php? 
> > page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

[Phpwebsite-developers] Strangeness with caching

[Verdon V. <ve...@gm...>]

Hi,

Just a heads-up, this struck me as curious once I sorted it out...

I am developing two phpws 1.x sites concurrently on different  
subdomains of my server. One of them is at devsite1.mydomain.com and  
the other is at devsite2.mydomain.com Both are using a custom theme  
but of the same name.

I was finding that when I made a change to the theme.tpl file in one  
site, the other site also seemed to get the changes applied when  
viewed in a browser, even though the .tpl files in each site were  
quite different.

This confused the heck out of me and after fiddling with any possible  
local cache, my php accelorator caches, and anything else I could  
think of, I found the following switch in /config/core/config.php and  
disabled it.

define('ALLOW_CACHE_LITE', TRUE);
define('ALLOW_SIGMA_CACHE', FALSE);   // << this was the problem
define('CACHE_LIFETIME', 3600);
define('CACHE_DIRECTORY', '/tmp/');

Once I identified it, the fix was easy enough. I suppose I should  
just change the cache directory, but I thought it curious that it  
would confuse the two subdomain's cached files. I wonder what it's  
doing to the data cache, CACHE_LITE?

rgds,
verdon

Re: [Phpwebsite-developers] Strangeness with caching

[<ma...@tu...>]

This rings a bell. I don't think the PEAR caching labels template cache
files with the same name regardless of their location. Please bug it on sf
and I'll try and find a work around.

Matt

> Hi,
>
> Just a heads-up, this struck me as curious once I sorted it out...
>
> I am developing two phpws 1.x sites concurrently on different
> subdomains of my server. One of them is at devsite1.mydomain.com and
> the other is at devsite2.mydomain.com Both are using a custom theme
> but of the same name.
>
> I was finding that when I made a change to the theme.tpl file in one
> site, the other site also seemed to get the changes applied when
> viewed in a browser, even though the .tpl files in each site were
> quite different.
>
> This confused the heck out of me and after fiddling with any possible
> local cache, my php accelorator caches, and anything else I could
> think of, I found the following switch in /config/core/config.php and
> disabled it.
>
> define('ALLOW_CACHE_LITE', TRUE);
> define('ALLOW_SIGMA_CACHE', FALSE);   // << this was the problem
> define('CACHE_LIFETIME', 3600);
> define('CACHE_DIRECTORY', '/tmp/');
>
> Once I identified it, the fix was easy enough. I suppose I should
> just change the cache directory, but I thought it curious that it
> would confuse the two subdomain's cached files. I wonder what it's
> doing to the data cache, CACHE_LITE?
>
> rgds,
> verdon
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

Re: [Phpwebsite-developers] Strangeness with caching

[Shaun M. <sh...@ae...>]

On 9 Apr 2007, at 17:11, ma...@tu... wrote:

> This rings a bell. I don't think the PEAR caching labels template  
> cache
> files with the same name regardless of their location. Please bug  
> it on sf
> and I'll try and find a work around.

Are these the .it files in /tmp?

eg...

/tmp/home__userid__public_html__mod__block__templates__admin.tpl.it

or

/tmp/javascript__ajax__head.js.it


Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk

Re: [Phpwebsite-developers] Strangeness with caching

[Verdon V. <ve...@ve...>]

I would imagine so... in my case, there's also a whole bunch

templates__filecabinet__manager__pick.tpl.it
templates__layout__themes.tpl.it
templates__users__forms__authorization.tpl.it

which I imagine are the ones causing trouble as they don't  
differentiate between various user accounts.

On a side note: I suspected this might have been some of the trouble  
I was having with the new filecabinet and clipping and permissions.  
Although the behaviour is different with caching off, I am still not  
able to make clipping or permissions work in the new FC.

verdon


On 9-Apr-07, at 12:33 PM, Shaun Murray wrote:

>
> On 9 Apr 2007, at 17:11, ma...@tu... wrote:
>
>> This rings a bell. I don't think the PEAR caching labels template
>> cache
>> files with the same name regardless of their location. Please bug
>> it on sf
>> and I'll try and find a work around.
>
> Are these the .it files in /tmp?
>
> eg...
>
> /tmp/home__userid__public_html__mod__block__templates__admin.tpl.it
>
> or
>
> /tmp/javascript__ajax__head.js.it
>
>
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> aegis hosting - http://www.aegishosting.co.uk
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] Strangeness with caching

[Shaun M. <sh...@ae...>]

How about taking them out of /tmp and putting them in a cache folder  
local to the branch using http://pear.php.net/manual/en/ 
package.html.html-template-sigma.html-template-sigma.setcacheroot.php ?


Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk

Re: [Phpwebsite-developers] Strangeness with caching

[Verdon V. <ve...@gm...>]

Yes, that config option is already there, just not default. Of  
course, whatever directory is configured needs to be writable by the  
webserver user. I tested with a dir that was user:user 755 and  
although no errors were produced, no caching occurred.

verdon


On 9-Apr-07, at 2:22 PM, Shaun Murray wrote:

> How about taking them out of /tmp and putting them in a cache folder
> local to the branch using http://pear.php.net/manual/en/
> package.html.html-template-sigma.html-template- 
> sigma.setcacheroot.php ?
>
>
> Shaun

Re: [Phpwebsite-developers] Strangeness with caching

[Matthew M. <ma...@tu...>]

I have committed some changes to the Template.php file.

You will need to add
define('CACHE_TPL_LOCALLY', true);
to your config/core/config.php file.

You will also need to create a writable directory in templates named
"cache":
templates/cache/

If the define is true, the template caching will be saved locally. If
false, it pops back to the /tmp/ directory (or whatever is set in
config.php). Note that if the define is not set in the config.php file,
Template assumes it as false. This will prevent breakage if people don't
update their config.php file.

Please test.

Thanks,
Matt


On Mon, 2007-04-09 at 14:48 -0400, Verdon Vaillancourt wrote:
> Yes, that config option is already there, just not default. Of  
> course, whatever directory is configured needs to be writable by the  
> webserver user. I tested with a dir that was user:user 755 and  
> although no errors were produced, no caching occurred.
> 
> verdon
> 
> 
> On 9-Apr-07, at 2:22 PM, Shaun Murray wrote:
> 
> > How about taking them out of /tmp and putting them in a cache folder
> > local to the branch using http://pear.php.net/manual/en/
> > package.html.html-template-sigma.html-template- 
> > sigma.setcacheroot.php ?
> >
> >
> > Shaun
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu