phpwiki-talk

[Phpwiki-talk] PhpWiki on RedHat

[Charles S. <ch...@st...>]

I've been running PhpWiki 1.3.2 with the mysql back-end on several RedHat
7.2 servers without much trouble, until I recently upgraded to the latest
php code via up2date (php-4.0.6-12).

No matter what I tried, I couldn't get PhpWiki to talk to mysql.  I tried
various modifications to the index.php file, as well as upgrading to both
1.3.3 and the latest CVS code (March 18, 2002).

It turns out there are some problems with the latest RedHat compile of the
mysql back-end for php.

First, if you're running 1.3.2, or earlier versions that relied on the PEAR
DB code from the host system, you'll get a message like the following when
upgrading:

/usr/local/lib/phpwiki-1.3.2/lib/FileFinder.php:82: Fatal[256]: DB.php: file
not found

This is because RedHat moved the pear libraries, so they are not found by
default.  To fix this, you need to add the new location of the pear files
(/usr/share/pear) to the include path:

ini_set('include_path', '/usr/share/pear/');

At this point, you'll get another error, this time something like:

/usr/local/lib/phpwiki-1.3.2/lib/WikiDB/backend/PearDB.php:27: Fatal[256]:
Can't connect to database: wikidb_backend_mysql: fatal database error

or the infamous:
Can't connect to local MySQL server through socket '/tmp/mysql.sock'

This is because the rocket scientists at RedHat compiled the mysql back-end
without mysqld running, so mysql.sock couldn't be found, resulting in the
compiled-in default pointing to /tmp/mysql.sock which doesn't exist.

The fix for this is pretty simple, however, just edit /etc/php.ini, find the
line that sets mysql.default_socket, and change it to the following:

mysql.default_socket = /var/lib/mysql/mysql.sock

Restart httpd so the change will take effect, and your phpwiki should be
back online...

Hopefully, this will save someone else the hassle I went through figuring
this out...

Charles Steinkuehler
ch...@st...

Re: [Phpwiki-talk] ImageAlignment

[Adam S. <ad...@pe...>]

On Mon, 2002-03-18 at 01:05, John Kershaw wrote:
> I've been wondering for a while whether it was possible to add image 
> align=left|right, so I had a dig around in the source on Friday and 
> added some tweaks so I can now put:

Cool!
 
> [http://www.whatever.com/image.jpg left] and it'll insert an 
> 'align=left' attribute into the img tag.

Another syntax I've seen (i think on PikiePikie) was using the <>^_
symbols to show alignment.  They use this for formating content within
table cells.  So maybe something like:

[http://.../image.jpg <]

> I was wondering whether this could be integrated into the main code, 
> or am I barking up a wrong tree? Are there already plans to 
> incorporate this kind of thing (plus alt tags?).

I suspect that a lot of this stuff will fall into place once we figure
out a way to do named anchors nicely.

Adam.

[Phpwiki-talk] ImageAlignment

[John K. <jo...@ke...>]

Hi,

I've been wondering for a while whether it was possible to add image 
align=left|right, so I had a dig around in the source on Friday and 
added some tweaks so I can now put:

[http://www.whatever.com/image.jpg left] and it'll insert an 
'align=left' attribute into the img tag.

I put the code here: 
http://phpwiki.sourceforge.net/phpwiki/ImageAlignment - is that okay?

I was wondering whether this could be integrated into the main code, 
or am I barking up a wrong tree? Are there already plans to 
incorporate this kind of thing (plus alt tags?).

I have *no* idea about how development works, other than I see a 
bunch of guys working together to produce something really cool, and 
I have a server that runs php which I'm trying to learn.

Let me know what you think,

John.
-- 

---------------------------------------------------------
email:  jo...@ke...         phone:      07944 755613
web:     www.kershaw.org    AOL: johnkershaw
---------------------------------------------------------

Re: [Phpwiki-talk] slow wiki

[Philip J. H. <ph...@ho...>]

Two ideas:

1. I experienced a configuration problem:

http://sourceforge.net/forum/forum.php?thread_id=652761&forum_id=18929

for details.

Basically it appears that phpwiki was creating ill-formed links to the
style sheets, and that caused the web browser to take forever to
display the page.

2. There was a bug in 1.3.3 that caused all pages to be rendered
   twice, doubling the execution time.  This has been fixed in the cvs
   snapshot versions.  I installed one of those from a few days ago on
   my site (www.hollenback.net), and it seems to work reasonably well.

P.

On Prickle-Prickle, the 1st of Discord, th...@co... spoke:
> Hello,
> 
> I'm trying to get the last revision (1.3.3) running and 
> would like to ask You to help me finding the reason for
> slow response times (it takes about 2 secs to get a page)
> 
> I've enabled the Debug-Mode, which shows me execution 
> times of 0,3 sec for a page.
> 
> 
> Thomas Kalka
> 
> 
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

-- 
Philip J. Hollenback
ph...@po...
http://www.hollenback.net

[Phpwiki-talk] slow wiki

[<th...@co...>]

Hello,

I'm trying to get the last revision (1.3.3) running and 
would like to ask You to help me finding the reason for
slow response times (it takes about 2 secs to get a page)

I've enabled the Debug-Mode, which shows me execution 
times of 0,3 sec for a page.


Thomas Kalka

[Phpwiki-talk] Re: PHP Drawing Tool

[Andy B. - S. Uk - V. - S. E. <And...@Su...>]

> http://www.xpenguin.com/phpcheckbox.php	
> 
> This is kinda cool.  Not as cool as the java draw thingy that twiki uses
> but still kinda neat (but a big benifit is it's PHP not Java :-).
> 
> Adam.
> 

One problem - the demo crashes my Netscape 4.74 on Solaris. Hmmm
Andy

Re: [Phpwiki-talk] Getting Involved?

[Paul S. <pa...@et...>]

On 13 Mar 2002, Adam Shand wrote:

:Here's now I see it.  The advantage of using something like apache for
:authentication is that there are already a myriad of authentication
:modules written (ldap, mysql, radius, htpasswd, ntlm etc etc).

Hi, my two cents on this:

1. We use mod_auth_external to authenticate users on an
   internal-only/private SSL web site for access to the Wiki.

2. Many of my users are paranoid security freaks who do not
   tolerate cookies.  Mailman, for example, generates complaints
   from the cookie-paranoid.

So I would be very happy if Phpwiki would use basic auth and let me
configure the back-end any way I please.

I would like it if there were an option to have Phpwiki assume that a
working basic auth system is present and have it assume that $REMOTE_USER
exists and is trustworthy, tie that to users' prefs, etc. automatically.

--Paul

Re: [Phpwiki-talk] Getting Involved?

[Adam S. <ad...@pe...>]

> I absolutely understand. Perhaps I could work with them. The specific
> ideas I have right now is similar to the suggestions made at 
> the URL: http://phpwiki.sourceforge.net/phpwiki/UserAuthenticationDoneForYou

The person who did the initial implementation of non-apache based user
auth was Joe Edelman who hasn't been around for a while.  I don't know
if he's just been quiet or has found other responsibilities.
 
> I was thinking that if we could setup a authentication API that
> could be plugged into either http authentication using apache's
> auth systems (like UserAuthType Basic) - or - setup proprietary
> authentication systems (like a username/password in a MySQL db)
> then wiki would not need to handle all the "innards" of authentication
> but rather simply pull the username and password from however 
> it's configured to use authentication.

Here's now I see it.  The advantage of using something like apache for
authentication is that there are already a myriad of authentication
modules written (ldap, mysql, radius, htpasswd, ntlm etc etc).  

The disadvantage is that it makes it harder (impossible?) to force
people to log in via a form where you can request other information
(like an email address) and also explain how things work and that they
may just need to supply a WikiWord compliant username rather then find
somewhere to register for an account.

Leveraging apache would be really nice for intranet wiki's
(mod_auth_ntlm and all your exchange users now have wiki logins). 
However their logins aren't wiki words which sucks for a wiki.  Twiki
gets around this (imho in a confusing, kludgy way) by having a seperate
list which makes login names to wiki names (eg. adams = AdamShand).

The main reason for user authentication imho is that it provides a basis
for other things like customized themes, email notification and such.  I
don't think we need full on real authentication, just something that is
"good enough" (WorseIsBetter) to make abuse a pain and hopefully
discourage abuse.

Adam.

PS. My wiki's have recently stated to have problems of random abuse from
people on the internet (it's gone from happening every few months to a
few times a week).  Is it just me or have others noticed anything like
this?  It scares me a little that it's only going to get worse.

Re: [Phpwiki-talk] Getting Involved?

[Eric C. <er...@ec...>]

Hi Steve!

I absolutely understand. Perhaps I could work with them. The specific
ideas I have right now is similar to the suggestions made at 
the URL: http://phpwiki.sourceforge.net/phpwiki/UserAuthenticationDoneForYou

I was thinking that if we could setup a authentication API that
could be plugged into either http authentication using apache's
auth systems (like UserAuthType Basic) - or - setup proprietary
authentication systems (like a username/password in a MySQL db)
then wiki would not need to handle all the "innards" of authentication
but rather simply pull the username and password from however 
it's configured to use authentication.

Does that make sense?

Also, we could have a default user authentication system - if none is
present but people want an authentication system. Most likely a simple 
plain text file with encrypted passwords. (Using md5)

Just some thoughts - I noticed that phpwiki 1.3.2 would recognize 
an admin logged in via http basic auth (use of the $PHP_AUTH_USER 
I suppose) but with phpwiki 1.3.3 that has been eliminated. :-(

Eric

At Wednesday, 13 March 2002, Steve Wainstead <sw...@pa...> wrote:

>Hi Eric!
>
>I know someone on the project was supposed to be working on user 
auth, and
>promised to deliver something right about now. I haven't heard anything
>though; I will have to search the mail archive.
>
>More than likely you would be welcome to work on this, but I need 
to make
>sure someone else isnt' already doing it. Do you have any specific 
ideas
>right now for auth?
>
>~swain
>
>On Tue, 12 Mar 2002, Eric Carter wrote:
>
>> Hi,
>>
>> I've been hacking around with PhpWiki a bit over the past month
>> and I have to say - this is an awesome project. I have some thoughts
>> and ideas and I'd like to get involved.
>>
>> I'm particularly interested in setting up a seperate User Authentication
>>
>> interface. I've been using simple http basic authentication - and
>> I'd like to know where things are going with the project.
>>
>> Thanks,
>> Eric
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Phpwiki-talk mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>>
>>
>>
>>
>
>---
>                  http://www.panix.com/~swain/
>"Without music to decorate it, time is just a bunch of boring
>production deadlines or dates by which bills must be paid."
>                     -- Frank Zappa
>
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

Re: [Phpwiki-talk] Getting Involved?

[Steve W. <sw...@pa...>]

Hi Eric!

I know someone on the project was supposed to be working on user auth, and
promised to deliver something right about now. I haven't heard anything
though; I will have to search the mail archive.

More than likely you would be welcome to work on this, but I need to make
sure someone else isnt' already doing it. Do you have any specific ideas
right now for auth?

~swain

On Tue, 12 Mar 2002, Eric Carter wrote:

> Hi,
>
> I've been hacking around with PhpWiki a bit over the past month
> and I have to say - this is an awesome project. I have some thoughts
> and ideas and I'd like to get involved.
>
> I'm particularly interested in setting up a seperate User Authentication
>
> interface. I've been using simple http basic authentication - and
> I'd like to know where things are going with the project.
>
> Thanks,
> Eric
>
>
>
>
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
>
>
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

[Phpwiki-talk] Getting Involved?

[Eric C. <er...@ec...>]

Hi,

I've been hacking around with PhpWiki a bit over the past month
and I have to say - this is an awesome project. I have some thoughts
and ideas and I'd like to get involved. 

I'm particularly interested in setting up a seperate User Authentication 

interface. I've been using simple http basic authentication - and 
I'd like to know where things are going with the project.

Thanks,
Eric

[Phpwiki-talk] PHP Drawing Tool.

[Adam S. <ad...@pi...>]

http://www.xpenguin.com/phpcheckbox.php	

This is kinda cool.  Not as cool as the java draw thingy that twiki uses
but still kinda neat (but a big benifit is it's PHP not Java :-).

Adam.

Re: [Phpwiki-talk] problems with 1.2.2 and MostVisited

[Adam S. <ad...@pe...>]

On Sun, 2002-03-10 at 08:12, Daniel Renkel wrote:
> hi there,
> 
> i recently got phpWiki 1.2.2 running (well, still some problems calling
> Admin.php) on our server, but my major question right now is, why isn't the
> MostVisited site not workig ?
> a known bug on 1.2.2 ? not in 1.2.2 ?
> 
> or could it be a problem that i'm running the german version (where it is
> MeistBesucht instead of MostVisited or MostPopular or whatever it is in
> english :) ...

You might want to check out the latest 1.3 release.  It's beta but
pretty stable and has a lot of new features, is a lot prettier (imho)
and the german translation has undergone a lot of work.

Adam.

[Phpwiki-talk] problems with 1.2.2 and MostVisited

[Daniel R. <re...@ce...>]

hi there,

i recently got phpWiki 1.2.2 running (well, still some problems calling
Admin.php) on our server, but my major question right now is, why isn't the
MostVisited site not workig ?
a known bug on 1.2.2 ? not in 1.2.2 ?

or could it be a problem that i'm running the german version (where it is
MeistBesucht instead of MostVisited or MostPopular or whatever it is in
english :) ...

any ideas ?

thanks,
    daniel renkel

Re: [Phpwiki-talk] Empowerment

[Adam S. <ad...@pe...>]

> Using a wiki is an excellent answer, but presents several problems, 
> due to its open nature. Pages would have to be editable only by the 
> site owners, it would need to allow image upload, and let them be 
> aligned etc.

IMHO ...

I think what you've described would be a CMS rather then a Wiki, and
lots of them already exist.  Sorta the entire point of a wiki is that
*everyone* can edit it.  While I support the idea that there may be
certain pages or certain times when a Wiki doesn't want publicly
editable pages, I think it kinda stops being a Wiki when the rule is
that only the site owners can edit the pages.
 
> Would it be worthwhile setting up a branch of phpwiki for 'single-owner' use?

You might want to check out some of the WikiAsPim pages which are on
some of the wiki's.  I believe there are good links from the PhpWiki
page.

Adam.

[Phpwiki-talk] Empowerment

[John K. <jo...@ke...>]

"I think the internet should be mostly comprised of wikis."

Eh, what? My job is building web sites for people, which is fine and 
I enjoy it. But mostly the folks who want to edit the sites day to 
day can't do it because they don't know html and don't want to learn 
it.

Using a wiki is an excellent answer, but presents several problems, 
due to its open nature. Pages would have to be editable only by the 
site owners, it would need to allow image upload, and let them be 
aligned etc.

Would it be worthwhile setting up a branch of phpwiki for 'single-owner' use?

Your thoughts?

John.
-- 

---------------------------------------------------------
email:  jo...@ke...         phone:      07944 755613
web:     www.kershaw.org    AOL: johnkershaw
---------------------------------------------------------

Re: [Phpwiki-talk] how to use categories? (with small attachment)

[Adam S. <ad...@pe...>]

Can this patch or an equivalent of it be committed to CVS?

Adam.

On Fri, 2002-02-22 at 02:56, Marcel van der Boom wrote:
> We use categories with the Category:Categoryname syntax  and the 
> FullTextSearch plugin to generate pages with the pages which belong to a 
> certain category.  For us we made a little change to the FullTextSearch 
> plugin (which is attached)
> 
> So what we do is:
> 
> 1.  At the bottom of a page we include the text Category:CategoryName 
> which is linked as per the configuration in the interwiki.map file (we 
> let it link to a page called "CategoryCategoryName")
> 2. On the page "CategoryCategoryName"  we include the following:
> 
> --snip--
> This page contains a list of documents in the Category:CategoryName 
> category:
> 
> <?plugin FullTextSearch s="Category:CategoryName" noheader=1 onlytitle=1 
> ?>  
> 
> or
> 
> <?plugin FullTextSearch s="Category:Development -Category:Category" 
> noheader=1 onlytitle=1 ?>
> 
> The latter will not show the main Category page which lists all categories.
> 
> The "onlytitle" parameter is the one we added to the plugin: if set to 1 
> the plugin only returns the names of the pages and not the text found in 
> the page itself.  I've attached the modified plugin. As this was a very 
> simple and quick hack to the module I don't know if this is of general 
> interest to include in the distribution, but here it 's attached.
> 
> We also have a Category:Empty page which lists all the non-categorized 
> pages. In this case the plugin like looks like:
> 
> <?plugin FullTextSearch s="-Category:" noheader=1 onlytitle=1 ?>
> 
> Notice the minus sign? This will give a list of pages NOT containing the 
> string "Category:"
> 
> Marcel
> 
> Roel Vanhout wrote:
> 
> >Hi all,
> >
> >While looking for documentation on the phpwiki site I noticed that there
> >seems to be a concept of categories - how do I use these? How do I
> >create one, and how do I add pages to a category? Is there a standard
> >way to get a list of all categories? And from what version on does this
> >work? Thanks!
> >
> >cheers,
> >
> >roel
> >
> >
> >
> >
> >_______________________________________________
> >Phpwiki-talk mailing list
> >Php...@li...
> >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> >
> 
> -- 
> Marcel van der Boom
> HS-Development BV
> Kwartiersedijk 14B
> Fijnaart, The Netherlands
> Tel. : 0168-468822
> Fax. : 0168-468823
> Email: ma...@hs...
> 
> 
> 

Re: [Phpwiki-talk] Flat-file database

[Steve W. <sw...@pa...>]

This looks really cool. The only downside I see is that it doesn't store 
the pages individually; without looking at the implementation, I'd guess 
from the interface that this is sort of a poor man's DBM written in PHP.

This is a downside b/c if the pages are stored individually then they 
can be put in CVS, something which was patched into 1.2 and the work was 
started on 1.3. Perhaps since we have our own versioning it won't matter.

I still want a machine interface to a Wiki. It would be nice if logs 
generated by cron jobs could be automatically inserted somehow.

~swain

Lawrence Akka wrote:
> Steve (and others, but especially Steve),
> 
> When you write the flat-file db code (:-))  you might take a look at 
> http://ffdb-php.sourceforge.net/
> 
> It looks ideal to me.
> 
> Lawrence
> 
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 
> 
> 

Re: [Phpwiki-talk] Flat-file database

[Steve W. <sw...@pa...>]

Reuse code? Bah, it's for wimps. ;-)

I'll take a look, thanks!

~swain

Lawrence Akka wrote:
> Steve (and others, but especially Steve),
> 
> When you write the flat-file db code (:-))  you might take a look at 
> http://ffdb-php.sourceforge.net/
> 
> It looks ideal to me.
> 
> Lawrence
> 
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 
> 
> 

[Phpwiki-talk] Flat-file database

[Lawrence A. <la...@us...>]

Steve (and others, but especially Steve),

When you write the flat-file db code (:-))  you might take a look at 
http://ffdb-php.sourceforge.net/

It looks ideal to me.

Lawrence

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki INSTALL,1.15,1.16

[Steve W. <sw...@pa...>]

Most unfortunate... I've becomee a recent convert to the school of 
"wikis need file uploads." We are using Twiki here at my new job (about 
which I'll write more some day), and the ability to attach Word or Visio 
docs to a page is very useful.

~swain

ph...@de... wrote:
> On Tue, 26 Feb 2002 18:16:37 -0800 (PST), "Jeff Dairiki"
> <da...@da...> wrote:
> => I think 4.0.4pl1 was the unspoken standard, and would be fine.  As
> => Reini says, it's in quite common use.  IIRC, it's the first version
> => of PHP 4 which didn't have big bugs.  (BTW, 4.0.4pl1 came after 4.0.4.
> => "pl" stands for "patch level", I think.  It's a ("doh!") stupid
> => bug-fix release, I think.)
> 
> You had to tempt fate, didn't you?  <grin>
> 
> PHP 4.1.2 was released today because almost all previous PHP
> versions have a security flaw related to the mime upload type,
> which may allow a remote attacker to execute arbitrary code. It
> appears this would afect PHP installed at a CGI in addition to
> the PHP module for Apache.
> 
> More info:
> http://security.e-matters.de/advisories/012002.html
> http://www.php.net/
> 
> 	HTH,
> 
> 	- Don
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 
> 
> 
> 

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki INSTALL,1.15,1.16

[<ph...@de...>]

On Tue, 26 Feb 2002 18:16:37 -0800 (PST), "Jeff Dairiki"
<da...@da...> wrote:
=> I think 4.0.4pl1 was the unspoken standard, and would be fine.  As
=> Reini says, it's in quite common use.  IIRC, it's the first version
=> of PHP 4 which didn't have big bugs.  (BTW, 4.0.4pl1 came after 4.0.4.
=> "pl" stands for "patch level", I think.  It's a ("doh!") stupid
=> bug-fix release, I think.)

You had to tempt fate, didn't you?  <grin>

PHP 4.1.2 was released today because almost all previous PHP
versions have a security flaw related to the mime upload type,
which may allow a remote attacker to execute arbitrary code. It
appears this would afect PHP installed at a CGI in addition to
the PHP module for Apache.

More info:
http://security.e-matters.de/advisories/012002.html
http://www.php.net/

	HTH,

	- Don

Re: Fwd: [Phpwiki-talk] PHPSESSID woes

[Lawrence A. <la...@us...>]

Did you read the comments as well ? ;-)

<extract from comments>
You can add this line into index.php to prevent it: 
ini_set('session.use_trans_sid', 0);
</extract>

At 10:52 27/02/2002, you wrote:
>>Have a look at 
>>http://sourceforge.net/tracker/index.php?func=detail&aid=504020&group_id=6121&atid=106121
>>
>>and see if that  helps
>>
>>Lawrence
>
>Erm, not really. How do I stop it happening?
>
>John.
>--
>
>---------------------------------------------------------
>email:  jo...@ke...         phone:      07944 755613
>web:     www.kershaw.org    AOL: johnkershaw
>---------------------------------------------------------

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki/lib Theme.php,1.43,1.44

[Lawrence A. <la...@us...>]

I tried that.  It looks awful on my Windows server.  Dates appear as 
"02/27/2002" (even though my Windows locale settings specify the UK 
convention of 27/2/2002, and I prefer February 27, 2002 in any event), and 
times appear as 08:23:45 (and I would prefer them with the seconds part).

You can, of course, specify the settings in the theme itself, by overriding 
the setDateFormat and setTimeFormat funcitons.

Lawrence

At 20:52 26/02/2002, you wrote:
>Lawrence Akka schrieb:
> > Workaround absence of %e date format specifier in Windows strftime 
> function.
> > See code for comments
> > +    // As a result, we have to use %d, and strip out leading zeros 
> ourselves.
> > +
> > +    var $_dateFormat = "%B %d, %Y";
> >      var $_timeFormat = "%I:%M %p";
>
>I would really prefer %x and %X because these are the recommended local
>settings.
>so one doesn't have to fix this for his locale.
>
>themes/*/themeinfo.php:
>$Theme->setDateFormat("%x");
>$Theme->setTimeFormat("%X");
>
>lib/Themes.lib:
>     //var $_dateFormat = "%B %d, %Y";
>     //var $_timeFormat = "%I:%M %p";
>     $_dateFormat = "%x";
>     $_timeFormat = "%X";
>
>docs:
>%x - preferred date representation for the current locale without the time
>%X - preferred time representation for the current locale without the date
>
>these do work in windows.
>--
>Reini Urban
>http://xarch.tu-graz.ac.at/home/rurban/
>
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Fwd: [Phpwiki-talk] PHPSESSID woes

[Lawrence A. <la...@us...>]

Morning John.

Have a look at 
http://sourceforge.net/tracker/index.php?func=detail&aid=504020&group_id=6121&atid=106121

and see if that  helps

Lawrence




>Hi,
>
>Quite often people arrive at my site then, after clicking a link, find 
>they've got &PHPSESSID=blahblahblah tagged to the end of their URL. This 
>then screws up the next link they click, so clicking the wikiword:
>
>BurleyGreenWall
>
>takes them to the page
>
>BurleyGreenWall& (or BurleyGreenWall%26)
>
>which of course doesn't exist, and causes them to wonder what went wrong.
>
>What's causing this and how do I stop it?
>
>John.
>--