phpwiki-talk

Re: [Phpwiki-talk] Call to protected method?

[Harold H. <ha...@ha...>]

Still trying to chase this issue down. Currently I can't edit pages. Ideas?

Thanks!

Harold


>
> PHP Fatal error:  Call to protected method WikiDB_backend::text_search()
> from context 'WikiDB' in
> /home/louise/public_html/phpwiki-code-9454-trunk/lib/WikiDB.php on line
> 337
>
> I started getting the above error on an otherwise working system recently
> when the edit tab is selected. I also just tried a fresh install of the
> most recent snapshot. The db type is file.
>
> Ideas?
>
> THANKS!
>
> Harold
>
>
>
>
>
> --
> FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
> opportunities available!
> Not sent from an iPhone.
>
>
>
> --
> FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
> opportunities available!
> Not sent from an iPhone.
>


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

Re: [Phpwiki-talk] Call to protected method?

[Marc-Etienne V. <Mar...@al...>]

On 31/12/2014 05:24, Harold Hallikainen wrote:
>
> PHP Fatal error:  Call to protected method WikiDB_backend::text_search()
> from context 'WikiDB' in
> /home/louise/public_html/phpwiki-code-9454-trunk/lib/WikiDB.php on line 337
>
> I started getting the above error on an otherwise working system recently
> when the edit tab is selected. I also just tried a fresh install of the
> most recent snapshot. The db type is file.
>
> Ideas?

Hello Harold,

Thank you for the bug report.

Unfortunately I rarely test with db type as file.

The text_search method must be public, it was protected in the
abstract class and not overwritten in the subclass for file.

It is fixed in r9456.

Best wishes for the new year!

Marc-Etienne

-- 
Marc-Etienne Vargenau Mar...@al...
Alcatel-Lucent International, Route de Villejust, 91620 NOZAY, FRANCE
+33 1 60 40 28 33 OnNet 2103 2833

[Phpwiki-talk] Call to protected method?

[Harold H. <ha...@ha...>]

PHP Fatal error:  Call to protected method WikiDB_backend::text_search()
from context 'WikiDB' in
/home/louise/public_html/phpwiki-code-9454-trunk/lib/WikiDB.php on line 337

I started getting the above error on an otherwise working system recently
when the edit tab is selected. I also just tried a fresh install of the
most recent snapshot. The db type is file.

Ideas?

THANKS!

Harold





-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

Re: [Phpwiki-talk] phpwiki-1.5.2: Fatal PHP error.

[jdebert <jd...@ga...>]

On Mon, 24 Nov 2014 17:07:39 +0100
Marc-Etienne Vargenau <Mar...@al...> wrote:

> 
> I will look to your SQL problem later.

Reference: mysql 5.6 manual, section 11.5:

BLOB and TEXT data type cannot have a default value.

I do remember that defining default values for blob/text was allowed in
earlier versions.

jd

Re: [Phpwiki-talk] phpwiki-1.5.2: Fatal PHP error.

[Marc-Etienne V. <Mar...@al...>]

On 22/11/2014 23:14, jdebert wrote:
> In re last,
>
> On Fri, 21 Nov 2014 17:25:25 -0800
> jdebert <jd...@ga...> wrote:
>
>> PHP Fatal error:  Call to undefined function posix_times()
>> in $PHPWIKI/lib/prepend.php on line 72, referer:
>> http://localhost/
>>
>
> [snip]
>>
>>      function DebugTimer()
>>      {
>>          $this->_start = $this->microtime();
>>          $this->_times = posix_times();
>>      }
>>
>
> I inserted a line from 1.4.0:
>
>        function DebugTimer() {
>            $this->_start = $this->microtime();
>            if (function_exists('posix_times'))  <----- from 1.4.0
>                $this->_times = posix_times();
>        }
>
> which seems to work so far and even took care of the deprecated
> function warnings. I had installed the php5 posix module before this
> thinking it may resolve the error but it did not.

Hi,

You are right, function posix_times does not always exist,
for example on Windows.

I had removed some function_exists checks for functions
that are supposed to be present in PHP >= 5.3 but for
this one it was not correct.

I have added the check again.

I will look to your SQL problem later.

Thank you for your remarks.

Best regards,

Marc-Etienne Vargenau

-- 
Marc-Etienne Vargenau Mar...@al...
Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
+33 1 60 40 28 33 OnNet 2103 2833

Re: [Phpwiki-talk] phpwiki-1.5.2: Fatal PHP error.

[jdebert <jd...@ga...>]

In re last,

On Fri, 21 Nov 2014 17:25:25 -0800
jdebert <jd...@ga...> wrote:

> PHP Fatal error:  Call to undefined function posix_times()
> in $PHPWIKI/lib/prepend.php on line 72, referer:
> http://localhost/
> 

[snip]
> 
>     function DebugTimer()
>     {
>         $this->_start = $this->microtime();
>         $this->_times = posix_times();
>     }
> 

I inserted a line from 1.4.0:

      function DebugTimer() {
          $this->_start = $this->microtime();
          if (function_exists('posix_times'))  <----- from 1.4.0
              $this->_times = posix_times();
      }
  
which seems to work so far and even took care of the deprecated
function warnings. I had installed the php5 posix module before this
thinking it may resolve the error but it did not.

However, this error seems to have prevented loading the virgin wiki
pages and there were sql errors about the page table being empty when
phpwiki was accessed after this. I had to destroy and re-create the
database over again so that phpwiki would load the pages into the db.

But here again, I encountered a problem. The schemas as written did not
work. mysql did not like defaults for the blob/text datatypes:

    ERROR 1101 (42000) at line 72: BLOB/TEXT column 'prefs' 
     can't have a default value

Deleting "DEFAULT ''" from every line defining a blob/text type in
mysql-initialize.sql schema allowed the tables to be created without
problem. IIRC, since at least mysql 5.6 and at least mariadb 5.6,
DEFAULT is no longer legal for types blob/text.

So far, the wiki is readable. In lynx, at least. I'll try editing,
creating pages and transferring pages from the old phpwiki later and
see if that works as well.

jd

[Phpwiki-talk] phpwiki-1.5.2: Fatal PHP error.

[jdebert <jd...@ga...>]

Started setting up phpwiki-1.5.2 and encountered this error:

PHP Fatal error:  Call to undefined function posix_times()
in $PHPWIKI/lib/prepend.php on line 72, referer:
http://localhost/

The function isn't defined even in php5. It doesn't look like it can be
simply commented out, either:


    function DebugTimer()
    {
        $this->_start = $this->microtime();
        $this->_times = posix_times();
    }

Really appreciate any clue.

Thanks

jd

Re: [Phpwiki-talk] Fatal error phpwiki-1.2.10

[jdebert <jd...@ga...>]

On Fri, 21 Nov 2014 16:19:20 +0100
Reini Urban <ru...@x-...> wrote:

> You can try to comment out this function call. Should work without.
Thanks. That works.

I can start the wiki now but I cannot do a zipdump. There are no
errors reported. The only complaints are from php about deprecated
functions. mysql logs no errors.

Without zipdump, seems I'm left the choice of copy-paste pages to the
new wiki or alter the tables in place for the new format. A choice
between time-consuming & error-prone versus risk of data loss. Fun.

> Am 21.11.2014 09:59 schrieb "Marc-Etienne Vargenau" <
> Mar...@al...>:
> >
> > Your PHP is too recent.
> >
> > function import_request_variables has been removed in recent
> > PHPs. See:

Thanks.

As I suspected.

jd

Re: [Phpwiki-talk] Fatal error phpwiki-1.2.10

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

You can try to comment out this function call. Should work without.
Am 21.11.2014 09:59 schrieb "Marc-Etienne Vargenau" <
Mar...@al...>:

> On 21/11/2014 05:14, jdebert wrote:
> > I'm trying to do a zipdump in 1.2.10 so I can upgrade to 1.5.2 but I
> > keep encountering this error:
> >
> > Fatal error: Call to undefined function import_request_variables()
> > in /home/www/html/old-phpwiki/lib/config.php on line 10
> >
> > I see several php files reference the above function but I don't see
> > where it's defined.
> >
> > What am I missing?
> >
> > php5-5.6.3
> > apache2-2.2.22
> > mariadb 10.0.3
> > phpwiki-1.2.10
>
> Hello,
>
> Thank you for your interest in PhpWiki.
>
> Your PHP is too recent.
>
> function import_request_variables has been removed in recent
> PHPs. See:
>
> http://php.net/manual/en/function.import-request-variables.php
>
> Best regards,
>
> Marc-Etienne Vargenau
>
> --
> Marc-Etienne Vargenau Mar...@al...
> Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
> +33 1 60 40 28 33 OnNet 2103 2833
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

Re: [Phpwiki-talk] Fatal error phpwiki-1.2.10

[Marc-Etienne V. <Mar...@al...>]

On 21/11/2014 05:14, jdebert wrote:
> I'm trying to do a zipdump in 1.2.10 so I can upgrade to 1.5.2 but I
> keep encountering this error:
>
> Fatal error: Call to undefined function import_request_variables()
> in /home/www/html/old-phpwiki/lib/config.php on line 10
>
> I see several php files reference the above function but I don't see
> where it's defined.
>
> What am I missing?
>
> php5-5.6.3
> apache2-2.2.22
> mariadb 10.0.3
> phpwiki-1.2.10

Hello,

Thank you for your interest in PhpWiki.

Your PHP is too recent.

function import_request_variables has been removed in recent
PHPs. See:

http://php.net/manual/en/function.import-request-variables.php

Best regards,

Marc-Etienne Vargenau

-- 
Marc-Etienne Vargenau Mar...@al...
Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
+33 1 60 40 28 33 OnNet 2103 2833

[Phpwiki-talk] Fatal error phpwiki-1.2.10

[jdebert <jd...@ga...>]

I'm trying to do a zipdump in 1.2.10 so I can upgrade to 1.5.2 but I
keep encountering this error:

Fatal error: Call to undefined function import_request_variables()
in /home/www/html/old-phpwiki/lib/config.php on line 10

I see several php files reference the above function but I don't see
where it's defined.

What am I missing?

php5-5.6.3
apache2-2.2.22
mariadb 10.0.3
phpwiki-1.2.10

jd

Re: [Phpwiki-talk] suppressing php warnings?

[Harold H. <ha...@ha...>]

> Le 22/05/2014 14:35, Harold Hallikainen a écrit :
>>
>> I'm migrating to a new server and am installing phpwiki-code-8855-trunk.
>> I'm getting a lot of warnings about preg_replace.
>>
>> Warning: "preg_replace(): The /e modifier is deprecated, use
>> preg_replace_callback instead"
>>
>> In /etc/php.ini, I have this line:
>> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
>>
>> which seems it should suppress warnings about deprecated features. But,
>> the warnings keep showing up.
>
> Hello Harold,
>
> I just created a patch to replace preg_replace with
> preg_replace_callback.
>
> It is in Subversion revision 8856.
>
> Can you please see if it solves your problem?
>
> Best regards,
>
> Marc-Etienne Vargenau


THANKS! That seems to reduce the number of warnings, but I suspect this is
also used in other files (and I'm having trouble figuring out which ones
since php error logging does not seem to be working).

I'll see if I can find the other occurrences. If you can find them also,
that would be great!

Thanks!

Harold


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

Re: [Phpwiki-talk] suppressing php warnings?

[Marc-Etienne V. <Mar...@al...>]

Le 22/05/2014 14:35, Harold Hallikainen a écrit :
>
> I'm migrating to a new server and am installing phpwiki-code-8855-trunk.
> I'm getting a lot of warnings about preg_replace.
>
> Warning: "preg_replace(): The /e modifier is deprecated, use
> preg_replace_callback instead"
>
> In /etc/php.ini, I have this line:
> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
>
> which seems it should suppress warnings about deprecated features. But,
> the warnings keep showing up.

Hello Harold,

I just created a patch to replace preg_replace with
preg_replace_callback.

It is in Subversion revision 8856.

Can you please see if it solves your problem?

Best regards,

Marc-Etienne Vargenau

-- 
Marc-Etienne Vargenau Mar...@al...
Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
+33 1 60 40 28 33 OnNet 2103 2833

[Phpwiki-talk] suppressing php warnings?

[Harold H. <ha...@ha...>]

I'm migrating to a new server and am installing phpwiki-code-8855-trunk.
I'm getting a lot of warnings about preg_replace.

Warning: "preg_replace(): The /e modifier is deprecated, use
preg_replace_callback instead"

In /etc/php.ini, I have this line:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT

which seems it should suppress warnings about deprecated features. But,
the warnings keep showing up.

Any ideas on an easy fix for this?

THANKS!

Harold



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

[Phpwiki-talk] browser-based functional testing

[Peter K. <pet...@gm...>]

I see that you use HttpUnit tests in PhpWiki. However, if you'd like
automated browser-based functional/regression testing, you may be
interested in SeLite. It extends Selenium IDE. It allows your tests to
access (read and write to) a test DB (isolated from the DB of the tested
application). It's open source.

It could work very well for you, especially since PhpWiki can have its data
in an SQLite DB. SeLite uses a (separate) SQLite DB for test data, so your
test data lifecycle would be very easy. However, you can benefit from
SeLite even if your test instance of PhpWiki uses other type of DB.

Creating tests in Selenium IDE is convenient and highly productive. It
doesn't require low-level programming skills, so even users/theme designers
could contribute new tests. Tests can be maintained in SVN. See
https://code.google.com/p/selite/wiki/ProjectHome.

I could create a test framework and provide some examples. Would there be
any interest?

-Peter Kehl

Re: [Phpwiki-talk] [phpwiki:code] vargenau committed to PhpWiki Code: Move info from code to help page

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

Interesting, thanks.
I'm still pretty busy with work related things.

Feel free to publish 1.4.0 by yourself.


On Tue, Apr 2, 2013 at 10:18 AM, Marc-Etienne Vargenau <
Mar...@al...> wrote:

> Le 02/04/2013 16:19, Reini Urban a écrit :
>
>> Hey,
>> you removed pgsrc/Help%2FWikiBlogPlugin
>> <http://sourceforge.net/p/**phpwiki/code/8735/tree//trunk/**
>> pgsrc/Help%2FWikiBlogPlugin<http://sourceforge.net/p/phpwiki/code/8735/tree//trunk/pgsrc/Help%2FWikiBlogPlugin>
>> >
>>
>> instead of adding the docs from the code.
>>
>
> Hello Reini,
>
> I do not think so, I see the file pgsrc/Help%2FWikiBlogPlugin
> in my working copy and when doing a fresh "svn co".
>
> The new svn viewer in Sourceforge seems broken.
>
> Will you have time to publish a new release of Phpwiki?
>
> Best regards,
>
> Marc-Etienne
>
> --
> Marc-Etienne Vargenau Marc-Etienne.Vargenau@alcatel-**lucent.com<Mar...@al...>
> Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
> +33 1 30 77 28 33 OnNet 2103 2833
>



-- 
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

Re: [Phpwiki-talk] [phpwiki:code] vargenau committed to PhpWiki Code: Move info from code to help page

[Marc-Etienne V. <Mar...@al...>]

Le 02/04/2013 16:19, Reini Urban a écrit :
> Hey,
> you removed pgsrc/Help%2FWikiBlogPlugin
> <http://sourceforge.net/p/phpwiki/code/8735/tree//trunk/pgsrc/Help%2FWikiBlogPlugin>
> instead of adding the docs from the code.

Hello Reini,

I do not think so, I see the file pgsrc/Help%2FWikiBlogPlugin
in my working copy and when doing a fresh "svn co".

The new svn viewer in Sourceforge seems broken.

Will you have time to publish a new release of Phpwiki?

Best regards,

Marc-Etienne

-- 
Marc-Etienne Vargenau Mar...@al...
Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
+33 1 30 77 28 33 OnNet 2103 2833

Re: [Phpwiki-talk] [phpwiki:code] vargenau committed to PhpWiki Code: Move info from code to help page

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

Hey,
you removed pgsrc/Help%2FWikiBlogPlugin<http://sourceforge.net/p/phpwiki/code/8735/tree//trunk/pgsrc/Help%2FWikiBlogPlugin>
instead of adding the docs from the code.


On Tue, Apr 2, 2013 at 3:25 AM, Repository PhpWiki code <
no...@co...> wrote:

> : Move info from code to help page
> http://sourceforge.net/p/phpwiki/code/8736/
> ------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/phpwiki/code/
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
>



-- 
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

Re: [Phpwiki-talk] Getting latest code set?

[Harold H. <ha...@ha...>]

> Le 25/11/2012 20:21, Harold Hallikainen a écrit :
>> I figured out how to get the latest code at
>> http://phpwiki.svn.sourceforge.net/viewvc/phpwiki/trunk/ . It's working
>> pretty well! THANKS to all of you working on this.
>>
>> Harold
>>
>
> Hello Harold,
>
> Thank you for interest in Phpwiki.
> We hope to have Phpwiki 1.4.0 out soon.
>
> Best regards,
>
> Marc-Etienne


Thanks! I've been using phpwiki for MANY years. On my recent test of the
version linked to above, I enabled captcha, but the images did not show
up.

On another note, I've really been having a problem with spam. I finally
moved the wiki and put a simple login screen on the original page. If the
login is successful (username and password of nospam), the page redirects
to the new location and all is well. This seems to have stopped the
spammers, for now, but is not very elegant. Captcha should stop automated
spam, but manually entered spam could still get through. I like the
registration process in Gallery ( http://gallery.menalto.com/ ) where I
receive an email of a registration request, then approve it. I've stopped
a lot of spammers with that. Something like that (or any other spam
prevention techniques) would be great in phpwiki.

Again, THANKS for the work on this. I look forward to using phpwiki for
years to come.

Harold
http://www.hallikainen.org/BroadcastHistory/



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

Re: [Phpwiki-talk] Getting latest code set?

[Marc-Etienne V. <Mar...@al...>]

Le 25/11/2012 20:21, Harold Hallikainen a écrit :
> I figured out how to get the latest code at
> http://phpwiki.svn.sourceforge.net/viewvc/phpwiki/trunk/ . It's working
> pretty well! THANKS to all of you working on this.
>
> Harold
>

Hello Harold,

Thank you for interest in Phpwiki.
We hope to have Phpwiki 1.4.0 out soon.

Best regards,

Marc-Etienne

-- 
Marc-Etienne Vargenau Mar...@al...
Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
+33 1 30 77 28 33 OnNet 2103 2833

Re: [Phpwiki-talk] Getting latest code set?

[Harold H. <ha...@ha...>]

I figured out how to get the latest code at
http://phpwiki.svn.sourceforge.net/viewvc/phpwiki/trunk/ . It's working
pretty well! THANKS to all of you working on this.

Harold

-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

[Phpwiki-talk] Getting latest code set?

[Harold H. <ha...@ha...>]

I've been running phpWiki for many years (page history on the home page
goes back to 2005). I'm now migrating to a new server that I have Fedora
Core 17 on. On my old system, I'm running phpWiki version 1.3.13p1 June, 9
2007.

When I run version 1.4.0rc1, I get a bunch of warnings that I assume have
been fixed in builds since 2010. For example, I get the following:

Warning: "substr() expects parameter 3 to be long, string given"

Warning: "strftime(): It is not safe to rely on the system's timezone
settings. You are *required* to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those
methods and you are still getting this warning, you most likely misspelled
the timezone identifier. We selected the timezone 'UTC' for now, but
please set date.timezone to select your timezone."


Warning: "Illegal string offset 'linkto'"


That last warning appears LOTS of time.

So, finally, the question. I see that various revisions have been
committed to the repository, including some in the past day or two.
Unfortunately, I don't know much about svn. Can someone give me a simple
way of downloading the latest code set to try on this system?

THANKS!

Harold



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.

Re: [Phpwiki-talk] SourceForge Project Upgrade Notification

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

On Thu, Oct 11, 2012 at 10:24 AM, SourceForge.net
<nor...@in...> wrote:
> Your project, PhpWiki, has been upgraded.
>
> Your source code repositories are currently being migrated to the new setup. You will recieve another email when that import is complete. That means that you and any other developers should do a fresh checkout using the new repository location when it is ready (see the "code" tab). Please be aware that large repositories may take a long time.
>
> Please report any issues to us at https://sourceforge.net/p/forge/site-support/new/  Thanks!

Thanks
-- 
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

Re: [Phpwiki-talk] splitting wikiwords in page headings

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

Thanks for the advice!  Unfortunately I just want to split the page
title, not the wikiwords on the rest of the page. :(

On Mon, Mar 12, 2012, at 04:49 PM, Marc-Etienne Vargenau wrote:
> Le 11/03/2012 21:49, Philip J. Hollenback a écrit :
> > I'm using basically the stock phpwiki-1.4.0 sidebar theme on my website
> > www.hollenback.net.  I'd like the wikiword title to be expanded into
> > regular words.  So if you look at
> >
> > http://www.hollenback.net/FakingItAsAWindowsAdmin
> >
> > I'd like the largest title to read 'Faking It As A Windows Admin', not
> > 'FakingItAsAWindowsAdmin'.
> >
> > I think I can do this by calling SplitPageName from stdlib.php in the
> > appropriate place in my theme template.  I messed around with this a
> > bit, but I found it broke the backlinks functionality on the page name
> > and generated errors in my phpwiki.
> >
> > Can someone suggest the simplest way to do this?
> 
> Hello Philip,
> 
> In file themes/<YourTheme>/themeinfo.php
> do a:
> $this->setAutosplitWikiWords(true);
> 
> This will do what you want in the title, but also in the whole
> wiki page.
> 
> Best regards,
> 
> Marc-Etienne
> 
> -- 
> Marc-Etienne Vargenau
> Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
> +33 (0)1 30 77 28 33, Mar...@al...
> 
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 
--  
Philip J. Hollenback
www.hollenback.net
@philiph

Re: [Phpwiki-talk] splitting wikiwords in page headings

[Marc-Etienne V. <Mar...@al...>]

Le 11/03/2012 21:49, Philip J. Hollenback a écrit :
> I'm using basically the stock phpwiki-1.4.0 sidebar theme on my website
> www.hollenback.net.  I'd like the wikiword title to be expanded into
> regular words.  So if you look at
>
> http://www.hollenback.net/FakingItAsAWindowsAdmin
>
> I'd like the largest title to read 'Faking It As A Windows Admin', not
> 'FakingItAsAWindowsAdmin'.
>
> I think I can do this by calling SplitPageName from stdlib.php in the
> appropriate place in my theme template.  I messed around with this a
> bit, but I found it broke the backlinks functionality on the page name
> and generated errors in my phpwiki.
>
> Can someone suggest the simplest way to do this?

Hello Philip,

In file themes/<YourTheme>/themeinfo.php
do a:
$this->setAutosplitWikiWords(true);

This will do what you want in the title, but also in the whole
wiki page.

Best regards,

Marc-Etienne

-- 
Marc-Etienne Vargenau
Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE
+33 (0)1 30 77 28 33, Mar...@al...