Re: [phplib] New site using phpslash... From: nathan r. hruby (nhruby <email protected>)
Date: 05/24/01

On Thu, 24 May 2001, Aric Caley wrote:

> I am developing a website and I wish to use phpslash on it. I have
> some questions:

You should probably ask them on phpslash-users <email protected>
(http://lists.sourceforge.net/mailman/listinfo/phpslash-users/ to
subscribe) :)

>
> What version of the code should I use? Should I keep the site
> constantly up to date with what is being developed, or just use the
> official releases? And, how do I go about updating the code without
> blowing out any changes I've made (say I totaly customize the
> templates to fit with my site's look and feel)? Will the databases be
> changing enough to blow out existing articles I've entered? I'm
> concerned that if I get my site up and running for a while and have
> lots of content posted that it will all go bye-bye with some future
> version of the code.
>

We provide upgrade paths for databases from stable release to stable
release. For a production site I highly suggest sticking with the stable
release, devel CVS code is typically broken in some way or another.

Templates will change over time, but the changes will never be too major
and will be documented.

We're certinaly not out to obliderate your stie :)

> I'd like to serve out different versions of the site... for instance,
> plain HTML, HTML with CSS, WML, and Flash... what's a good way to go
> about doing this? Have several different sets of templates and
> somehow direct the phpslash code to the appropriate directory? I was
> thinking having just one set of templates in some form of XML code and
> have an XML -> whatever post processor... this make any sense?
>

You'll need to do a serious bit of hacking to get XSLT working with
phpSlash. our next release should have a Theme/Skin system that lets a
user change between entire sets of templates. This should do what you
want.

> I have the code currently running and it works, most of the time.
> Seemingly randomly, but all too frequently (on the order of 1 out of 3
> or 4 page accesses) I get a screenfull of errors on a page, but a
> refresh will display just fine... what could be the problem here?

You should post the errors. If you're running and testing the site on the
same machine (like your home devel box) you'll get MySQL errors about
inserting duplicate keys. This is becasue your browser is runing through
the site too fast. The latenct implied by any real network connection
will solve that problem for you (unless it's an intranet and every one is
connected by GigE... :)

>
> Finaly, I'd like to contribute to developing the code, as I'm sure I
> will need some features that dont exist yet. How should I go about
> doing this, when the time comes?
>

Talk to us on phpslash-users about stuff you want to do, and we'll try to
help. If you find bugs or have simple patches send to the SourceForge
page at http://sf.net/projects/phpslash/

-n 

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
nathan hruby / digital statement
nathan <email protected>
http://www.dstatement.com/

Public GPG key can be found at:
http://www.dstatement.com/nathan-gpg-key.txt
ED54 9A5E 132D BD01 9103  EEF3 E1B9 4738 EC90 801B
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>