phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] help with time-out on a custom script

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

Verdon,

One method would be to to limit the select results.

For example, 1.0's conversion script pulls data in batches, converts the
batch, then loads the next page. The batch number is incremented and
continues until out of results.

A better solution my be to break from the API and use a select join:

SELECT mod_users.user_id
FROM   mod_users, mod_cstmembers_members
WHERE  expiryDate < $today 
       AND
       mod_cstmembers_members.owner = mod_users.user_id

I would use getCol for the results.
Then I would manually delete on the results,

foreach ($results as $user_id) {
$GLOBALS['core']->query("DELETE mod_groups WHERE user_id=$user_id and
group_id=$group_id");
}

I haven't tried it personally, but I believe mysql 4.0 allows delete
joins so you could skip the select part.

This is all from the top of my head so testing might be necessary :)

Good luck,
Matt

On Sun, 2007-02-04 at 16:31 -0500, Verdon Vaillancourt wrote:
> Hi,
> 
> I'm trying to cobble together something kind of customized to do some  
> maintenance on a phpws 0.10.2 site and am running into timeout  
> errors. I'm hoping someone might be able to suggest an alternative  
> method for me.
> 
> The error is
> PHP Fatal error:  Maximum execution time of 30 seconds exceeded in / 
> home/user/public_html/dev/en/lib/pear/DB/mysql.php on line 316
> 
> The goal of the script is that I have a table with member profiles  
> that include an expiration date. I need a script that can look at  
> that table, find the expired users, then look up the corresponding  
> user and remove them from a couple groups. Eventually, this script  
> will get run via cron. I am just getting started...
> 
> <?php
> 
> require_once("/home/user/public_html/dev/en/conf/config.php");
> define('PHPWS_SOURCE_DIR', $source_dir);
> require_once PHPWS_SOURCE_DIR . 'security.php';
> require_once PHPWS_SOURCE_DIR . 'core/Core.php';
> require_once PHPWS_SOURCE_DIR . 'mod/users/class/Users.php';
> require_once PHPWS_SOURCE_DIR . 'mod/users/class/Groups.php';
> 
> $GLOBALS['core'] =& new PHPWS_Core(NULL, NULL);
> 
> $today = date("Y-m-d H:i:s", mktime(0, 0, 0, date("m"), date("d"),  
> date("Y")));
> 
> /* first get the array of expired members */
> $expiredMembers = $GLOBALS["core"]->sqlSelect 
> ("mod_cstmembers_members", "expiryDate", $today, NULL, "<", NULL,  
> NULL, NULL, NULL, TRUE);

> /* then loop through them */
> foreach ($expiredMembers as $member){
>      /* get the user_id */
>      $user_id = PHPWS_User::getUserId($member['owner']);
>      if ($user_id) {
>          /* remove them from the groups */
>          $group_id = 1;
>          PHPWS_User_Groups::removeGroupFromUser($user_id, $group_id);
>      }
> }
> 
> ?>
> 
> Thanks,
> verdon

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

[Phpwebsite-developers] help with time-out on a custom script

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

Hi,

I'm trying to cobble together something kind of customized to do some  
maintenance on a phpws 0.10.2 site and am running into timeout  
errors. I'm hoping someone might be able to suggest an alternative  
method for me.

The error is
PHP Fatal error:  Maximum execution time of 30 seconds exceeded in / 
home/user/public_html/dev/en/lib/pear/DB/mysql.php on line 316

The goal of the script is that I have a table with member profiles  
that include an expiration date. I need a script that can look at  
that table, find the expired users, then look up the corresponding  
user and remove them from a couple groups. Eventually, this script  
will get run via cron. I am just getting started...

<?php

require_once("/home/user/public_html/dev/en/conf/config.php");
define('PHPWS_SOURCE_DIR', $source_dir);
require_once PHPWS_SOURCE_DIR . 'security.php';
require_once PHPWS_SOURCE_DIR . 'core/Core.php';
require_once PHPWS_SOURCE_DIR . 'mod/users/class/Users.php';
require_once PHPWS_SOURCE_DIR . 'mod/users/class/Groups.php';

$GLOBALS['core'] =& new PHPWS_Core(NULL, NULL);

$today = date("Y-m-d H:i:s", mktime(0, 0, 0, date("m"), date("d"),  
date("Y")));

/* first get the array of expired members */
$expiredMembers = $GLOBALS["core"]->sqlSelect 
("mod_cstmembers_members", "expiryDate", $today, NULL, "<", NULL,  
NULL, NULL, NULL, TRUE);

/* then loop through them */
foreach ($expiredMembers as $member){
     /* get the user_id */
     $user_id = PHPWS_User::getUserId($member['owner']);
     if ($user_id) {
         /* remove them from the groups */
         $group_id = 1;
         PHPWS_User_Groups::removeGroupFromUser($user_id, $group_id);
     }
}

?>

Thanks,
verdon

Re: [Phpwebsite-developers] SVN menu plugin for OSX

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

Great news. Thank you.

On Fri, 2007-02-02 at 11:06 +0000, Shaun Murray wrote:
> In case any of you on OSX missed it, after a long break development  
> on the SCPlugin contextual menu for OSX's Finder so that you can work  
> with svn repositories directly in the Finder has begun again. Anyone  
> familiar with TortoiseSVN on Windows will appreciate SCPlugin.
> 
> A couple of days ago there was a new release - here's the news....
> 
> 2007/01/27 - Announcing Release 0.6 of SCPlugin!
> 
> The new version is here!
> 
> An active development team has re-formed around SCPlugin, we've made  
> some great progress, and we're ready to roll out a new release. Both  
> the developer's mail list and the users' list have become strong and  
> active.
> 
> So, what's new with version 0.6?
> 
> Plenty!
> 
> * First, we've switched from running a command-line copy of the  
> subversion program, to calling the libraries directly. This avoids  
> many problems with funny file names, it's faster, and it will  
> eventually allow SCPlugin to function without any separately  
> installed command-line tool (though we're not quite there, yet).
> * With the release of Subversion 1.4, we're able to switch to storing  
> login credentials for your remote repositories in the MacOS X  
> Keychain, a vastly more secure and standard way to do this.
> * We no longer need to install things into three different places.  
> The plugin consists of just one bundle file. No preferences to  
> configure.
> 
> 
> http://scplugin.tigris.org/
> 
> 
> My quest continues for something as nice as CVL for cvs but at the  
> moment, SCPlugin and Textmate's svn support are ok.
> 
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> aegis hosting - http://www.aegishosting.co.uk
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> 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

Re: [Phpwebsite-developers] SVN menu plugin for OSX

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

Thanks for the heads up Shaun... I wasn't aware of this :)

On 2-Feb-07, at 6:06 AM, Shaun Murray wrote:

> In case any of you on OSX missed it, after a long break development
> on the SCPlugin contextual menu for OSX's Finder so that you can work
> with svn repositories directly in the Finder has begun again. Anyone
> familiar with TortoiseSVN on Windows will appreciate SCPlugin.
>
> A couple of days ago there was a new release - here's the news....
>

[Phpwebsite-developers] SVN menu plugin for OSX

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

In case any of you on OSX missed it, after a long break development  
on the SCPlugin contextual menu for OSX's Finder so that you can work  
with svn repositories directly in the Finder has begun again. Anyone  
familiar with TortoiseSVN on Windows will appreciate SCPlugin.

A couple of days ago there was a new release - here's the news....

2007/01/27 - Announcing Release 0.6 of SCPlugin!

The new version is here!

An active development team has re-formed around SCPlugin, we've made  
some great progress, and we're ready to roll out a new release. Both  
the developer's mail list and the users' list have become strong and  
active.

So, what's new with version 0.6?

Plenty!

* First, we've switched from running a command-line copy of the  
subversion program, to calling the libraries directly. This avoids  
many problems with funny file names, it's faster, and it will  
eventually allow SCPlugin to function without any separately  
installed command-line tool (though we're not quite there, yet).
* With the release of Subversion 1.4, we're able to switch to storing  
login credentials for your remote repositories in the MacOS X  
Keychain, a vastly more secure and standard way to do this.
* We no longer need to install things into three different places.  
The plugin consists of just one bundle file. No preferences to  
configure.


http://scplugin.tigris.org/


My quest continues for something as nice as CVL for cvs but at the  
moment, SCPlugin and Textmate's svn support are ok.


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

Re: [Phpwebsite-developers] Delivery

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

I'd like to think the latter.

On Mon, 2007-01-08 at 14:28 +0000, Shaun Murray wrote:
> On 8 Jan 2007, at 07:38, Greg Morgan wrote:
> 
> > I do know that core is used on Solaris systems for C segmentation  
> > fault
> > files.  The OS dumps a copy of the program's memory into a core file.
> 
> At least in the default config in Linux, Apache also shows the  
> phpwebsite core directory with a little bomb next to it when viewing  
> with indexes allowed.
> 
> CVS on my system marks the core directory as a file that's not  
> important, like it does hidden dot files.
> 
> I'm not sure what they're trying to say but they're describing core  
> code as either not important or 'da bomb'.
> 
> 
> 
> 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
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Delivery

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

On 8 Jan 2007, at 07:38, Greg Morgan wrote:

> I do know that core is used on Solaris systems for C segmentation  
> fault
> files.  The OS dumps a copy of the program's memory into a core file.

At least in the default config in Linux, Apache also shows the  
phpwebsite core directory with a little bomb next to it when viewing  
with indexes allowed.

CVS on my system marks the core directory as a file that's not  
important, like it does hidden dot files.

I'm not sure what they're trying to say but they're describing core  
code as either not important or 'da bomb'.



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

Re: [Phpwebsite-developers] Delivery

[Greg M. <drk...@co...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew McNaney wrote:
> Is "core" a misleading name for the base files of phpwebsite?
> 
> Any advice would be appreciated.
> 
How big will OpenSolaris be?  I don't know but we do have
http://www.blastwave.org/ , a GPLed Java, a hint of a GPL3 Solaris, and
Knoppix like CDs in the form of BeLenix
http://www.genunix.org/distributions/belenix_site/?q=about.  As a
Solaris customer at work, I am always disappointed at how far back the
available code versions are for Solaris but I guess it is improving.

I do know that core is used on Solaris systems for C segmentation fault
files.  The OS dumps a copy of the program's memory into a core file.  I
recall responding to a forum message.  The guy was upset that he did not
have a backup of the core directory.  You see the default settings of
Solaris exclude the *core* from backups. ;-0  Well that was easy to fix
with a copy of the core directory from another tar.gz file and the
altering of the default backup settings.  However, you may want to stay
away from the word core in the 1.x world for part of the community that
runs phpWebSite on Solaris or OpenSolaris.

Regards,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFFofTuxyxe5L6mr7IRAtCZAJ9bOM7VMK6x4BSEOsTjOmJFGVNlAwCfdxyj
PWoce84+Lzy1rVntF2aS9og=
=cew2
-----END PGP SIGNATURE-----

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

On 5 Jan 2007, at 17:58, Matthew McNaney wrote:

>> Couldn't we just add images in some shorthand text format (maybe
>> extending BBCode) that pointed to an uploaded image asset that the
>> user has uploaded to their own personal filecabinet? and images
>> uploaded during a blog item creation process are added into a default
>> file cabinet?
>
> File Cabinet does use SmartTags. If you upload an image and clip it  
> you
> can use the SmartTag anywhere you like. It looks like this:
>
> [filecabinet:image:1]
>
> SmartTags are flexible and we could alignment, styles, etc. to it as
> well.


Cool. I presume the SmartTag knows about the asset type so presents  
it in an appropriate way? Then all we need do is expand the types to  
add audio, video, YouTube link etc.


As Verdon said, maybe just let users format the image by wrapping it  
in a div. If they've got a wysiwyg editor, even , the old js one,  
then it's easy enough.

Now it just needs an easy upload facility for getting the image into  
a users personal filecabinet at the time the user is writing the blog  
entry.


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

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

On 5-Jan-07, at 12:58 PM, Matthew McNaney wrote:

>> Couldn't we just add images in some shorthand text format (maybe
>> extending BBCode) that pointed to an uploaded image asset that the
>> user has uploaded to their own personal filecabinet? and images
>> uploaded during a blog item creation process are added into a default
>> file cabinet?
>
> File Cabinet does use SmartTags. If you upload an image and clip it  
> you
> can use the SmartTag anywhere you like. It looks like this:
>
> [filecabinet:image:1]
>
> SmartTags are flexible and we could alignment, styles, etc. to it as
> well.

I quite like the SmartTags. Personally, I'd just use them barebones  
and wrap them in a div or span for styling. I'd avoid using the old  
img align attributes, though I can see the ability to send style or  
border info through the tag to be useful. I guess it just boils down  
to personal working preferences and methods. There's a lot of ways to  
skin a cat!

verdon

Ps. no offense to cat lovers ;-)

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

> Couldn't we just add images in some shorthand text format (maybe  
> extending BBCode) that pointed to an uploaded image asset that the  
> user has uploaded to their own personal filecabinet? and images  
> uploaded during a blog item creation process are added into a default  
> file cabinet?

File Cabinet does use SmartTags. If you upload an image and clip it you
can use the SmartTag anywhere you like. It looks like this:

[filecabinet:image:1]

SmartTags are flexible and we could alignment, styles, etc. to it as
well.

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

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

On 5 Jan 2007, at 16:14, Matthew McNaney wrote:

> As Verdon suggested, I'd like the image manager included in File  
> Cabinet
> able to handle your suggestions. It has an Image and Document class
> built in.
>

Sounds like a good place to put it.

> Profiles uses it although I haven't really looked at that module in a
> while.
>
> Blog and Web Pages will have a feature to add images outside of the
> FCKeditor. I thought people were tired of having the templated image
> locations. I was wrong :P Once I get that feature back in, we can
> discuss the limitations of File Cabinet and how to proceed.
>

I think people ARE tired of the inflexible fixed templated positions  
but that doesn't preclude being able to use images outside of editors  
like FCKeditor. The idea to escape from templates isn't a bad one.

Couldn't we just add images in some shorthand text format (maybe  
extending BBCode) that pointed to an uploaded image asset that the  
user has uploaded to their own personal filecabinet? and images  
uploaded during a blog item creation process are added into a default  
file cabinet?

eg. [img asset=assetid, align=left|right|center]




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

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

I can convert it to 1.0.0. Please add it to the featreq list at
sourceforge. BTW, wysiwyg is included with 1.0 in the javascript
directory. May be an older version though. In any case, I can add it as
an editor choice.


On Thu, 2007-01-04 at 12:35 +0000, Shaun Murray wrote:
> On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:
> 
> >
> > Does anyone else have anything to add?
> >
> 
> Add the simple wysiwyg tool from 0.10.3 (unreleased) into 1.0. The  
> version we ended up with in CVS is really quite good, edits in place  
> and works on all browsers unlike FCK or whatever.
> 
> The only thing I'd change is make it use bbcode instead of html (or  
> make it selectable)
> 
> I've got this to look at myself as there's no way I'm ghetto-ising  
> non-Firefox/IE users.
> 
> 
> 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
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

[Phpwebsite-developers] Delivery followup

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

Thank you to everyone who responded. Following your suggestions, here is
my tentative plan.

core renamed to base.

base_1_4_6.tgz untars to 

phpwebsite_base_1_4_6/
phpwebsite_base_1_4_6/core/
phpwebsite_base_1_4_6/core/class/
phpwebsite_base_1_4_6/inc/
phpwebsite_base_1_4_6/themes/
etc.


Modules

blog_1_1_1.tgz untars to

blog_1_1_1/mod/blog/
blog_1_1_1/mod/blog/class/
etc.

The module method is similar to the PEAR package method. This should
prevent accidental overwrite and (hopefully) less placement confusion.

This is not set yet, so please reply back if you think this is unwise.

Best regards,
Matt


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

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

As Verdon suggested, I'd like the image manager included in File Cabinet
able to handle your suggestions. It has an Image and Document class
built in.

Profiles uses it although I haven't really looked at that module in a
while.

Blog and Web Pages will have a feature to add images outside of the
FCKeditor. I thought people were tired of having the templated image
locations. I was wrong :P Once I get that feature back in, we can
discuss the limitations of File Cabinet and how to proceed.

Thanks,
Matt 

On Fri, 2007-01-05 at 14:02 +0000, Shaun Murray wrote:
> On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:
> 
> > * Core image upload function (perhaps added to core/class/File.php)
> 
> I was thinking about this this morning when working out how http:// 
> www.huddletogether.com/projects/lightbox2/ might be used to present  
> images in blog or a photoalbum rewrite or in an ecommerce module  
> where you want small images in the description but big images, or  
> multiple images.
> 
> I'd like to see a core Image class instead of bundling into File like  
> we used to. Maybe it's parent is File so that there's common  
> functions but there's different requirements often such as  
> thumbnailing, resizing, watermarking and viewing.
> 
> I was also thinking that an 'album' class was needed to manage a  
> group of images or maybe this should be able to more generally manage  
> a group of files including audio, video and normal files. Then with  
> an album core class available it'd be easier to upload, present and  
> manage multiple images in a standard way across the modules.
> 
> 
> Have a play with lightbox2 btw. It's lovely.
> 
> 
> 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
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

Hi Shaun,

On 5-Jan-07, at 9:02 AM, Shaun Murray wrote:

>
> On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:
>
>> * Core image upload function (perhaps added to core/class/File.php)
>
> I was thinking about this this morning when working out how http://
> www.huddletogether.com/projects/lightbox2/ might be used to present
> images in blog or a photoalbum rewrite or in an ecommerce module
> where you want small images in the description but big images, or
> multiple images.
>
> I'd like to see a core Image class instead of bundling into File like
> we used to. Maybe it's parent is File so that there's common
> functions but there's different requirements often such as
> thumbnailing, resizing, watermarking and viewing.
>
> I was also thinking that an 'album' class was needed to manage a
> group of images or maybe this should be able to more generally manage
> a group of files including audio, video and normal files. Then with
> an album core class available it'd be easier to upload, present and
> manage multiple images in a standard way across the modules.

I've come to realize since my initial post that there is a fairly  
good image class in File Cabinet (that's what the Featured Photo mod  
is using and it seems a good example of how it might be used) but  
it's not as complete as what you're describing. I wasn't really  
looking there for 'core' things. I guess that's just semantics and in  
the long run probably doesn't matter where things are located in the  
file system, but I was considering File Cabinet a mod and not core  
(albeit a core module). Another way it might have been handled would  
have been to have put File Cabinet's file and image classes in /core/ 
class/ and I might have found them there. You say tomato and I say   
tomato ;-)

Anywise, I agree that thumbnailing/resizing and watermarking are  
critical functions. BTW... thumbnailing/resizing is still available  
in /core/class/File.php

>
> Have a play with lightbox2 btw. It's lovely.
That is a nice visual effect. Someone has made a mod for zen-cart  
(open source e-commerce solution) that uses it and it's pretty popular.

rgds,
verdon

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:

> * Core image upload function (perhaps added to core/class/File.php)

I was thinking about this this morning when working out how http:// 
www.huddletogether.com/projects/lightbox2/ might be used to present  
images in blog or a photoalbum rewrite or in an ecommerce module  
where you want small images in the description but big images, or  
multiple images.

I'd like to see a core Image class instead of bundling into File like  
we used to. Maybe it's parent is File so that there's common  
functions but there's different requirements often such as  
thumbnailing, resizing, watermarking and viewing.

I was also thinking that an 'album' class was needed to manage a  
group of images or maybe this should be able to more generally manage  
a group of files including audio, video and normal files. Then with  
an album core class available it'd be easier to upload, present and  
manage multiple images in a standard way across the modules.


Have a play with lightbox2 btw. It's lovely.


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

[Phpwebsite-developers] Linkman patch

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

It should be noted that the linkman patch released at http:// 
phpwebsite.appstate.edu/blog/1226 is based on the v0.10.x cvs code  
and not the v0.10.2 release. I'm not sure just patching that file  
over 0.10.2 will work properly.

In the cvs version I'd previously solved this problem by adding a  
setting so that you can disable anonymous submissions. It would  
probably be a good idea to supply the entire module here in the patch  
and note the new setting and ask admins to boost in the new module.  
The extra patch is still useful though should the admin leave the  
setting off.


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

Re: [Phpwebsite-developers] Delivery

[hr_vbid <hi...@dc...>]

Good evening (from Berlin is good morning in US ...)
About the Delivery, my wish is to have the tar always relative to a current
installation path - the place, where the main index php resides. When my
focus is, for example, at .../public_html, the decompress can overwrite the
actual installation. In case of modules, .../public_html/mod, in case of
core, .../public_html/core, in case of the relative root, just that
public_html base.
If I'm afraid about doing something becomes dangerous, I can set the path to
anywhere else and decompress. In this case, manual copy/move is required.
But the decompressed files may be viewed before.
With simple words, I prefer the same relative path to core and mods in the
tar, without the need to investigate in each single case where I have to go
in the path tree to decompress.
Regards, Hilmar


Matthew McNaney wrote:
> 
> Good morning.
> 
> I am looking for feedback on how the core and modules should be
> distributed....
> 
> 

-- 
View this message in context: http://www.nabble.com/Delivery-tf2913502.html#a8164528
Sent from the PhpWebsite - Dev mailing list archive at Nabble.com.

Re: [Phpwebsite-developers] Delivery

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

On 4-Jan-07, at 8:14 AM, Matthew McNaney wrote:

> On Thu, 2007-01-04 at 11:53 +0000, Shaun Murray wrote:
>
>> I'd prefer that as then it's less likely I or someone else doesn't
>> overwrite the root directory. Certainly from the phpws-comm project,
>> most modules unpack to module-vn.n.n directories and are then moved
>> in but you usually work in /mod not root
>>
>> That in itself confuses some people as they often don't rename the
>> module-vn.n.n directory and end up with two modules of the same name
>> installed from different directories.
>
> Anyone have any reservations about having the tarballs decompress to a
> version labeled directory? For example, blog_1_0_1.tgz creates  
> directory
> blog_1_0_1/ ?
This works for me, as I often rename a copy of the new version I've  
just expanded in this manner anywise, so I have a bit of a local  
archive of version histories.

>
>> Maybe it's something we can look at enhancing with boost so the
>> process is web based entirely? Use PEAR's Archive_Tar class?
>
> I'll read up on it, but my spider-sense tingles when thinking about  
> file
> execution at the web level.
Speaking only for myself... although this would be convenient in the  
right hands, I sure wouldn't want my clients being able to do updates  
via browser/cp either. Often I have to make minor tweaks to mods to  
suit a client and I know if they could click an update button they  
would, and blow them away ;-) Also, and I know this sounds petty, I  
make my living building and maintaining client sites. All that said,  
I rarely give deity access to a client, just to protect them from  
themselves.

>
>
>> Call it 'base' ???
>
> I like the name 'base'. Any objections?
Works for me too.

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

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

On Thu, 2007-01-04 at 11:53 +0000, Shaun Murray wrote:

> I'd prefer that as then it's less likely I or someone else doesn't  
> overwrite the root directory. Certainly from the phpws-comm project,  
> most modules unpack to module-vn.n.n directories and are then moved  
> in but you usually work in /mod not root
> 
> That in itself confuses some people as they often don't rename the  
> module-vn.n.n directory and end up with two modules of the same name  
> installed from different directories.

Anyone have any reservations about having the tarballs decompress to a
version labeled directory? For example, blog_1_0_1.tgz creates directory
blog_1_0_1/ ?

> Maybe it's something we can look at enhancing with boost so the  
> process is web based entirely? Use PEAR's Archive_Tar class?

I'll read up on it, but my spider-sense tingles when thinking about file
execution at the web level.


> Call it 'base' ???

I like the name 'base'. Any objections?

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

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

On 4-Jan-07, at 7:35 AM, Shaun Murray wrote:

> I've got this to look at myself as there's no way I'm ghetto-ising
> non-Firefox/IE users.
>
Ya, us Safari users have to stick together ;-)

Re: [Phpwebsite-developers] Wish-list for 1.x core

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

On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:

>
> Does anyone else have anything to add?
>

Add the simple wysiwyg tool from 0.10.3 (unreleased) into 1.0. The  
version we ended up with in CVS is really quite good, edits in place  
and works on all browsers unlike FCK or whatever.

The only thing I'd change is make it use bbcode instead of html (or  
make it selectable)

I've got this to look at myself as there's no way I'm ghetto-ising  
non-Firefox/IE users.


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

Re: [Phpwebsite-developers] Happy New Year!

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

On 2 Jan 2007, at 19:28, Matthew McNaney wrote:
> 3) Anonymous submission rights for calendar and blog
>

My first job this year is sticking many of the features I stuck in  
Announce for 0.10.x into Blog so it can be used as a multi-user blog  
system including personal blog list pages, archives and promoting  
blogs to the front page. And image uploads.



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

Re: [Phpwebsite-developers] Delivery

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

On 3 Jan 2007, at 13:27, Matthew McNaney wrote:

> Good morning.
>
> I am looking for feedback on how the core and modules should be
> distributed.
>
> Initially, modules untarred to their own directory. For example,
> blog_1_3_4.tgz would untar as the directory blog/.
>

I'd prefer that as then it's less likely I or someone else doesn't  
overwrite the root directory. Certainly from the phpws-comm project,  
most modules unpack to module-vn.n.n directories and are then moved  
in but you usually work in /mod not root

That in itself confuses some people as they often don't rename the  
module-vn.n.n directory and end up with two modules of the same name  
installed from different directories.

Maybe it's something we can look at enhancing with boost so the  
process is web based entirely? Use PEAR's Archive_Tar class?


> As for the core, some people are untarring that distro into the core
> directory when, in fact, it needs to be decompressed and copied  
> into the
> root.
>
> How would you prefer this be done? How would you like the modules and
> core to untar? When decompressed, what should the directories be  
> named?
> Is "core" a misleading name for the base files of phpwebsite?

Call it 'base' ???

Call just the core library 'core'.

And for the record I've always disliked 'core' as a directory name  
since Apache generally thinks it's a core dump and my CVS tool  
ignores it by default. Even raised an RFE to change it way back.


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