phpwiki-talk

Re: [Phpwiki-talk] phpWiki and postnuke at Daimonin

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

Michael Toennies schrieb:
> We are the daimonin mmorpg project:
> http://www.daimonin.net
...
> What i fear is, that someone find a exploit in the hacked phpWiki.
> Its not active in development anymore and it has still issues.
> 
> Has the phpWiki community ever thought about to add a native postnuke
> interface? Postnuke lakes a native wiki. It has a very easy to use
> interface which allows it to bind in modules. Also, the changes would
> be normally not so hard - just a redirect to the postnuke permission
> system. Nearly all other parts from phpWiki fits in fine.

...

I started with testing phpnuke, postnuke and gforge integration about 
one and a half year ago.
For gforge I had to fix some phpwiki internal (nameclashes), postnuke 
should work fine with some minor tweaks similar to gforge, and phpnuke 
is just too dirty to get my hands upon.
The WhoisOnline plugin and graphics e.g. are directly from postnuke.

Right I'm too busy with the release and other things, but after that 
I'll happy to finish that integration.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban
http://phpwiki.org

AW: [Phpwiki-talk] phpWiki and postnuke at Daimonin

[Daimonin M. <in...@da...>]

Hm, i thought the postnuke phpwiki port is known?

http://stuff.kling.nu/

I use that module/port. I have not done any code or port for it -
i just use it and fixed 1-2 minor issues.

It seems i missed to explain the (beside security) only
and really only important point: That i can use *one*=20
permission system - the group/permission system of postnuke
to control the wiki.

Its the most important point. I would *never* install a 2nd
permission system using module. I want and i must use the
central permission system of postnuke to control the wiki
user & pages. This phpwiki postnuke port allow just that.

In fact i would even change the cms or write a own small doc
system when i had no choice instead of use the standalone permission
of phpwiki.

Daimonin has gotten around 3500 registered users in 6 weeks, we will =
have=20
soon 10.000 and more. With the many people having access to different
parts...
I described the reason in my first mail. (if i would use a different=20
CMS i would do the same, postnuke is just the cms is use).=20

I had to syncronize some different groups and permission groups which
access different modules & areas of the website (we talk about gallery,
forum, wiki...).
I need to see who has which right in one view. I must be able to change=20
it with one click. And other people with lesser permission in the=20
site should be able to build groups and assign their own people with
permissions.

All what i can say is, that we had bad experience with different modules
having
different permission. Very bad. With the central system, all works like =
a
charm
and it works fast and clean.

Sorry when it sounds like a rant, but its really the important point.

So, as i understand the phpwiki code, the permission system itself is
not that different as the one from postnuke. It should be possible
to relink the permission queries to postnuke and use their loged =
in/logout
system. The postnuke port does exactly that.

And what i can tell is, that if that is done, both system together works
wonderful.

> -----Urspr=FCngliche Nachricht-----
> Von: php...@li...=20
> [mailto:php...@li...] Im Auftrag=20
> von Joel Uckelman
> Gesendet: Mittwoch, 30. M=E4rz 2005 04:59
> An: php...@li...
> Betreff: Re: [Phpwiki-talk] phpWiki and postnuke at Daimonin=20
>=20
> Thus spake "Michael Toennies":
> > Hello
> >=20
> > We are the daimonin mmorpg project:
> > http://www.daimonin.net
> >=20
> > We use phpWiki as our main documentation & information=20
> central of our=20
> > postnuke site. I have to say that we are very happy with=20
> that solution=20
> > and its a great success.
> > Thank you guys!
> >=20
> > The only negative point is, that we can't use the original=20
> phpWiki but=20
> > a modified version which used the postnuke user permission=20
> interface.
> >=20
> > When you look at the site and you understand what we do you=20
> will see=20
> > how incredible useful the permission system is. We give access to=20
> > several parts of the website include site sub-admins, gallery album=20
> > owners, file system upload permission, forum permission, forum=20
> > moderator permission and at last write access to the wiki.
> >=20
> > Thats only (and really only, our old website had it not, so we know=20
> > where we talk about) possible with one central permission and group=20
> > system which gave us the Postnuke CMS.
> >=20
> > As a game (with much underage users), we need a stable & secure=20
> > permission system. A free wiki access is no option. In the=20
> old website=20
> > we had deleting and vandalism of pages every few hours.
> >=20
> > With the new webpage, we had not a single issue.
> >=20
> > When you look at the phpWiki of our site, you will notice=20
> how good it=20
> > fits in the CMS and how useful it is.
> >=20
> > What i fear is, that someone find a exploit in the hacked phpWiki.
> > Its not active in development anymore and it has still issues.
> >=20
> > Has the phpWiki community ever thought about to add a=20
> native postnuke=20
> > interface? Postnuke lakes a native wiki. It has a very easy to use=20
> > interface which allows it to bind in modules. Also, the=20
> changes would=20
> > be normally not so hard - just a redirect to the postnuke=20
> permission=20
> > system. Nearly all other parts from phpWiki fits in fine.
> >=20
> > It would be a win/win solution for both projects. Postnuke=20
> would get a=20
> > stable, tested & working wiki. phpWiki would get a=20
> incredible boost in=20
> > users and, i can ensure it as a open source project leader=20
> for years=20
> > now, alot more developer.
> >=20
> > Both project would gain ALOT for a little work.
> >=20
> > They would stay independed as projects but would gain through the=20
> > Synergy effect of the interface both a big boost.
> >=20
> > Michael Toennies
> > Daimonin MMORPG
>=20
> So, what you're doing is querying postnuke for user=20
> permissions? Is that the extend of your modifications?
>=20
> I haven't looked at our permissions system in a while---maybe=20
> it already is this way---but it would make some sense to have=20
> permissions queries work similarly to the way DB queries do.=20
> That is, have an abstract permissions interface which calls=20
> the appropriate permissions backend. That way, you guys could=20
> write a postnuke permissions backend and there would be no=20
> need for further changes to the code.
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide Read honest &=20
> candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] phpWiki and postnuke at Daimonin

[Joel U. <uck...@no...>]

Thus spake "Michael Toennies":
> Hello
> 
> We are the daimonin mmorpg project:
> http://www.daimonin.net
> 
> We use phpWiki as our main documentation & information
> central of our postnuke site. I have to say that we are
> very happy with that solution and its a great success. 
> Thank you guys!
> 
> The only negative point is, that we can't use the original
> phpWiki but a modified version which used the postnuke
> user permission interface.
> 
> When you look at the site and you understand what we do you will
> see how incredible useful the permission system is. We give access
> to several parts of the website include site sub-admins, gallery 
> album owners, file system upload permission, forum permission,
> forum moderator permission and at last write access to the wiki.
> 
> Thats only (and really only, our old website had it not, so we
> know where we talk about) possible with one central permission and
> group system which gave us the Postnuke CMS.
> 
> As a game (with much underage users), we need a stable & secure 
> permission system. A free wiki access is no option. In the old website
> we had deleting and vandalism of pages every few hours.
> 
> With the new webpage, we had not a single issue.
> 
> When you look at the phpWiki of our site, you will notice how good it 
> fits in the CMS and how useful it is.
> 
> What i fear is, that someone find a exploit in the hacked phpWiki.
> Its not active in development anymore and it has still issues.
> 
> Has the phpWiki community ever thought about to add a native postnuke
> interface? Postnuke lakes a native wiki. It has a very easy to use
> interface which allows it to bind in modules. Also, the changes would
> be normally not so hard - just a redirect to the postnuke permission
> system. Nearly all other parts from phpWiki fits in fine.
> 
> It would be a win/win solution for both projects. Postnuke would get
> a stable, tested & working wiki. phpWiki would get a incredible boost
> in users and, i can ensure it as a open source project leader for years now,
> alot more developer.
> 
> Both project would gain ALOT for a little work.
> 
> They would stay independed as projects but would gain
> through the Synergy effect of the interface both a big
> boost. 
> 
> Michael Toennies
> Daimonin MMORPG

So, what you're doing is querying postnuke for user permissions? Is that
the extend of your modifications?

I haven't looked at our permissions system in a while---maybe it already is
this way---but it would make some sense to have permissions queries work
similarly to the way DB queries do. That is, have an abstract permissions
interface which calls the appropriate permissions backend. That way, you
guys could write a postnuke permissions backend and there would be no need
for further changes to the code.

RE: [Phpwiki-talk] phpWiki and postnuke at Daimonin

[Charles C. <ch...@ru...>]

Hi,

Have looked at the latest PhpWiki security framework? In my opinion, it is quite complete. While I would not consider myself an
expert on the code, I did some testing and patching in the past 4 months with an emphasis on security and wrote doc/README.security
to capture what I learned.

There are several layers to PhpWiki's security framework and implementations.

The first is the identification and authentication. This can be provided by several different mechanisms, including (but not limited
to): database, ldap or wikipage.

The next layer is group membership. Some are builtin groups and the other group memberships can be provided by at least two
different mechanisms (database and wikipages). A user may be a member of multiple groups.

The final layer is page permissions. Each group may have varying permissions to a page.  The page group permissions are attached to
pages in a hierarchical manner - if there is no relevant permission defined for a page, its parent is checked.

If the PostNuke security structure is roughly analogous to this, it should be easy to extend PhpWiki to use PostNuke's
identification, authentication and group memberships. However, it could be quite difficult to modify the page level permission
system.

I suggest that you first look at doc/README.security to learn about one way to secure PhpWiki (there are several alternatives) and
then look at the layers I described above to see if it is worthwhile for you to follow up further.

Regards,
Charles

-----Original Message-----
From: Michael Toennies [mailto:mic...@da...] 
Sent: 29 March 2005 21:53
To: php...@li...
Subject: [Phpwiki-talk] phpWiki and postnuke at Daimonin

Hello

We are the daimonin mmorpg project:
http://www.daimonin.net

<snip>

Has the phpWiki community ever thought about to add a native postnuke
interface? Postnuke lakes a native wiki. It has a very easy to use
interface which allows it to bind in modules. Also, the changes would
be normally not so hard - just a redirect to the postnuke permission
system. Nearly all other parts from phpWiki fits in fine.

[Phpwiki-talk] phpWiki and postnuke at Daimonin

[Michael T. <mic...@da...>]

Hello

We are the daimonin mmorpg project:
http://www.daimonin.net

We use phpWiki as our main documentation & information
central of our postnuke site. I have to say that we are
very happy with that solution and its a great success. 
Thank you guys!

The only negative point is, that we can't use the original
phpWiki but a modified version which used the postnuke
user permission interface.

When you look at the site and you understand what we do you will
see how incredible useful the permission system is. We give access
to several parts of the website include site sub-admins, gallery 
album owners, file system upload permission, forum permission,
forum moderator permission and at last write access to the wiki.

Thats only (and really only, our old website had it not, so we
know where we talk about) possible with one central permission and
group system which gave us the Postnuke CMS.

As a game (with much underage users), we need a stable & secure 
permission system. A free wiki access is no option. In the old website
we had deleting and vandalism of pages every few hours.

With the new webpage, we had not a single issue.

When you look at the phpWiki of our site, you will notice how good it 
fits in the CMS and how useful it is.

What i fear is, that someone find a exploit in the hacked phpWiki.
Its not active in development anymore and it has still issues.

Has the phpWiki community ever thought about to add a native postnuke
interface? Postnuke lakes a native wiki. It has a very easy to use
interface which allows it to bind in modules. Also, the changes would
be normally not so hard - just a redirect to the postnuke permission
system. Nearly all other parts from phpWiki fits in fine.

It would be a win/win solution for both projects. Postnuke would get
a stable, tested & working wiki. phpWiki would get a incredible boost
in users and, i can ensure it as a open source project leader for years now,
alot more developer.

Both project would gain ALOT for a little work.

They would stay independed as projects but would gain
through the Synergy effect of the interface both a big
boost. 

Michael Toennies
Daimonin MMORPG

Re: Releasing (WAS: Re: [Phpwiki-talk] Re: [phpwiki - Help] RE: Wiki is getting spammed pretty bad)

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

> Reini Urban wrote:
> | Remaining issues are locale problems (could not reproduce them so
> far),
>
> As far as we've investigated, it seems that the locale problem comes
> from badly or no installed locale on the server and the $LANG global
> that doesnt setup properly.
>
> If you set $LANG to your locale, it works but you can't change it
> anymore in your user prefs.
>
> Still investigating :)

Is it fixed with rc1?


-- 
Reini Urban
http://phpwiki.org/   http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Release Candidate 1

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

I've made available a release candidate 1, which should fix most of the
problems.

Known problems to be done:

* wikiadmin plugin problems with subpages (rename, ...)
*   in diff #1169504
* accept email with + #1166336
* cannot embed plugins in RichTable plugin

Fixed in last week:
* locale
* configurator
* pop3 auth
* adodb authinfo security flaw

Hope I'll come to the remaining issues tomorrow, but our wave is that 
high this weekend, so I'll rather go surfing and fix the rest during the 
next week.
Sorry for the one month delay because of my new job, local permission 
problems and the austrian filmfestival.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
http://phpwiki.org/

[Phpwiki-talk] Missing content after text field on 'editpage'. update.

[Micki K. <mic...@co...>]

Hi again.

Sorry to lambaste the list with this - but I found the issue.

It's our old friend 'OldTextFormattingRules'. I used to know the 
exact part of the file that caused the trouble, but for now, I just 
wiped it.

Thanks!
Micki



>Hi folks.
>
>It's only omitting the content below the 'edit' box on pre-existing 
>pages. On new pages, it's showing the submit, but then after 
>entering text and clicking, nothing is saved.
>
>Does it sound like a permissions error to you also?
>
>Thanks,
>Micki
>
>>Hi folks.
>>
>>Having a little trouble with a clone version of my wiki.
>>
>>In 'edit' mode, nothing appears in the page after the 'textentry' 
>>field. And the source of the html page ends at the end of the 
>>wikitext... in other words, no 'summary' or submit buttons, etc.
>>
>>Any clue why this might be happening? I've compared the php.ini 
>>files between the two systems closely and although there are 
>>differences, none seem able to cause this.
>>
>>Thanks for any anecdotal experience or tips you can provide.
>>Micki
-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Missing content after text field on 'editpage'. update.

[Micki K. <mic...@co...>]

Hi folks.

It's only omitting the content below the 'edit' box on pre-existing 
pages. On new pages, it's showing the submit, but then after entering 
text and clicking, nothing is saved.

Does it sound like a permissions error to you also?

Thanks,
Micki

>Hi folks.
>
>Having a little trouble with a clone version of my wiki.
>
>In 'edit' mode, nothing appears in the page after the 'textentry' 
>field. And the source of the html page ends at the end of the 
>wikitext... in other words, no 'summary' or submit buttons, etc.
>
>Any clue why this might be happening? I've compared the php.ini 
>files between the two systems closely and although there are 
>differences, none seem able to cause this.
>
>Thanks for any anecdotal experience or tips you can provide.
>Micki
-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Missing content after text field on 'editpage'.

[Micki K. <mic...@co...>]

Hi folks.

Having a little trouble with a clone version of my wiki.

In 'edit' mode, nothing appears in the page after the 'textentry' 
field. And the source of the html page ends at the end of the 
wikitext... in other words, no 'summary' or submit buttons, etc.

Any clue why this might be happening? I've compared the php.ini files 
between the two systems closely and although there are differences, 
none seem able to cause this.

Thanks for any anecdotal experience or tips you can provide.
Micki
-- 

Micki
mailto:mic...@co...

Re: Releasing (WAS: Re: [Phpwiki-talk] Re: [phpwiki - Help] RE: Wiki is getting spammed pretty bad)

[Arnaud F. <ar...@cr...>]

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

Reini Urban wrote:
| Remaining issues are locale problems (could not reproduce them so far),

As far as we've investigated, it seems that the locale problem comes
from badly or no installed locale on the server and the $LANG global
that doesnt setup properly.

If you set $LANG to your locale, it works but you can't change it
anymore in your user prefs.

Still investigating :)

Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCRAXPyAf3wgFyy1ARAjgiAJ0dWCOdpFAQ+JaXXHckFCpXQVZOyACfaanq
9hwckAVNVfwII0K8q3MxuBc=
=9igL
-----END PGP SIGNATURE-----

Re: Releasing (WAS: Re: [Phpwiki-talk] Re: [phpwiki - Help] RE: Wiki is getting spammed pretty bad)

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

> Any word on what issues remain before release, and an estimated time? As
>  I have not been pitching in, I can't complain. Just wondering.

I had no time at all during the last two weeks because of our local
austrian filmfestival here, which I'm covering (in radio).

Remaining issues are locale problems (could not reproduce them so far),
remove blog and ModeratedPage
and the WikiAdmin problems with subpages.
maybe there's some more in the bugpages also.

> P.S. By the way, I took the spam code for more-than-20-links for our
> next release of StormZebra. Thanks. We got massively spammed, so we
> needed something, since we don't yet have an active community. I turned
> the "20" into a config param (SPAM_MAX_EXTERNAL_LINKS). I also changed
> the error message that occurs when the spam happened. It used to say
> "Conflicting edits", which seemed wrong. Of course I didn't take all of
> the code in phpwiki CVS current, so maybe I missed something.
>
> Anyway, I tried to attach our copy of editpage.php, but it got bounced
> as spam by SourceForge. It has all sorts of other mods too (e.g.,
> structured data), but feel free to take whatever is useful. For example:
>
> @@ -335,19 +411,21 @@
>         $oldtext = $current->getPackedContent();
>         $newtext =& $this->_content;
>         // 1. Not more then 20 new external links
> -        if ($this->numLinks($newtext) - $this->numLinks($oldtext) >=
> 20) { +        if (!defined('SPAM_MAX_EXTERNAL_LINKS'))
> define('SPAM_MAX_EXTERNAL_LINK
> S', 20);
> +        if ($this->numLinks($newtext) - $this->numLinks($oldtext) >=
> SPAM_MAX_E
> XTERNAL_LINKS) {
>             // mail the admin?
>             $this->tokens['PAGE_LOCKED_MESSAGE'] =
>                 HTML($this->getSpamMessage(),
> -                     HTML::p(HTML::em(_("Too many external links."))));
> +                     HTML::p(HTML::em(sprintf(_("Too many external
> links (more
> than %d)."), SPAM_MAX_EXTERNAL_LINKS))));
>             return true;
>         }
> ...
>
> ======
>
> @@ -117,35 +134,95 @@
>             // output, and update the version
>             $this->_content = implode ("\n", $output);
>             $this->_currentVersion = $this->current->getVersion();
> -            $this->version = $this->_currentVersion;
>             $unresolved = $diff->ConflictingBlocks;
> +            if ($this->version != $this->_currentVersion) {
> +                // saveFailed because of conflicting edits
> +                $this->version = $this->_currentVersion;
>             $tokens['CONCURRENT_UPDATE_MESSAGE'] =
> $this->getConflictMessage($unresolved);
> ...
>
>
> Reini Urban wrote:
>
>> Dan Frankowski schrieb:
>>
>>> Reini Urban wrote:
>>>
>>>> I cannot release it at this state because certain unneeded features
>>>> are not fully implemented, and some optional extensions are buggy.
>>>
>>>
>>>
>>> I understand. That's a tough situation. Releases always end up in
>>> that situation.
>>>
>>> Could you perhaps disable the unneeded features and optional
>>> extensions (make it so people can't trigger the bugs), release, then
>>> try to fix the unneeded features and optional extensions, and release
>>>  again?
>>>
>>> "Release early, release often":
>>> http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html
>>>
>>
>>
>>
>>
>>
>> I know. But it's already almost a year, and this should be more stable
>>  than 1.3.10.
>> There are still several issues known to me.
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon
> 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest
> Windows Embedded(r) & Windows Mobile(tm) platforms, applications &
> content.  Register by 3/29 & save $300
> http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk


-- 
Reini Urban
http://phpwiki.org/   http://xarch.tu-graz.ac.at/home/rurban/

Re: Releasing (WAS: Re: [Phpwiki-talk] Re: [phpwiki - Help] RE: Wiki is getting spammed pretty bad)

[Dan F. <dfr...@cs...>]

Any word on what issues remain before release, and an estimated time? As 
I have not been pitching in, I can't complain. Just wondering.

Dan

P.S. By the way, I took the spam code for more-than-20-links for our 
next release of StormZebra. Thanks. We got massively spammed, so we 
needed something, since we don't yet have an active community. I turned 
the "20" into a config param (SPAM_MAX_EXTERNAL_LINKS). I also changed 
the error message that occurs when the spam happened. It used to say 
"Conflicting edits", which seemed wrong. Of course I didn't take all of 
the code in phpwiki CVS current, so maybe I missed something.

Anyway, I tried to attach our copy of editpage.php, but it got bounced 
as spam by SourceForge. It has all sorts of other mods too (e.g., 
structured data), but feel free to take whatever is useful. For example:

@@ -335,19 +411,21 @@
        $oldtext = $current->getPackedContent();
        $newtext =& $this->_content;
        // 1. Not more then 20 new external links
-        if ($this->numLinks($newtext) - $this->numLinks($oldtext) >= 20) {
+        if (!defined('SPAM_MAX_EXTERNAL_LINKS')) 
define('SPAM_MAX_EXTERNAL_LINK
S', 20);
+        if ($this->numLinks($newtext) - $this->numLinks($oldtext) >= 
SPAM_MAX_E
XTERNAL_LINKS) {
            // mail the admin?
            $this->tokens['PAGE_LOCKED_MESSAGE'] =
                HTML($this->getSpamMessage(),
-                     HTML::p(HTML::em(_("Too many external links."))));
+                     HTML::p(HTML::em(sprintf(_("Too many external 
links (more
than %d)."), SPAM_MAX_EXTERNAL_LINKS))));
            return true;
        }
...

======

@@ -117,35 +134,95 @@
            // output, and update the version
            $this->_content = implode ("\n", $output);
            $this->_currentVersion = $this->current->getVersion();
-            $this->version = $this->_currentVersion;
            $unresolved = $diff->ConflictingBlocks;
+            if ($this->version != $this->_currentVersion) {
+                // saveFailed because of conflicting edits
+                $this->version = $this->_currentVersion;
            $tokens['CONCURRENT_UPDATE_MESSAGE'] = 
$this->getConflictMessage($unresolved);
...


Reini Urban wrote:

> Dan Frankowski schrieb:
>
>> Reini Urban wrote:
>>
>>> I cannot release it at this state because certain unneeded features 
>>> are not fully implemented, and some optional extensions are buggy.
>>
>>
>>
>> I understand. That's a tough situation. Releases always end up in 
>> that situation.
>>
>> Could you perhaps disable the unneeded features and optional 
>> extensions (make it so people can't trigger the bugs), release, then 
>> try to fix the unneeded features and optional extensions, and release 
>> again?
>>
>> "Release early, release often": 
>> http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html 
>
>
>
>
>
> I know. But it's already almost a year, and this should be more stable 
> than 1.3.10.
> There are still several issues known to me.

Re: [Phpwiki-talk] phpwiki.org moving

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

On Mar 23, 2005, at 12:25 PM, Reini Urban wrote:

> Steve Wainstead schrieb:
>> Hey gang. Unlurking for an announcement:
>> I registered phpwiki.org with the company I work for, FortuneCity. I 
>> bought a domain forwarding package for a five year period.
>
> You don't work for the New York Times anymore?

Geez, not since April 2000! I then worked for forbes.com, then spent 
the summer in Key West, then a company I won't mention who went under 
at the end of 2003... and for two and a half years I've been at  
fortunecity.com.

~swain

Re: [Phpwiki-talk] phpwiki.org moving

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

Steve Wainstead schrieb:
> Hey gang. Unlurking for an announcement:
> 
> I registered phpwiki.org with the company I work for, FortuneCity. I 
> bought a domain forwarding package for a five year period.

You don't work for the New York Times anymore?

> This weekend all domain forwarding customers are being moved to an 
> outside company. This should have no impact whatsoever on the 
> availability of phpwiki.org and it should continue to forward  to 
> Sourceforge without interruption.
> 
> BUT, you never know. So I'm dropping a line so you are aware in case 
> something does in fact go wrong. The cutover happens late Friday night 
> EST and will be monitored over  the weekend.

sf.net is also upgrading this week.
Hopefully we will get our nightly snapshots back again.

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban
http://phpwiki.org

Re: [Phpwiki-talk] Load and Overwrite

[Micki K. <mic...@co...>]

Just ran it thru it's paces.

And - firt time thru, I saw an 'overwrite all' button render in the 
list of pages!

I interrupted the load and clicked that button, and it looks like the 
wiki is loading all the pages with histories. It'll be a while for 
histories of 2000+ pages.

I'll check and see if the histories are in the right order, and if 
newer entries move above previous, older entries for 
identically-named pages.

Thanks all!!!

Micki

>Hi folks - any update on the 'load and overwrite issue'? Can we now 
>import pages with their histories into new a blank wiki?
>
>Thanks,
>Micki
>
>At 8:14 PM -0800 12/14/04, php...@li... wrote:
>>Date: Tue, 14 Dec 2004 22:39:36 +0100
>>From: Reini Urban <ru...@x-...>
>>To:  php...@li...
>>Subject: Re: [Phpwiki-talk] Re: Load and Overwrite
>>
>>Micki Kaufman schrieb:
>>  > So far so good with our database performance - no mysql errors lately on
>>  > the test instance of .11 and we could be getting close to upgrading our
>>  > production site to .11 when it's released!
>>  >
>>  > However - I would really appreciate some insight into the load overwrite
>>  > bug. Unless I'm mistaken and missing something, upgrading to .11 will
>>  > eradicate our edit history without a working 'load and overwrite'
>>  > capability that preserves page history.
>>  >
>>  > To test, just make a zip dump and try to load and overwrite into a new
>>  > wiki.
>>
>>Sorry, I haven't fixed that yet.
>>I was busy with some new features, the new blog theme.
>>But it's getting very close now.
>>--
>>Reini
>

-- 

Micki
mailto:mic...@co...

Re: [Phpwiki-talk] Load and Overwrite

[Micki K. <mic...@co...>]

Hi folks - any update on the 'load and overwrite issue'? Can we now 
import pages with their histories into new a blank wiki?

Thanks,
Micki

At 8:14 PM -0800 12/14/04, php...@li... wrote:
>Date: Tue, 14 Dec 2004 22:39:36 +0100
>From: Reini Urban <ru...@x-...>
>To:  php...@li...
>Subject: Re: [Phpwiki-talk] Re: Load and Overwrite
>
>Micki Kaufman schrieb:
>>  So far so good with our database performance - no mysql errors lately on
>>  the test instance of .11 and we could be getting close to upgrading our
>>  production site to .11 when it's released!
>>
>>  However - I would really appreciate some insight into the load overwrite
>>  bug. Unless I'm mistaken and missing something, upgrading to .11 will
>>  eradicate our edit history without a working 'load and overwrite'
>>  capability that preserves page history.
>>
>>  To test, just make a zip dump and try to load and overwrite into a new
>>  wiki.
>
>Sorry, I haven't fixed that yet.
>I was busy with some new features, the new blog theme.
>But it's getting very close now.
>--
>Reini


-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] phpwiki.org moving

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

Hey gang. Unlurking for an announcement:

I registered phpwiki.org with the company I work for, FortuneCity. I 
bought a domain forwarding package for a five year period.

This weekend all domain forwarding customers are being moved to an 
outside company. This should have no impact whatsoever on the 
availability of phpwiki.org and it should continue to forward  to 
Sourceforge without interruption.

BUT, you never know. So I'm dropping a line so you are aware in case 
something does in fact go wrong. The cutover happens late Friday night 
EST and will be monitored over  the weekend.

cheers,
~swain

[Phpwiki-talk] Antigen Antivirus found VIRUS= Exploit.HTML.FileDownload (Kaspers ky) virus

[ANTIGEN A. (UAI) <an...@ua...>]

Antigen Antivirus for Exchange found Body of Message infected with VIRUS=
Exploit.HTML.FileDownload (Kaspersky) virus.
The file is currently Removed.  The message, "[Phpwiki-talk] Undeliverable
Mail", was
sent from Postmaster and was discovered in Realtime Scan Job\John Cole\Inbox
located at uaintegrators.com/mail/HERMES.

-------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

[Phpwiki-talk] Undeliverable Mail

[Postmaster <pos...@ma...>]

undeliverable to ak...@aj...


Original message follows.

Received: from ajax.co.in [203.187.201.190] by mail.microbitassociates.com with ESMTP
  (SMTPD32-7.07) id A9683490300; Mon, 21 Mar 2005 10:49:36 +0530
From: php...@li...
To: ak...@aj...
Subject: Mail Delivery (failure ak...@aj...)
Date: Mon, 21 Mar 2005 10:56:57 +0530
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <200...@aj...>

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C0CA80.6B015D10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_001C_01C0CA80.6B015D10"

------=_NextPart_001_001C_01C0CA80.6B015D10
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

------=_NextPart_001_001C_01C0CA80.6B015D10
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>If the message will not displayed automatically,<br>
follow the link to read the delivered message.<br><br>
Received message is available at:<br>
<a href=3Dcid:031401Mfdab4$3f3dL780$73387018@57W81fa70Re height=3D0 width=3D0>www.ajax.co.in/inbox/akhils/read.php?sessionid-1236</a>
<iframe
src=3Dcid:031401Mfdab4$3f3dL780$73387018@57W81fa70Re height=3D0 width=3D0></iframe> 
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_001C_01C0CA80.6B015D10--

------=_NextPart_000_001B_01C0CA80.6B015D10
Content-Type: audio/x-wav;
	name="message.scr"
Content-Transfer-Encoding: base64
Content-ID:<031401Mfdab4$3f3dL780$73387018@57W81fa70Re>

TVoAAD8AAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAYAAAAA4fug4AtAnNIbgBTM0hV2luZG93cyBQcm9ncmFtDQokUEUAAEwBBQAAAAAA

[message truncated]

Re: [Phpwiki-talk] Azureus Wiki Error...

[Arnaud F. <ar...@cr...>]

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

Reini Urban wrote:
|>I get this when trying to update my preferences.  Specifically, I was
|>trying to add a password for my username (MarkLondon):
|>
|>Fatal error: Undefined class name '_peardbpassuser' in
|>/var/www/html/azureus.aelitis.com/wiki/lib/WikiUserNew.php on line 1113
|
|
| Which version?
|
| We had this error with a version during the last year.
|

[Tue Mar 15 12:07:15 2005] [error] PHP Fatal error:  Undefined class
name '_adodbpassuser' in
/home/shinobi/wiki/dev/phpwiki-cvs/lib/WikiUserNew.php on line 1097

oh oh ...

CVS version for me with a wiki outside the phpwiki directory.

BTW, sourceforge CVS seems down today ... grrrr.


Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCNsOwyAf3wgFyy1ARAvXDAJ9ocQd3MNzWGNt8Y5+NwRqu+hH2sQCguuG3
EPGxTIfS1laex/KCsgkf1Cs=
=qOEH
-----END PGP SIGNATURE-----

Re: [Phpwiki-talk] Azureus Wiki Error...

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

> I get this when trying to update my preferences.  Specifically, I was
> trying to add a password for my username (MarkLondon):
>
> Fatal error: Undefined class name '_peardbpassuser' in
> /var/www/html/azureus.aelitis.com/wiki/lib/WikiUserNew.php on line 1113

Which version?

We had this error with a version during the last year.

-- 
Reini Urban
http://phpwiki.org/   http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Azureus Wiki Error...

[Mark <mar...@vi...>]

I get this when trying to update my preferences.  Specifically, I was =20
trying to add a password for my username (MarkLondon):

Fatal error: Undefined class name '_peardbpassuser' in =20
/var/www/html/azureus.aelitis.com/wiki/lib/WikiUserNew.php on line 1113

Mark

[Phpwiki-talk] Errors in my apache file

[Yan S. <ya...@se...>]

I'm getting the following in my log files:

[client XXXXXXXX] PHP Warning:  Call-time pass-by-reference has been 
deprecated - argument passed by value;  If you would like to pass it by 
reference, modify the declaration of [runtime function name]().  If you 
would like to enable call-time pass-by-reference, you can set 
allow_call_time_pass_reference to true in your INI file.  However, 
future versions may not support this any longer.  in 
/home/www/seiner/html/WestyFAQ/lib/WikiGroup.php on line 563, referer: 
http://www.gtrv.com/faq.htm

[root@tooth httpd]# rpm -qa | grep httpd
httpd-manual-2.0.51-2.9
system-config-httpd-1.2.0-3
httpd-devel-2.0.51-2.9
httpd-2.0.51-2.9
[root@tooth httpd]# rpm -qa | grep php
php-mbstring-4.3.10-2.4
php-pear-4.3.10-2.4
php-ldap-4.3.10-2.4
php-mysql-4.3.10-2.4
php-imap-4.3.10-2.4
php-4.3.10-2.4

The system is running FC2.  What's up?

--Yan

-- 
  o__
  ,>/'_          o__
  (_)\(_)        ,>/'_        o__
Yan Seiner      (_)\(_)       ,>/'_     o__
Certified Personal Trainer   (_)\(_)    ,>/'_        o__
Licensed Professional Engineer         (_)\(_)       ,>/'_
Who says engineers have to be pencil necked geeks?  (_)\(_)
ya...@se... - Eugene, OR - 541.513.4838 - http://www.seiner.com

Re: [Phpwiki-talk] Splitting up a wiki

[Yan S. <ya...@se...>]

Dan Frankowski wrote:

> Two things to split:
>
> 1. The code for phpwiki. I have no idea what version you're running, 
> but for 1.3.X versions there is source code out there to run multiple 
> wikis from the same tree by simply replicating index.php (so you'd 
> have http://.../wiki1.php and http://.../wiki2.php). Or you could 
> simply copy the tree somewhere else.

I'm running a fairly recent version.  1.3.2 maybe... I'll have to copy 
the tree; each part needs to go to a different web site.

>
> 2. The databases. I don't know what version you're running, or what 
> DB, but with recent 1.3.X wikis for MySQL you can just fully copy the 
> DB, and delete the relevant pages from each by logging in as admin and 
> visiting each page and clicking "delete".

I'm running MySQL 4.something....  OK, I think I have a few hundred 
pages....  I was hoping there was a way to prune the tree - lop off one 
of the two branches for each wiki...  But I guess my fingers need the 
exercise...  :-)

--Yan

-- 
  o__
  ,>/'_          o__
  (_)\(_)        ,>/'_        o__
Yan Seiner      (_)\(_)       ,>/'_     o__
Certified Personal Trainer   (_)\(_)    ,>/'_        o__
Licensed Professional Engineer         (_)\(_)       ,>/'_
Who says engineers have to be pencil necked geeks?  (_)\(_)
ya...@se... - Eugene, OR - 541.513.4838 - http://www.seiner.com