phpwebsite-developers — For our development team.

[Phpwebsite-developers] Go to Module Link

[Wendall C. <wen...@to...>]

Hey everyone,

Don and I have never taken the time to see why the Go to Module link
doesn't work with some mods after installing. I finally took the time to
find out and wanted to share it with everyone, and discuss adding it to
mods that don't have it, or modify the behavior of
mod/boost/class/Boost.php.

Anyway, in conf/controlpanel.php you need to add "admin"=>TRUE to the
$link[] array to have the "Go to Module" link appear after boosting your
mod.

I didn't test to see if this makes the mod only available to admin users
in the control panel. If that is the case, I think a modification to
Boost.php may be in order. The line that would need to be altered is 337
in current cvs:
if (isset($modLink['admin']) && (bool)$modLink['admin'] == TRUE)

I'm not sure what the original thought was behind this line. It doesn't
really make any sense to me since a user must be a Diety to boost
anyway. May be more appropriate to just whack this line. Something to
look into anyway.

Wendall
-- 
"Only the ideas that we really live have any value." --Hermann Hesse
(Demian)

Re: [Phpwebsite-developers] DOCTYPE and server side charset for themes

[Mike N. <mh...@us...>]

On Sat, 2004-04-03 at 10:31, Mike Noyes wrote:
> I'm not sure how useful you'll find this, but here it is anyway. This
> sets the doctype and server side charset. The <meta content-type set by
> layout is redundant with this setup. This solution should work with
> Mozilla and IE. Feedback is appreciated.

Everyone,
These files are now in the -comm cvs repository. Enjoy.

http://cvs.sourceforge.net/viewcvs.py/phpwebsite-comm/themes/debug/

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Re: [Phpwebsite-developers] BBCode

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

On 6 Apr 2004, at 05:08, Don Seiler wrote:

> On Tue, Apr 06, 2004 at 05:04:27AM +0100, Shaun Murray wrote:
>> I noticed it in a form where you filled in your email address. eg. a
>> contact page. The user entered in an address which was getting saved 
>> in
>> the database as a mailto: link. Not terribly useful if you actually
>> wanted the email address for processing later but easily avoided by 
>> not
>> using parseOutput.
>
> I don't think you want to be using parseOutput() to prefill form fields
> anyway.  It's my opinion that parseOutput() is used for displaying of
> that entered data.  In a form edit field you'd want to see the raw data
> unparsed.
>

Yep. Almost certainly true else you get weird things like html entities 
turning back into their characters so the reason you put them in in the 
first place gets lost.


> Where are you seeing this?  One of my mods?
>

Nah, it was in the mailto mod announced on the phpwebsite site a few 
days ago that I noticed it but thought I'd mention it just in case 
other people came across it in their modules.


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

Re: [Phpwebsite-developers] BBCode

[Don S. <do...@se...>]

On Tue, Apr 06, 2004 at 05:04:27AM +0100, Shaun Murray wrote:
> I noticed it in a form where you filled in your email address. eg. a=20
> contact page. The user entered in an address which was getting saved in=
=20
> the database as a mailto: link. Not terribly useful if you actually=20
> wanted the email address for processing later but easily avoided by not=
=20
> using parseOutput.

I don't think you want to be using parseOutput() to prefill form fields
anyway.  It's my opinion that parseOutput() is used for displaying of
that entered data.  In a form edit field you'd want to see the raw data
unparsed.

Where are you seeing this?  One of my mods?

Don.

--=20
"There is book smart and the kind of smart that helps do calculus.  But sma=
rt
is also instinct and judgement and common sense.  Smart comes in all kinds =
of
different ways."

George W. Bush
September 19, 2000
=46rom CNN interview.

Re: [Phpwebsite-developers] BBCode

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

On 6 Apr 2004, at 04:02, Don Seiler wrote:

> On Tue, Apr 06, 2004 at 02:14:25AM +0100, Shaun Murray wrote:
>> Don't use parseOutput on email address fields in your modules as the
>> PEAR BBCode parser will convert anything it thinks is an email address
>> into a mailto: link.
>
> Or use the BBCode parsing to your advantage and let it do the mailto:
> link.  *shrug*

I noticed it in a form where you filled in your email address. eg. a 
contact page. The user entered in an address which was getting saved in 
the database as a mailto: link. Not terribly useful if you actually 
wanted the email address for processing later but easily avoided by not 
using parseOutput.



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

Re: [Phpwebsite-developers] BBCode

[Don S. <do...@se...>]

On Tue, Apr 06, 2004 at 02:14:25AM +0100, Shaun Murray wrote:
> Don't use parseOutput on email address fields in your modules as the=20
> PEAR BBCode parser will convert anything it thinks is an email address=20
> into a mailto: link.

Or use the BBCode parsing to your advantage and let it do the mailto:
link.  *shrug*

Don.

--=20
"I am mindful not only of preserving executive powers for myself, but for
predecessors as well."

George W. Bush
January 29, 2001
Washington, D.C.

[Phpwebsite-developers] BBCode

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

Just a quick 'gotcha'

Don recently added BBCode parsing to core/Text.php in CVS.

Don't use parseOutput on email address fields in your modules as the 
PEAR BBCode parser will convert anything it thinks is an email address 
into a mailto: link.


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

[Phpwebsite-developers] The Fat Controller

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

Today, I have been mostly looking at the announcement module and how it  
posts and expires announcements today and there are a number of bugs  
and holes in the design which I've reported but I thought I'd put them  
all in one place and in context. I was just going to mail the team this  
email but thought it might be useful discussion for developers in  
general. And it gave me an excuse to put my email address on another  
mailing list.


There's three fields which cover if an announcement is shown or not in  
the announce module.

active - this is controlled by 'Hide/Show' in the settings and the  
Approval module. Hide/Show also activates/deactivates the fatcat db  
entry.
poston - the date an announcement is posted.
expiration - the date an article is to be expired.

There was a bug in the past announcement block where it ignored poston.  
I submitted a bug report and fix today.
http://sourceforge.net/tracker/index.php? 
func=detail&aid=929870&group_id=15539&atid=115539

The poston/expiration settings are ill thought out with regard to  
categories. These don't activate/deactivate the fatcat entry so fatcat  
will report announcements that are approved but outside the date range.  
I've raised a bug report for that.  
http://sourceforge.net/tracker/index.php? 
func=detail&aid=930107&group_id=15539&atid=115539 . I'm not sure how to  
fix that.

You may also not want to expire an announcement but there is no setting  
for this. There's also no way to specify a year or time of day in the  
interface - all important for those 'Happy New Year' posts that you  
queue up whilst sober. I RFE'd that -  
http://sourceforge.net/tracker/index.php? 
func=detail&aid=929861&group_id=15539&atid=365539


However,

There's also a pagemaster and menuman RFE -  
https://sourceforge.net/tracker/? 
func=detail&atid=365539&aid=722741&group_id=15539

...and I'm sure you could argue a case for blockmaker, article, jobman,  
listings.....

Expanded Workflow abilities were mentioned in interviews with the team  
on phpwebsitemanual.com which will be very welcomed by me at least  
coming from a journalistic background where everything has to go past  
the right desk before it gets out or you're embargoed on a story until  
noon on May the 14th but you must get the article ready to beat the  
press.

To recap, the current workflow controls are...

1) Announce (as detailed above) with it's problems

2) We have FatCat being told what is active or not from the modules and  
which category.

3) The Approval module tells modules to hide/show content on submission  
only.

4) Other modules have their own methods.


So we have workflow information spread about all over the place.

This gelled together, to me, as the basis of an expanded role for  
FatCat as a 'FatController'. A kind of central control module with  
which you controlled the showing and hiding of content as well as  
categorising it and I guess an audit trail should be in there also so  
perhaps we don't need userid, datecreated, dateupdated in the module  
either. Fatcat already stores content ids and active or not settings  
but not timed control settings so those would be need to be added.  
Currently you can view expired announcements for instance because  
FatCat knows nothing of expiration dates.

FatCat currently doesn't control the ability to display content - each  
module does. In the new 'FatController' world, each module would have  
to ask the controller what it is allowed to display and workflow info  
like active, poston, expiration, dateCreated, dateUpdated etc, would  
come from the controller, not the module.

Thoughts?


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

Re: [Phpwebsite-developers] DOCTYPE and server side charset for themes

[Mike N. <mh...@us...>]

On Sat, 2004-04-03 at 10:31, Mike Noyes wrote:
> Ref. HTML Declarations
> http://www.htmldog.com/guides/htmladvanced/declarations/

Everyone,
Here is another reference that describes the issues theme.php attempts
to solve.

Serving XHTML 1.0
        XHTML & MIME types
        'Standards' vs 'Quirks' modes
        The XML declaration

http://www.w3.org/International/articles/serving-xhtml/Overview.html

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Re: [Phpwebsite-developers] DOCTYPE and server side charset for themes

[Mike N. <mh...@us...>]

Everyone,
Even better, set the else doctype to transitional, and you can still use
validator.w3.org. Enjoy. :-)


On Sat, 2004-04-03 at 13:08, Mike Noyes wrote:
> The method below is also a good xhtml well-formed debugging tool when
> used with Mozilla/Firefox.

> On Sat, 2004-04-03 at 10:31, Mike Noyes wrote:
> > theme.php
> > <?php
> > if(stristr($_SERVER["HTTP_ACCEPT"],"application/xhtml+xml")){
> > header("Content-Ty
> > pe: application/xhtml+xml; charset=UTF-8");
> >    $THEME["DOCTYPE"] = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>
> > <!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.1//EN\"
> >     \"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd\">";
> > } else { header("Content-Type: text/html; charset=UTF-8");
> >    $THEME["DOCTYPE"] = "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0
> > Strict//EN
> > \"
> >    \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">";
> > }
> > ?>

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Re: [Phpwebsite-developers] DOCTYPE and server side charset for themes

[Mike N. <mh...@us...>]

Everyone,
The method below is also a good xhtml well-formed debugging tool when
used with Mozilla/Firefox.


On Sat, 2004-04-03 at 10:31, Mike Noyes wrote:
> I'm not sure how useful you'll find this, but here it is anyway. This
> sets the doctype and server side charset. The <meta content-type set by
> layout is redundant with this setup. This solution should work with
> Mozilla and IE. Feedback is appreciated.
> 
> Don,
> Thank you for helping me with the php code. :-)
> 
> 
> mod/layout/conf/config.php
>      define("ALLOW_THEME_PHP_INSERTION", TRUE);
> 
> theme.php
> <?php
> if(stristr($_SERVER["HTTP_ACCEPT"],"application/xhtml+xml")){
> header("Content-Ty
> pe: application/xhtml+xml; charset=UTF-8");
>    $THEME["DOCTYPE"] = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>
> <!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.1//EN\"
>     \"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd\">";
> } else { header("Content-Type: text/html; charset=UTF-8");
>    $THEME["DOCTYPE"] = "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0
> Strict//EN
> \"
>    \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">";
> }
> ?>
> 
> theme.tpl -- first line must be
> {DOCTYPE}
> 
> 
> Ref. HTML Declarations
> http://www.htmldog.com/guides/htmladvanced/declarations/

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

[Phpwebsite-developers] DOCTYPE and server side charset for themes

[Mike N. <mh...@us...>]

Everyone,
I'm not sure how useful you'll find this, but here it is anyway. This
sets the doctype and server side charset. The <meta content-type set by
layout is redundant with this setup. This solution should work with
Mozilla and IE. Feedback is appreciated.

Don,
Thank you for helping me with the php code. :-)


mod/layout/conf/config.php
     define("ALLOW_THEME_PHP_INSERTION", TRUE);

theme.php
<?php
if(stristr($_SERVER["HTTP_ACCEPT"],"application/xhtml+xml")){
header("Content-Ty
pe: application/xhtml+xml; charset=UTF-8");
   $THEME["DOCTYPE"] = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>
<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.1//EN\"
    \"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd\">";
} else { header("Content-Type: text/html; charset=UTF-8");
   $THEME["DOCTYPE"] = "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0
Strict//EN
\"
   \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">";
}
?>

theme.tpl -- first line must be
{DOCTYPE}


Ref. HTML Declarations
http://www.htmldog.com/guides/htmladvanced/declarations/

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Re: [Phpwebsite-developers] phpwsBB 0.9.0 Released

[Don S. <do...@se...>]

singletrack found some bad bugs so I pulled the release.  Consider it
your April Fool's joke from me.

Don.

On Thu, Apr 01, 2004 at 09:22:08PM -0600, Don Seiler wrote:
> phpwsBB is a native bulletin board module for the phpWebSite content
> manage system, version 0.9.3-2 or later. It features thread monitoring
> and administration, including marking threads sticky, locking threads,
> and forking messages off to new threads.
>=20
> Changes galore. Most visible are the icons that I stole from
> http://svgicons.sf.net to make phpwsBB a little softer on the eyes.
> Other changes include having some personal monitoring preferences, and
> some bug/logic fixes when it comes to monitoring in general.
>=20
> Also added the ability for a site admin to take phpwsBB "offline",
> making it unavailable for everyone but deities to do maintenance work on
> the site.
>=20
> http://phpwsbb.sourceforge.net
> --=20
> "It's clearly a budget.  It's got a lot of numbers on it."
>=20
> George W. Bush
> May 5, 2000
> Reported by Reuters.



--=20
"People make suggestions on what to say all the time.  I'll give you an
example.  I don't read what's handed to me.  People say, 'Here, here's your
speech,' or 'Here's an idea for a speech.'  They're changed.  Trust me."

George W. Bush
March 15, 2000
Quoted in the New York Times.

[Phpwebsite-developers] phpwsBB 0.9.0 Released

[Don S. <do...@se...>]

phpwsBB is a native bulletin board module for the phpWebSite content
manage system, version 0.9.3-2 or later. It features thread monitoring
and administration, including marking threads sticky, locking threads,
and forking messages off to new threads.

Changes galore. Most visible are the icons that I stole from
http://svgicons.sf.net to make phpwsBB a little softer on the eyes.
Other changes include having some personal monitoring preferences, and
some bug/logic fixes when it comes to monitoring in general.

Also added the ability for a site admin to take phpwsBB "offline",
making it unavailable for everyone but deities to do maintenance work on
the site.

http://phpwsbb.sourceforge.net
--=20
"It's clearly a budget.  It's got a lot of numbers on it."

George W. Bush
May 5, 2000
Reported by Reuters.

[Phpwebsite-developers] language file generator

[Don S. <do...@se...>]

I've written a script that will parse your module's php files and
generate a valid PHPWS language file.  Right now I hard coded "en" but
whatever.

http://phpwsbb.sourceforge.net/createlang.php.txt

Just download, take the ".txt" off the name, cd into the top level of
your module and:

php /path/to/createlang.php

It will then recursively start at your pwd and get all translated texts.
It then writes a lang/$mod_title.en.lng file, grabbing $mod_title from
your conf/boost.php.  *WARNING* It _will_ overwrite your current
language file.  But in theory this is what you'd want.

Anyway feel free to use and report any bugs and what not.  One big
concern that you might have is that right now it only searches based on
double-quotes, which is what I use.  I know a lot of you use
single-quotes for things like $_SESSION['translate'] where I use
$_SESSION["translate"].  Feel free to add that capability and send me a
patch or just change my line for your own private, selfish uses, you
jerk.

Thanks to alindeman in #php for the regex help.

Don.

--=20
"The most important job is not to be governor, or first lady in my case."

George W. Bush
January 30, 2000
=46rom speech in Pella, Iowa and quoted in the San Antonio Express-News.

[Phpwebsite-developers] Documentation Status

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

I just finished additional updates to the CVS section of the manual.  A 
sample is located here 
http://kissalice.sourceforge.net/phpmanual/output/c2120.html.  I 
reworked it after seeing a post in the forums.

Yeah I still stink at docbook. ;-) I am wondering about the opening line 
again.  The original manual.xml file has this reference
<!DOCTYPE set PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
"http://docbook.org/xml/4.2/docbookx.dtd".  While looking around it 
looks like all of the docbook.org references are being migrated to 
either docbook.sourceforge.net or www.oasis-open.org.  Where should the 
'<!DOCTYPE set PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"' line be 
directed in the future?

Greg

Re: [Phpwebsite-developers] Using session information to limit mailings...

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

php.net has probably the best information on this subject.

Briefly, you place information in a session like so:

$_SESSION['variable_name_here'] = "foo";

This session will remain until the user logs off or until you destroy
it.

You then access it just like you would any other variable.

$bar = $_SESSION['variable_name_here'];

echo $bar;

// prints 'foo'

~Matt

On Wed, 2004-03-17 at 12:02, Tony Miller wrote:
> I am writing a mailto module to allow folks to make harvest proof links
> easily on their websites.  I am almost ready for release but I have one
> more thing I want to accomplish.
> 
> When it goes to the thank you form after mailing the information, the user
> is able to refresh the page over and over and over effectively using my
> module to mailbomb someone.
> 
> I would like to limit (possibly timewise) the number of times that an
> individual session can mail.  I am thinking a 5 minute lag between mailing
> based on how mailtos are usually used.  Someone reads a page, decides to
> mailto, and does it.  They don't go to each and every link on the page
> sending it stuff (unless they are a spammer and we want to stop that).
> 
> I'm thinking of a global variable or something like that (maybe a table
> that stores session and time mailed) but I don't have a good handle on how
> to access the session variable.  Does anyone have a tutorial on what
> variables phpwebsite uses to store the session string for a particular
> session?  I've grepped the source, and I must have missed something
> because I haven't found the info.
> 
> Thanks in advance for your help,
> -Tony
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

[Phpwebsite-developers] Using session information to limit mailings...

[Tony M. <to...@ci...>]

I am writing a mailto module to allow folks to make harvest proof links
easily on their websites.  I am almost ready for release but I have one
more thing I want to accomplish.

When it goes to the thank you form after mailing the information, the user
is able to refresh the page over and over and over effectively using my
module to mailbomb someone.

I would like to limit (possibly timewise) the number of times that an
individual session can mail.  I am thinking a 5 minute lag between mailing
based on how mailtos are usually used.  Someone reads a page, decides to
mailto, and does it.  They don't go to each and every link on the page
sending it stuff (unless they are a spammer and we want to stop that).

I'm thinking of a global variable or something like that (maybe a table
that stores session and time mailed) but I don't have a good handle on how
to access the session variable.  Does anyone have a tutorial on what
variables phpwebsite uses to store the session string for a particular
session?  I've grepped the source, and I must have missed something
because I haven't found the info.

Thanks in advance for your help,
-Tony

[Phpwebsite-developers] typo on phpws site

[Don S. <do...@se...>]

http://phpwebsite.appstate.edu/index.php?module=3Dpagemaster&PAGE_user_op=
=3Dview_page&PAGE_id=3D52

Title is "Thrid Party Modules".  Assuming you meant "Third".

And yes I was found it because I'm a loser and typed my own name into
google.  Happy now?  Huh?  HUH?!?!

Jerks.
--=20
"Will the highways on the Internet become more few?"

George W. Bush
January 29, 2000
Question asked by the candidate in Concord, New Hampshire and reported in
Slate magazine.

Re: [Phpwebsite-developers] Build Proceedure for the XML Manual Files

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

Mike Noyes wrote:
>>While working on this book, I had to change all instances of
>>"http://docbook.org/xml/4.2/docbookx.dtd" to
>>"/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd"
>>on Fedora Core 1."
> 
> 
> Your catalog files in /etc/xml aren't setup properly. See:
> 
>         Catalog support
>         http://xmlsoft.org/catalog.html
<snip>

> Take a look at these resources:
> 
>         DocBookXSL: The Complete Guide
>         http://www.sagehill.net/docbookxsl/
>         
>         DocBookXSLStylesheet Documentation
>         http://docbook.sourceforge.net/release/xsl/current/doc/
>         
>         DocBook Wiki
>         http://www.docbook.org/wiki/moin.cgi/
>         
>         Docbook Frequently Asked Questions
>         http://www.dpawson.co.uk/
>         
> Also, take a look at the XXE DocBook editor.
> 
>         XMLmind XML Editor
>         http://www.xmlmind.com/xmleditor/
> 
Mike,

Thanks for the response.  I see I have a catalog in /etc/xml/catalog.  I 
am still digesting the information from the sagehill site.  I am still 
trying to understand the both the public identifier and system 
identifier mapped on my computer.

xsltproc is doing a much better job.

Greg

Re: [Phpwebsite-developers] Branches

[Steven L. <st...@tu...>]

On Tue, 2004-03-16 at 14:33, Robert Aldridge wrote:
> Can someone point me to a "HowTo" or other
> documentation on creating branch sites once your main
> phpWebsite is set up?  I've stumbled around what
> documentation I could find and have "Googled" but to
> no avail.
> 
> Specifically, what must one do before trying to create
> a branch?  Create a new database?  Create a new
> folder?  Is all of this handled in the "Create new
> branch" scripts?

Robert,

 There should be a file by the name of CREATION.txt in the directory
mod/branch/docs/ off the base of your phpwebsite directory.  I believe
this will answer all your questions.

-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

[Phpwebsite-developers] Branches

[Robert A. <bam...@ya...>]

Hello list,

Can someone point me to a "HowTo" or other
documentation on creating branch sites once your main
phpWebsite is set up?  I've stumbled around what
documentation I could find and have "Googled" but to
no avail.

Specifically, what must one do before trying to create
a branch?  Create a new database?  Create a new
folder?  Is all of this handled in the "Create new
branch" scripts?

Thanks,

Robert Aldridge

__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

Re: [Phpwebsite-developers] Build Proceedure for the XML Manual Files

[Mike N. <mh...@us...>]

On Sun, 2004-03-14 at 16:54, Greg Morgan wrote:
> Here's what I have done so far 
> http://kissalice.sourceforge.net/phpmanual/output/set1.html.  It has all 
> my rough ideas in rough rough form.  I cleaned up the CVS section today. 
>   I have added an "Installation, Upgrade, and Maintenance" and fleshed 
> out the "Developer's Guide".  Essentially, I have cobble many of my 
> phpWS forum responses together.  I've started to manipulate them into a 
> manual.  I think Ray O. on the LEAF list said that's one way to help. 
> Watch what is happening in the mailing lists/forums and try and solve 
> those problems. LOL, I've created a few of my own with docbook.

Greg,
Nice work. :-)

> In the http://kissalice.sourceforge.net/phpmanual/ directory are two 
> files.  00readme.txt explains what I had to do to get this working on 
> Redhat's fedora core 1.  That file says, "
> jw -f docbook -b html -o output manual.xml
> 
> docbook2html manual.xml

That is a jade wrapper script. It's not recommended for DocBook XML. You
should be using xsltproc or saxon with the DocBook XSL Stylesheets.

> While working on this book, I had to change all instances of
> "http://docbook.org/xml/4.2/docbookx.dtd" to
> "/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd"
> on Fedora Core 1."

Your catalog files in /etc/xml aren't setup properly. See:

        Catalog support
        http://xmlsoft.org/catalog.html

> The jw with -o to output placed all the html files in the output 
> directory.  makemanual.sh is the jw command in a shell script.
> 
> I don't understand why the official manuals look like this
<snip>

This is a result of the xslt engine (jade) you used. Auto-generated
chapter numbers are different for the DSSSL stylesheets.

> Any solutions and feedback would be appreciated.

Take a look at these resources:

        DocBookXSL: The Complete Guide
        http://www.sagehill.net/docbookxsl/
        
        DocBookXSLStylesheet Documentation
        http://docbook.sourceforge.net/release/xsl/current/doc/
        
        DocBook Wiki
        http://www.docbook.org/wiki/moin.cgi/
        
        Docbook Frequently Asked Questions
        http://www.dpawson.co.uk/
        
Also, take a look at the XXE DocBook editor.

        XMLmind XML Editor
        http://www.xmlmind.com/xmleditor/

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Re: [Phpwebsite-developers] Build Proceedure for the XML Manual Files

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

Mike Noyes wrote:
> On Sat, 2004-03-13 at 07:14, Greg Morgan wrote:
> 
>>Is there a document that explains how the xml build is setup?  I was 
>>fooling around with the manual .xml files and could not get them to 
>>build the same way that they are in phpwebsiteroot/manual directory.
> 
> 
> Greg,
> Building the DocBook manual should be fairly straight forward, provided
> your environment is setup properly. You'll need the proper entities
> also. Let me know if you need help.
> 
> manual.xml
> http://res1.stddev.appstate.edu/horde/chora/cvs.php/phpwebsite/manual
> 
Good.  It looks like no one has worked on these files for eight months.

Here's what I have done so far 
http://kissalice.sourceforge.net/phpmanual/output/set1.html.  It has all 
my rough ideas in rough rough form.  I cleaned up the CVS section today. 
  I have added an "Installation, Upgrade, and Maintenance" and fleshed 
out the "Developer's Guide".  Essentially, I have cobble many of my 
phpWS forum responses together.  I've started to manipulate them into a 
manual.  I think Ray O. on the LEAF list said that's one way to help. 
Watch what is happening in the mailing lists/forums and try and solve 
those problems. LOL, I've created a few of my own with docbook.

In the http://kissalice.sourceforge.net/phpmanual/ directory are two 
files.  00readme.txt explains what I had to do to get this working on 
Redhat's fedora core 1.  That file says, "
jw -f docbook -b html -o output manual.xml

docbook2html manual.xml

While working on this book, I had to change all instances of
"http://docbook.org/xml/4.2/docbookx.dtd" to
"/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd"
on Fedora Core 1."

The jw with -o to output placed all the html files in the output 
directory.  makemanual.sh is the jw command in a shell script.

I don't understand why the official manuals look like this
...
bk01ch01.html     bk01ch06s06.html  bk02ch04s04.html  bk02ch08s06.html
bk01ch01s02.html  bk01ch06s07.html  bk02ch04s05.html  bk02ch08s07.html
bk01ch01s03.html  bk01ch06s08.html  bk02ch04s06.html  bk02ch08s08.html
...
when mine look like this
...
book1977.html  c2150.html  x1048.html  x2015.html  x2154.html  x252.html
book1.html     c2152.html  x1051.html  x2016.html  x2155.html  x312.html
book2006.html  c2155.html  x107.html   x2019.html  x2156.html  x35.html
...

I believe the main problem I have is on this example page, 
http://kissalice.sourceforge.net/phpmanual/output/x2223.html.  See all 
the '>'s.  Those are supposed to be graphics.  I receive this error when 
executing jade i.e. jw, 
"jade:/home/edrive/phpwebsite/phpwebsite932/manual/xml/core/developer/themedevel.xml:151:42:E: 
character data is not allowed here".  Google did not point me to 
anything outstanding.  Moreover, I copied this stanza from the user guide,
     <screenshot>
       <graphic fileref="images/winxp.png"/>
     </screenshot>
These three lines are lines 150-152 in the above error message.  I don't 
have a clue.  Right now I am happy to massage the text into something 
meaningful.

The module you and I talked about on IRC and email is at the beginning 
of the developer tutorial.  Can I quote our session as an example of how 
the item class is discovered?

Oh! I tried searching for the xml editor you and Lynn talked about on 
the LEAF developer's list.  However, I was fruitless.  Do you have have 
the URL for that editor?

After reading this article, http://www106.pair.com/rhp/hacking.html, I 
thought I should post what I've done with the documentation.  One the 
one hand, I wanted to be able to "show the code" while on the other hand 
I wanted to make sure that I start coordinating with others.  If this is 
  acceptable work, then I would like to merge it with the official 
documentation.  I'd rather work in the community than go off and be the 
lone cowboy and have yet another place for the users to look for 
information.

Any solutions and feedback would be appreciated.

Regards,
Greg Morgan

Re: [Phpwebsite-developers] Build Proceedure for the XML Manual Files

[Mike N. <mh...@us...>]

On Sat, 2004-03-13 at 07:14, Greg Morgan wrote:
> Is there a document that explains how the xml build is setup?  I was 
> fooling around with the manual .xml files and could not get them to 
> build the same way that they are in phpwebsiteroot/manual directory.

Greg,
Building the DocBook manual should be fairly straight forward, provided
your environment is setup properly. You'll need the proper entities
also. Let me know if you need help.

manual.xml
http://res1.stddev.appstate.edu/horde/chora/cvs.php/phpwebsite/manual

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs