Not logged in. · Lost password · Register

All posts by dokojo (6)

topic: Loads of errors with Greebo (and new server)  in the forum: General Help and Support Server Setup
Avatar
dokojo #1
Member since Apr 2018 · 6 posts
Group memberships: Members
Show profile · Link to this post
Quote by andi on 2018-05-09, 17:45:
You got answers on your initial question already. I simply wanted to point out that using our router is the preferred way when using the built-in webserver.

I see. Thanks for the hint.
topic: Loads of errors with Greebo (and new server)  in the forum: General Help and Support Server Setup
Avatar
dokojo #2
Member since Apr 2018 · 6 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 60716
Quote by andi on 2018-05-02, 23:48:
Please use index.php as a router.
php -S localhost:8000 index.php

I tried it, didn't change behaviour as far as I could observe.

What was that supposed to achieve?
topic: After upgrade to Greebo, failed to open stream  in the forum: General Help and Support Installation and Configuration
Avatar
dokojo #3
Member since Apr 2018 · 6 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 60569
inc/plugin.php [sic] is on a line in data/deleted.files of Greebo. I might be wrong, but to me it seems, this line is wrong, and fixing the Updater plugin(s) seems to me to address the issue at the wrong location?
topic: Loads of errors with Greebo (and new server)  in the forum: General Help and Support Server Setup
Avatar
dokojo #4
Member since Apr 2018 · 6 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 60485
Just read thread 15778. They seem to think there is a problem with the upgrade plugin, but I do believe, inc/plugin.php [sic] was falsely included in data/deleted.files. Since I also have a cleanup run after installation, inc/Plugin.php got deleted. The line was still in there when I downloaded stable today. Commented it and tried again, now it seems to work.

However, the builtin server in the php executable is putting all errors and warnings into the generated pages... and the code generates a lot of them... sigh. Different issue, though.

@turnermm: That'd be a quick fix for the issue, yes. Thanks.
topic: installing dokuwiki beneath a page on a server  in the forum: General Help and Support Server Setup
Avatar
dokojo #5
Member since Apr 2018 · 6 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 60384
Subject: a try
Dokuwiki uses relative pathnames wherever I looked, so it should be fine. But I don't know nginx at all, so I might be very wrong... but I'd assume you'd have to change the
root /dokuwiki
to
root /
, throw out the @dokuwiki out of try_files, change
location @dokuwiki {
to
location /dokuwiki {
and adapt the rewrite rules like so:
        rewrite ^/_media/(.*) /lib/exe/fetch.php?media=$1 last;
        rewrite ^/_detail/(.*) /lib/exe/detail.php?media=$1 last;
        rewrite ^/_export/([^/]+)/(.*) /doku.php?do=export_$1&id=$2 last;
        rewrite ^/(.*) /doku.php?id=$1&$args last;
becomes
        rewrite ^(/dokuwiki)/_media/(.*) $1/lib/exe/fetch.php?media=$2 last;
        rewrite ^(/dokuwiki)/_detail/(.*) $1/lib/exe/detail.php?media=$2 last;
        rewrite ^(/dokuwiki)/_export/([^/]+)/(.*) $1/doku.php?do=export_$2&id=$3 last;
        rewrite ^(/dokuwiki)/(.*) $1/doku.php?id=$2&$args last;
Probably
        try_files $uri $uri/ /doku.php;
could be changed to
        try_files $uri $uri/ /dokuwiki/doku.php;
in the ~ \.php location, also. Or better throw out /doku.php there, it shouldn't be needed if there are no nonexistant .php.
Then you could use the rest of the server like usual, and address the dokuwiki with http://www.example.com/dokuwiki/. Given my background, that's a bit of a wild guess, though...

(I hate it when ppl give me answers like "why do you want to do that" or "use a different webserver", but I believe it's fair after answering the original question, so: I used dokuwiki with lighttpd on a RasPi, and that works like this out of the box afair. Might be an option.)
topic: Loads of errors with Greebo (and new server)  in the forum: General Help and Support Server Setup
Avatar
dokojo #6
Member since Apr 2018 · 6 posts
Group memberships: Members
Show profile · Link to this post
Subject: Loads of errors with Greebo (and new server)
Hi there,

I used to use a small Dokuwiki on a Windows localhost with QuickPHP (http://www.zachsaw.com/?pg=quickphp_php_tester_debugger). That worked nicely until Greebo came along with PHP >= 5.4 syntax and features. QuickPHP is a bit old meanwhile, so I thought, why not upgrade. So I tried the Dokuwiki with PHP 7.2 (nts) and the builtin server, like so:
php -S localhost:8000 -t <wikiroot>
Now when I open localhost:8000, I get loads of errors:
Warning: require(wikiroot/inc/Plugin.php): failed to open stream: No such file or directory in wikiroot\inc\load.php on line 112

Fatal error: require(): Failed opening required 'wikiroot/inc/Plugin.php' (include_path='.;C:\php\pear') in wikiroot\inc\load.php on line 112
This is the line 112 in load.php:
'DokuWiki_Plugin'          => DOKU_INC.'inc/Plugin.php',
, which then gets required a bit down.

And it's true, there is no Plugin.php in inc. There are two others, \bin\plugin.php and inc\Action\Plugin.php. So I insert these into load.php, the first one throwing loads of warnings about the usage of STDOUT and others; the second one looks a bit better, only one error message:
Fatal error: Class 'DokuWiki_Plugin' not found in X:\down\Dropbox\jokno\dexwiki_jo\lib\plugins\action.php on line 15
Here I gave up. In all cases, the pages don't get served; I only get error messages.

I'm a bit stumped here. How broken is dokuwiki? Or PHP? Or is it just some option I have to set?
Close Smaller – Larger + Reply to this post:
Special characters:
Special queries
Go to forum
Imprint
This board is powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2015 by Yves Goergen
Current time: 2019-11-20, 01:17:22 (UTC +01:00)