phpwiki-talk

Re: [Phpwiki-talk] help creating a new UserPreference

[Reini U. <ru...@x-...>]

Carsten Klapp schrieb:
> I'm trying to add a new preference to PhpWiki but I'm not doing very well
> with it.
> checkbox: "Display TextFormattingRules while editing."

Fine.
But I'd rather appreciate user-definable themes. 
just a pulldown of all available themes, stored in the cookie. (optionally
only)
-- 
Reini Urban
  http://atelier.akbild.ac.at/ (soon)
  http://xarch.tu-graz.ac.at/home/rurban/ (big)
  http://tv.mur.at/ (kulturelles)

Re: [Phpwiki-talk] Re: 1.4 release

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

On 29 Jan 2002 16:56:52 -0800, Adam Shand
<ad...@pe...> wrote:


=> would you mind mailing a url to a screenshot or something?  i'm curious
=> what you've done.
	<snip>
=> i run a public wiki and had similar complaints from users and concerns
=> from myself.  one of the biggest things i didn't/don't like was that
=> with the standard wiki "look and feel" is that there is no site
=> consistancy.  it's very space efficient which is great when you are are
=> familiar with the site but for people who found a page on our site from
=> another site (or google) they had no idea what we, as a whole, were
=> about and there was no immediately obvious way for them to find out. 
=> you can see the really ugly hack i did to moinmoin here:
=>  http://www.personaltelco.net/

	You did a very nice job with yours and one can see by the
content how well it's working for you.  My changes don't improve
over yours, except perhaps in one area: I use a light pastel type
color for the background on the left column, the right title
area, the bottom non-content area, *and* a small right hand empty
column (tables) to visually frame the content - this "pops" the
content up into view more and pushes the non-content back down a
bit as well, and it gives more white space all around the
content, making it appear less dense (which is a good thing).

	I really like what you've done.  Your cute little icons
are nice as well and you might add a little "home" icon for your
front page (as I think many folks like to start over easily from
deep within content - and yes i did the same logo link in the
upper left corner but you need to know that's a home link - what
a long parenthetical comment, oh well....).

	Only other thing I did was to put two very prominent
EditText-type links in the left column to make it real easy and
obvious how to update the page.

	You did a nice consistent job with the edit page as well.
It seems like no matter what one does however, it's still much
too geeky.

	Finally, (with your indulgence) I like your logo but if
it were mine I'd shrink it down a bit to take up less of the
prime screen area. It does provide a good graphic consistency
from one page to the next.

	I like what you've done and gotten a couple ides for some
that I'd like to do as well.  I'll see where the "stable" daily
CVS is on the day I pull the phpwiki-lottery handle and go from
there.

	Thanks for the link. i think it helps to see how
different folks are formatting Wikis. I completely agree with
your other comments on look-and-feel.

	Cheers,

	- Don

[Phpwiki-talk] Nice wiki interface

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

Just come across a rather nice wiki interface at 
http://www.langreiter.com/space/start

I particularly like the navigation features, and the backlinks sidebar

Larwrence

[Phpwiki-talk] help creating a new UserPreference

[Carsten K. <car...@ma...>]

Hi,
I'm trying to add a new preference to PhpWiki but I'm not doing very well 
with it.

checkbox: "Display TextFormattingRules while editing."

I've added a new preference to the array in main.php and set up the 
userprefs.tmpl but the checkmark always comes up checked (or always 
unchecked). I'd like to add another preference to also allow 
context-sensitive plugin help on the edit screen, but just trying to get 
this simple pref to work I'm ready to pull my hair out.

Thanks for your help,
Carsten

main.php
'editHelpTfr' => new _UserPreference(true),
also tried
'editHelpTfr' => new _UserPreference_int(1,0,1),

userprefs.tmpl
<?php
if ($request->getPref('editHelpTfr')) {
   $editHelpTfrCB = HTML::input(array('type' => 'checkbox',
                                      'name' => 'pref[editHelpTfr]',
                                      'value' => 
$request->getPref('editHelpTfr'),
                                      'checked' => 'checked'
                                      ));
} else {
   $editHelpTfrCB = HTML::input(array('type' => 'checkbox',
                                      'name' => 'pref[editHelpTfr]',
                                      'value' => 
$request->getPref('editHelpTfr')
                                      ));
?>

Re: [Phpwiki-talk] Re: 1.4 release

[Reini U. <ru...@x-...>]

Steve Wainstead schrieb:
> That said, are we ready for a 1.3.3 yet before the new parser is
> incorporated?

sure. the new parser works fine enough for me, the interface also.
i would consider it stable enough, BUT ... (you know Jeff and Carsten)
they are in terrible good flux now and a lot of plugin's are still waiting.

re parser: still missing are block level tags, like <nowiki> linebreak(s)
</nowiki> 
and such, for easily pasting code.

BTW: I use the daily updated alpha CVS version for my stable and public 
wiki. there's no major error or flaw, it's just getting and better.
-- 
Reini Urban
  http://atelier.akbild.ac.at/ (soon)
  http://xarch.tu-graz.ac.at/home/rurban/ (big)
  http://tv.mur.at/ (kulturelles)

Re: [Phpwiki-talk] Re: 1.4 release

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

> 	Thanks for asking.  Most of what I've done is
> user-specific style, layout and formatting, with a few minor hack
> bits thrown in for navigation as well. Nothing really that ports,
> I'm afraid. Look and feel stuff.

would you mind mailing a url to a screenshot or something?  i'm curious
what you've done.
 
> 	Biggest formatting change is to move almost all the links
> etc to the left side of each page (table) which makes the wiki
> easier to navigate IMO, especially for new visitors. Whitespace
> and page blocking is important IMO, the standard Wiki is too
> text-dense on the page. Sorry I don't have a publicly visible
> example of my formatting changes at the moment.

i run a public wiki and had similar complaints from users and concerns
from myself.  one of the biggest things i didn't/don't like was that
with the standard wiki "look and feel" is that there is no site
consistancy.  it's very space efficient which is great when you are are
familiar with the site but for people who found a page on our site from
another site (or google) they had no idea what we, as a whole, were
about and there was no immediately obvious way for them to find out. 
you can see the really ugly hack i did to moinmoin here:

 http://www.personaltelco.net/

my long term goal on what i will do is have a a small navigation bar
across the top and bottom (edit, like pages, spell check, attach file
etc) and then down teh side have the equivelent of slashboxes for these
things:

* if not logged in get an intro to wiki box (welcome, yes your supposed
  to be able to edit the pages and please do ... responsibly).
* if they are logged in the get the last X  number of recent changes or
  maybe full recent changes or recent edits.
* the X most popular wiki pages
* the list of categories on the wiki (eg CategoryCategory)

other ideas for boxes:

* relevant rss/rdf feeds from other sites (weblogs, wiki's etc)
* a page status box (number of pages, hits/minute/etc ... geek stuff)
* maybe a calendar with upcoming events
* maybe a list of the X most active wiki users (friendly competition can
  be a good motivator :-)
* an rdf/rss of the last X messages from our mailing list (i don't know
  why no one has written a parser for mailman yet)
* a unified recent changes for all of the other community networking
  groups
* recent changes from our node map database
* the list goes on and on :-)

ideally all of these boxes would be imported from rss/rdf sources and
parsed with something like fase4php.  even more ideally all of this
would be configurable on a per user basis (to control which or if there
are any boxes).

so ... there's my grand scheme of things that i'm slowly working
towards, i'd love to hear about what you're trying to achive and what
you've done so far to get there.  our wiki is a crucial part of the
personal telco community (in someways it's built stronger ties then our
mailing list, though it has built much fewer).  it's also our main
presence to the world which is important as well.

adam.

Re: [Phpwiki-talk] Re: 1.4 release

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

On Tue, 29 Jan 2002 17:35:26 -0500, Carsten Klapp
<car...@ma...> wrote:
=> The latest 1.3 uses a regular web page with an input form for logins 
=> instead of the old http authentication method. As before, only the admin 
=> has a password. Does this address the authentication problem with the cgi 
=> version of php you had?

	Sorry, haven't really looked too terribly closely at the
details of 1.3 as I was waiting with hope for the next release
and 1.3 has so far always been referred to as alpha code.

	My current phpWiki uses straight standard Apache
.htaccess control for http server access to the entire site
(directory level) and also separately for more limited access to
the admin.php file itself.  BTW, I was looking to tack on a front
end for user verification and really liked the way it looked as
running inside PostNuke (www.postnuke.org).

	For several reasons (including use on shared servers),
I'm restricted to PHP as CGI as a standard but I run it "wrapped"
under my user to closely control its use by Apache.

=> What kind of hacks do you have in your 1.2, anything worth sharing? Or any 
=> new features we might consider adding in at some point?

	Thanks for asking.  Most of what I've done is
user-specific style, layout and formatting, with a few minor hack
bits thrown in for navigation as well. Nothing really that ports,
I'm afraid. Look and feel stuff.

	Biggest formatting change is to move almost all the links
etc to the left side of each page (table) which makes the wiki
easier to navigate IMO, especially for new visitors. Whitespace
and page blocking is important IMO, the standard Wiki is too
text-dense on the page. Sorry I don't have a publicly visible
example of my formatting changes at the moment.

	One complaint I encountered with my user base was that
the navigation (outside of the wiki text itself) was not up to
their expectations and not standardized.  The other "complaint"
was that it was just too egalitarian: "whaddayamean I can just
type in changes to this page right here and now?"

	Cheers,

	- Don

Re: [Phpwiki-talk] Re: 1.4 release

[Carsten K. <car...@ma...>]

Hi Don,

The latest 1.3 uses a regular web page with an input form for logins 
instead of the old http authentication method. As before, only the admin 
has a password. Does this address the authentication problem with the cgi 
version of php you had?

What kind of hacks do you have in your 1.2, anything worth sharing? Or any 
new features we might consider adding in at some point?

:-)
Carsten

On Tuesday, January 29, 2002, at 05:25  pm, ph...@de... wrote:
>
> 	I have to pick something fairly soon as a new stable base
> to then include some of my enduser-specific hacks from 1.2 and
> I'm not as likely to be able to do this line-in-the-sand again
> for some quite a period of time.

Re: [Phpwiki-talk] Re: 1.4 release

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

On Tue, 29 Jan 2002 ph...@de... wrote:

> 	I have no complaints whatsoever, you folks have done a
> terrific job with phpWiki and I love the install I've hacked from
> the 1.2 path.

I'm sure all the developers appreciate this, Don! Thanks.

> 	On requests: I was pushing for a stable release soon, as
> it sounds to me like a whole new great-leap-forward is happening
> now ... exciting but linear-time-consuming is how it sounds.
>
> 	I have to pick something fairly soon as a new stable base
> to then include some of my enduser-specific hacks from 1.2 and
> I'm not as likely to be able to do this line-in-the-sand again
> for some quite a period of time.
>
> 	Suggestions: ignore me and stay creative.  I'll find a
> way to get by. I'll just grumble to myself about how the world
> could be a better place if volunteer,non-paid phpWiki developers
> would just take even less time sleeping and spend more time
> coding like they should <g>.

And I'm sure they appreciate the humor :-)

It's an understatement to say I've admin'd this project loosely over the
last six or so months (even an understatement to say I've admin'd it!) But
I've really enjoyed all the energy being poured into PhpWiki and I'm
reluctant to stop it now with milestones and release dates. However, it's
not too farfetched to agree on what features we will wait for before 1.4
is released (2.0 is more likey the version number).

That said, are we ready for a 1.3.3 yet before the new parser is
incorporated?

~swain

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

Re: [Phpwiki-talk] Re: 1.4 release

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

On Tue, 29 Jan 2002 11:47:15 -0800, Jeff Dairiki
<da...@da...> wrote:
=> The latest CVS code (as of last week, I think) should work.  I have not
=> tested it (except under mod_php), nor have I heard any reports (success or
=> failure) about it.

	Thanks, but I get nervous about "latest CVS" copies. I
can barely spell CVS and I really don't know when to dip into
that river, nor what to expect.
 
=> (There's still no real user authentication.  But bogo-logins (or signins)
=> and admin logins should work...)

	Ok, thanks. 

=> I'm not sure I understand the rest of your comments.

	Sorry.

=>  I get the idea that you are not happy with the current state of PhpWiki affairs,

	Just the release schedule and that's just chomping at the
bit on my part. Open-ended feature sets make me nervous when I'm
an expectant enduser.

=> but I don't think I understand why very well.  Could you try restating your
=> complaints/suggestions/requests?

	I have no complaints whatsoever, you folks have done a
terrific job with phpWiki and I love the install I've hacked from
the 1.2 path.

	On requests: I was pushing for a stable release soon, as
it sounds to me like a whole new great-leap-forward is happening
now ... exciting but linear-time-consuming is how it sounds.

	I have to pick something fairly soon as a new stable base
to then include some of my enduser-specific hacks from 1.2 and
I'm not as likely to be able to do this line-in-the-sand again
for some quite a period of time.
 
	Suggestions: ignore me and stay creative.  I'll find a
way to get by. I'll just grumble to myself about how the world
could be a better place if volunteer,non-paid phpWiki developers
would just take even less time sleeping and spend more time
coding like they should <g>.

	Thanks for everything,

	- Don

Re: [Phpwiki-talk] Re: 1.4 release

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

On 29 Jan 2002 13:03:16 -0800, Adam Shand
<ad...@pe...> wrote:
=> nnnoooooooo! :-)  1.3 really hasn't been around that long.  i think
=> getting the wiki markup and new parsing engine going is an important
=> thing to happen before another stable release.  otherwise it's just that
=> many more people that are going to have to go through a major overhaul
=> on their web site.

	OK, you're probably right.

=> i have yet to put phpwiki into production for myself but i've played
=> with it a lot and run several 1.3 wiki's for other people and its been
=> pretty uneventful.  

	Uneventful is nice especially when it's still labeled as
alpha code.

=> also upgrading is fairly painless,
	<snip step by step>

	Thanks for the instructions, appreciated.

=> i know it's not ideal, and i'm looking forward to a stable release as
=> well, but *good things* are happening, lets not ruin our wonderful
=> developers momentum :-)

	Well, that's really the ultimate criterion: I do _not_
want to do anything to stifle or trip-up the developers.  I
wasn't really going to post and perhaps I shouldn't have.  It is
a great little app; I'd just like to get it into some sort of
stable production on a couple of things without missing too much
of the future and without waiting too long. <sigh>

	Thanks to all the developers.  phpWiki is great and
getting even better thanks to your efforts - they are
appreciated. Take your time, anytime next week will be fine <g>.

	Cheers,

	- Don

Re: [Phpwiki-talk] Re: 1.4 release

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

> 	I love phpWiki but I sure wish we could have more
> "stable" versions and a less lengthy open-for-development alpha
> code stretch. I don't mean to be rude, I really do thank everyone
> very much  for all their efforts on behalf of the unwashed
> WikiMasses like me, but how about putting new major markup
> changes into the next major release level?

nnnoooooooo! :-)  1.3 really hasn't been around that long.  i think
getting the wiki markup and new parsing engine going is an important
thing to happen before another stable release.  otherwise it's just that
many more people that are going to have to go through a major overhaul
on their web site.
 
> 	This is such a great system, it's hard to wait for months
> to be able to grab a stable version to use as a base for real
> life.  Guess I shouldn't look the gifthorse in the mouth but
> alpha code is only fun for the developers.

i have yet to put phpwiki into production for myself but i've played
with it a lot and run several 1.3 wiki's for other people and its been
pretty uneventful.  

also upgrading is fairly painless, if you keep all the libs out of the
DocumentRoot (which you should do anyway) and use a seperate directory
for your databases (or use sql).  just untar the source into
/var/lib/phpwiki-1.3.4 (or whatever) and then change the pointers in
index.php to point to the new location.  if it causes problems just roll
back.  if you want to be really careful copy index.php to testwiki.php
and change that first.  that way you can test it out without
interrupting your live wiki.

i know it's not ideal, and i'm looking forward to a stable release as
well, but *good things* are happening, lets not ruin our wonderful
developers momentum :-)

adam.

[Phpwiki-talk] Re: 1.4 release

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

On Mon, 28 Jan 2002 21:00:22 -0800, Jeff Dairiki
<da...@da...> wrote:
=> Yes, and I've just about got a new inline markup parser working too.
=> I think we should wait awhile (month or two?) to make sure we all agree
=> on just what the new markup syntax should be.

	<groan>.  Looks like it's 1.3.x for my base now (and a
bunch of hacking ahead, to be forever cemented-in).  Has 1.3.x
been updated to not require PHP module authentication for some of
us on shared servers who use PHP running CGI "wrapped" for
security?

	I love phpWiki but I sure wish we could have more
"stable" versions and a less lengthy open-for-development alpha
code stretch. I don't mean to be rude, I really do thank everyone
very much  for all their efforts on behalf of the unwashed
WikiMasses like me, but how about putting new major markup
changes into the next major release level?

	This is such a great system, it's hard to wait for months
to be able to grab a stable version to use as a base for real
life.  Guess I shouldn't look the gifthorse in the mouth but
alpha code is only fun for the developers.

	Please forgive the rant.

	Thanks,

	- Don

Re: 1.4 release (was Re: [Phpwiki-talk] Something very weird has happened to my Wiki)

[Jeff D. <da...@da...>]

>  From my view the only remaining requirement I'd like to see met before
a 1.> 4 release, is updated locale translations. German is complete but
Swedish,>   Dutch, Italian are still at a 1.2 level or slightly above. I
don't think > an incomplete French translation should hold up a 1.4
release, really it's > work has just begun (so there's no need to rush
that one).

Actually, the translations are the one thing that, I think, shouldn't hold
up the release.  It's great if the translations are up-to-date, but, if I
were a translator, I would wait for a stable release _before_ really
working hard to clean up the translations.  The translations can always be
updated in 1.4.n.
 
> The new block parser and New Wiki Markup is in progress.

Yes, and I've just about got a new inline markup parser working too.
I think we should wait awhile (month or two?) to make sure we all agree
on just what the new markup syntax should be.

Re: 1.4 release (was Re: [Phpwiki-talk] Something very weird has happened to my Wiki)

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

> > The new block parser and New Wiki Markup is in progress.
> 
> yes, this is very new and should settle a bit.

i just wanted to say thanks to everyone.  i just checked the new block
parser out yesterday and it's amazing, i especially like the new table
syntax.

thanks!
adam.

Re: 1.4 release (was Re: [Phpwiki-talk] Something very weird has happened to my Wiki)

[Reini U. <ru...@x-...>]

Carsten Klapp schrieb:
> I'm not sure what the general consensus is about moving to a 1.4 release
> version.

not now, after the recent changes.

>  From my view the only remaining requirement I'd like to see met before a 1.
> 4 release, is updated locale translations. German is complete but Swedish,
>   Dutch, Italian are still at a 1.2 level or slightly above. I don't think
> an incomplete French translation should hold up a 1.4 release, really it's
> work has just begun (so there's no need to rush that one).
> 
> The new block parser and New Wiki Markup is in progress.

yes, this is very new and should settle a bit.

> What else do we have going before another 1.3 release or a 1.4 release?
-- 
Reini Urban
  http://atelier.akbild.ac.at/ (soon)
  http://xarch.tu-graz.ac.at/home/rurban/ (big)
  http://tv.mur.at/ (kulturelles)

Re: [Phpwiki-talk] Working version of phpwiki on Win32?

[Lawrence A. <Law...@th...>]

I am running it on one of my systems, although it only has one user (me)

Using Foxserv, ie PHP 4.0.6, Apache (cant remember - most recent version i think) and 
phpWiki 1.3.2 (and cvs code), all on Windows XP and also 2000 without major 
problems

Apache terminates a thread every now and then, but I think that's just Apache's 
problem.

Try setting the include path variable in the index.php file.  Don't forget, Windows uses 
semicolons instead of colons, so you need something like 

ini_set('include_path', ".;c:/path/to/phpwiki/files");

You may also need to include the path of the PEAR DB file there.  Note, PHP doesn't 
seem to mind forward slashes in file paths, and it is easier to use them to avoid 
problems with escape characters.


Lawrence Akka

===============================================================
 Anyone running phpwiki on Win32?  If so what versions of
phpwiki, PHP and (perhaps) MySQL are you using?



Running the latest phpwiki with PHP 4.1.0 caused a fault in PHP(!).

Running with the newer

Versions I'm using (unsuccessfully) on Windows 2000:

PHP 4.1.1
mysql  Ver 11.15 Distrib 3.23.47, for Win95/Win98 (i32)

Error from running PhpWiki 1.2.2:
-----
Warning: Failed opening 'lib/mysql.php' for inclusion (include_path='..') in
C:\tools\phpwiki-1.2.2\lib\config.php on line 111
Fatal error: Call to undefined function: opendatabase() in
C:\tools\phpwiki-1.2.2\index.php on line 14
-----

Error from running PhpWiki 1.3.2:
-----
Fatal error: Failed opening required 'lib/ErrorManager.php'
(include_path='..') in C:\tools\phpwiki-1.3.2\lib\prepend.php on line 11
-----

Is there a problem with include_path on Win32?

I did pull out the current PHP sources from CVS to take a look.
Punted after looking at the PHP build workspace/project.
Too much rework needed... :).


_______________________________________________
Phpwiki-talk mailing list
<EMAIL: PROTECTED>
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] Working version of phpwiki on Win32?

[Reini U. <ru...@x-...>]

"Preston L. Bannister" schrieb:
> Anyone running phpwiki on Win32?  If so what versions of
> phpwiki, PHP and (perhaps) MySQL are you using?

yes, runs fine on apache-1.3.20 / php-4.0.6 / mysql-3.23.40-max-nt 
and on on the newest setup msvc apache-1.3.22 / php-4.1.1 (much faster)

but fails on the pear session lib with mysql, so i think that there's is a 
bug in the php mysql session code in 4.1.x. with fs-sessions it works fine.

It does work on the latest cygwin apache setup, but I couldn't yet 
compile libmysql for a newer cygwin.

I cvs up daily and it it always runs fine.

> Running the latest phpwiki with PHP 4.1.0 caused a fault in PHP(!).
-- 
Reini Urban
  http://atelier.akbild.ac.at/ (soon)
  http://xarch.tu-graz.ac.at/home/rurban/ (big)
  http://tv.mur.at/ (kulturelles)

1.4 release (was Re: [Phpwiki-talk] Something very weird has happened to my Wiki)

[Carsten K. <car...@ma...>]

I'm not sure what the general consensus is about moving to a 1.4 release 
version.

 From my view the only remaining requirement I'd like to see met before a 1.
4 release, is updated locale translations. German is complete but Swedish,
  Dutch, Italian are still at a 1.2 level or slightly above. I don't think 
an incomplete French translation should hold up a 1.4 release, really it's 
work has just begun (so there's no need to rush that one).

The new block parser and New Wiki Markup is in progress.

What else do we have going before another 1.3 release or a 1.4 release?

(I'm not necessarily pushing for a 1.4 release myself, just responding to 
Don's q.)

Carsten

On Monday, January 28, 2002, at 01:44  pm, ph...@de... wrote:

> On 13 Jan 2002 13:28:56 -0800, Adam Shand
> <ad...@pe...> wrote:
> => i was talking about a 1.4 release, something that people could use in
> => production services.  i'm really enjoying watching the improvements
> => being made in the 1.3 tree though.  this was more a question of "should
> => i wait for 1.4 or should i just plunge in and deal with 1.3 cause 1.4 
> is
> => a long way away :-).
>
> 	I've been wrestling with the same question for some time
> now and it sounds like 1.3 is the answer as 1.4 has more to do.
>
> 	As a wiki-lover and user (and not one of the developers),
> I'd like to see freezing 1.3.x and rolling it to 1.4, dropping
> status/support from 1.2 and moving to release of 1.4 as non-alpha
> code.
>
> 	Thanks to all for such a great system.
>
> 	Cheers,
>
> 	- Don

[Phpwiki-talk] Working version of phpwiki on Win32?

[Preston L. B. <pre...@sp...>]

Anyone running phpwiki on Win32?  If so what versions of
phpwiki, PHP and (perhaps) MySQL are you using?

Running the latest phpwiki with PHP 4.1.0 caused a fault in PHP(!).

Running with the newer

Versions I'm using (unsuccessfully) on Windows 2000:

PHP 4.1.1
mysql  Ver 11.15 Distrib 3.23.47, for Win95/Win98 (i32)

Error from running PhpWiki 1.2.2:
-----
Warning: Failed opening 'lib/mysql.php' for inclusion (include_path='..') in
C:\tools\phpwiki-1.2.2\lib\config.php on line 111
Fatal error: Call to undefined function: opendatabase() in
C:\tools\phpwiki-1.2.2\index.php on line 14
-----

Error from running PhpWiki 1.3.2:
-----
Fatal error: Failed opening required 'lib/ErrorManager.php'
(include_path='..') in C:\tools\phpwiki-1.3.2\lib\prepend.php on line 11
-----

Is there a problem with include_path on Win32?

I did pull out the current PHP sources from CVS to take a look.
Punted after looking at the PHP build workspace/project.
Too much rework needed... :).

Re: [Phpwiki-talk] Something very weird has happened to my Wiki

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

On 13 Jan 2002 13:28:56 -0800, Adam Shand
<ad...@pe...> wrote:
=> i was talking about a 1.4 release, something that people could use in
=> production services.  i'm really enjoying watching the improvements
=> being made in the 1.3 tree though.  this was more a question of "should
=> i wait for 1.4 or should i just plunge in and deal with 1.3 cause 1.4 is
=> a long way away :-).

	I've been wrestling with the same question for some time
now and it sounds like 1.3 is the answer as 1.4 has more to do.  

	As a wiki-lover and user (and not one of the developers),
I'd like to see freezing 1.3.x and rolling it to 1.4, dropping
status/support from 1.2 and moving to release of 1.4 as non-alpha
code.

	Thanks to all for such a great system.

	Cheers,

	- Don

Re: [Phpwiki-talk] Interwiki link to phpwiki cvs

[Carsten K. <car...@ma...>]

Already have it. :-)

php-function http://www.php.net/manual/en/function.%s.php
php-lookup http://www.php.net/manual-lookup.php?pattern=
PhpWiki http://phpwiki.sourceforge.net/phpwiki/index.php?
PhpWikiAlpha http://phpwiki.sourceforge.net/alpha/
PhpWikiCvs http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpwiki/phpwiki/

On Sunday, January 27, 2002, at 07:14  pm, Lawrence Akka wrote:

> Had a quick thought.  What about an Interwiki link to the cvs code at SF.
>
> PhpWikiSource  http://cvs.sourceforge.net/cgi-
> bin/viewcvs.cgi/phpwiki/phpwiki/%s?rev=HEAD&content-
> type=text/vnd.viewcvs-markup
>
> (or something like that)
>
> so that PhpWikiSource:display.php will link to display.php in cvs
>
> Would do the change myself, but
>
> 1)  Wanted to know if good idea
>
> 2)  Too tired - bed time
>
> Lawrence

[Phpwiki-talk] Interwiki link to phpwiki cvs

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

Had a quick thought.  What about an Interwiki link to the cvs code at SF. 

PhpWikiSource  http://cvs.sourceforge.net/cgi- 
bin/viewcvs.cgi/phpwiki/phpwiki/%s?rev=HEAD&content-type=text/vnd.viewcvs-markup 

(or something like that) 

so that PhpWikiSource:display.php will link to display.php in cvs 

Would do the change myself, but 

1)  Wanted to know if good idea 

2)  Too tired - bed time 

Lawrence 

==========NOTICE==========
Internet e-mail is not necessarily secure or reliable.  Please let us know if you would like to establish a secure channel of communication.
This e-mail and any attachments are confidential and may be legally privileged. They are intended only for the use of the named recipient. If you are not the named or intended recipient, please notify us immediately. In such an event, you should not disclose the contents of this e-mail or any attachments to any other person, nor copy, print, store or use them in any manner whatsoever. Thank you for your co-operation.
Although we have taken precautions to minimize the risk of transmitting software viruses, you are advised to carry out your own virus checks on any attachments to this message.
Tel: +44 (0)207 842 1200
http://www.20essexst.com
pos...@20...

[Phpwiki-talk] CSS class names

[Jeff D. <da...@da...>]

Carsten Klapp said:
>
> Didn't remember I'd done that until I read my comments in the log:
>
> establishes (diff) as a wikiaction link, for hiding it in
> phpwiki-printer. css

> So I'm thinking of this... I'm not happy with this class name
> 'no-printer'
>  but can't think of anything better.

My first reaction is that, if it's going to have a class, it might
as well be something like 'wiki-rc-action', so that if someone does
ever want to buttonify them (or whatever) that have that freedom.



At some point, we really need to (re-)document, and establish some
standards as to what classes are used where in PhpWiki.   Probably
some renaming (for uniformity) and namespace cleanliness is in order.
Ugh.

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki phpwiki-heavy.css,1.7,1.8 phpwiki.css,1.25,1.26

[Carsten K. <car...@ma...>]

Didn't remember I'd done that until I read my comments in the log:

establishes (diff) as a wikiaction link, for hiding it in phpwiki-printer.
css

Besides hiding the diffs from printed output, there's no reason (for 
themes or whatnot) that it need be a wikiaction. The RecentChanges days 
buttons don't hide from the printer.css properly either.

So I'm thinking of this... I'm not happy with this class name 'no-printer'
  but can't think of anything better.

     function diffLink ($rev) {
         global $Theme;
!       return $Theme->makeButton(_("(diff)"), $this->diffURL($rev), 
'no-printer');
     }




                 $b->addButton($label, "RecentChanges?days=" .$daynum
                                       .$url_show_minor .$url_show_all,
                               'wikiaction');
             }
!           return HTML::div(array('class'=>'no-printer'), $b->getContent(
));
         }


On Friday, January 25, 2002, at 11:12  pm, Jeff Dairiki wrote:

> Carsten Klapp said:
>> I think I prefer the plain-text ones as well.
>>
>> Somewhere along the way to the new ButtonFactory the RecentChanges
>> '(diff) 's were converted into buttons...
>
> It was before that, I think.
>
> It used to be that the (diff) links were just plain links --- not
> tagged with any CSS class.  It was you who added the wikiaction class to 
> the
> diff links (v 1.16 of lib/plugin/RecentChanges.php):
> http://cvs.sf.net/cgi-
> bin/viewcvs.cgi/phpwiki/phpwiki/lib/plugin/RecentChanges.php.diff?r1=1.15&
> r2=1.16
> I think it's best we leave the .wikiaction and .wikiadmin classes
> signifying the links one might like buttonized (the links in the toolbars,
> and some of thes ones in PhpWikiAdministration.)
>
> I say just remove the wikiaction class designation from the "(diff)" 
> links.
> (Or I guess, if it's needed for some themes, make them be of yet another
> (new) class.)
>
> In other words, don't de-button them by changing the CSS, de-button them
> by changing the HTML.
>
>
>