DokuWiki

So I would like to authenticate users using drupal accounts.    There is a plugin, authdrupal7 but I have not been able to get much from it, and turns out it uses old mysql access functions now removed as of PHP7, and there has been a ticket on that ... [More] for quite some time. I set up to use authpdo and it's not hard to get that to "work" but there is hash function in the crypthash set to match Drupal's.  Drupal keeps the type of hash in the first 4 chars of the encrypted password, the salt in the next 8 characters, and the result of some number of SHA512 hashes (I think it's 15 of them?) with the number I think derived from the hash type. Anyway, not something you can do in SQL easily.   The best way might be to write a drupal hash function to add to the set of crypthashes.  But I don't see them when I grep for them -- where are they? Failing all this, what are some good alternate ways to have a system where users can register for an account, confirm their email address with a link mailed them, and then log on and update their account, change password if they want etc. I was going to let drupal do all that and it made sense to just rely on that system since my site has both drupal 7 and the wiki. [Less]

So I would like to authenticate users using drupal accounts.    There is a plugin, authdrupal7 but I have not been able to get much from it, and turns out it uses old mysql access functions now removed as of PHP7, and there has been a ticket on that ... [More] for quite some time. I set up to use authpdo and it's not hard to get that to "work" but there is hash function in the crypthash set to match Drupal's.  Drupal keeps the type of hash in the first 4 chars of the encrypted password, the salt in the next 8 characters, and the result of some number of SHA512 hashes (I think it's 15 of them?) with the number I think derived from the hash type. Anyway, not something you can do in SQL easily.   The best way might be to write a drupal hash function to add to the set of crypthashes.  But I don't see them when I grep for them -- where are they? Failing all this, what are some good alternate ways to have a system where users can register for an account, confirm their email address with a link mailed them, and then log on and update their account, change password if they want etc. I was going to let drupal do all that and it made sense to just rely on that system since my site has both drupal 7 and the wiki. [Less]

After enabling the full htaccess (removing the ## commenting before certain code), the images were broken again, (and probably other related to _media, _detail, and _export), so I changed the regex to (_?.+), and now not broken.  I hope no more ... [More] surprises.  I hope no more teasing. So, again, in case you are reading this and not sure WTF is the purpose. In past I had a site that:   * had dokuwiki in a subfolder instead of root   * used underscores as a word separator for my own naming of pages and media   * used ugly URLs I followed the steps to use Nice Url's, but incoming requests from old links still showed the ugly, so used htaccess regex above to "301" tell user's web browsers and search engines that there is only one page, and to stop asking for the old URLs. Google, the all powerful, say "underscore bad", unless you are Wikipedia.  So I renamed all my pages and media with hyphens, and used the plugin "orphans wanted" to clean up internal links.  For existing links coming from outside my website to no longer be dead, I used regex to reform the request and provide a 301.  The user's web browser then requests the Corrected Nice URL, and the dokuwiki-supplied-regex does it's thing for the internal request. Check my work: http://www.mekineer.com/dokuwiki/doku.…?id=information_t… should now resolve as: https://mekineer.com/information-technology/2019-search-en… [Less]

After enabling the full htaccess (removing the ## commenting before certain code), the images were broken again, (and probably other related to _media, _detail, and _export), so I changed the regex to (_?.+), and now not broken.  I hope no more ... [More] surprises.  I hope no more teasing. So, again, in case you are reading this and not sure WTF is the purpose. In past I had a site that:   * had dokuwiki in a subfolder instead of root   * used underscores as a word separator for my own naming of pages and media   * used ugly URLs I followed the steps to use Nice Url's, but incoming requests from old links still showed the ugly, so used htaccess regex above to "301" tell user's web browsers and search engines that there is only one page, and to stop asking for the old URLs. Google, the all powerful, say "underscore bad", unless you are Wikipedia.  So I renamed all my pages and media with hyphens, and used the plugin "orphans wanted" to clean up internal links.  For existing links coming from outside my website to no longer be dead, I used regex to reform the request and provide a 301.  The user's web browser then requests the Corrected Nice URL, and the dokuwiki-supplied-regex does it's thing for the internal request. Check my work: http://www.mekineer.com/dokuwiki/doku.…?id=information_t… should now resolve as: https://mekineer.com/information-technology/2019-search-en… [Less]

If I use hyphens as word separators in the images, then they don't appear in the pages.  Rename the images with underscores, and everything's ok. I have the dokuwiki setting to use hyphens as word separators enabled, and I have the ... [More] underscore-removal and doku.php-removal sections disabled in the htaccess above. Ok... had to flush the browser cache.  Maybe Ctrl-F5 isn't doing what it's supposed to.  Now maybe things will start to make some kind of sense. [Less]

If I use hyphens as word separators in the images, then they don't appear in the pages.  Rename the images with underscores, and everything's ok. I have the dokuwiki setting to use hyphens as word separators enabled, and I have the ... [More] underscore-removal and doku.php-removal sections disabled in the htaccess above. Ok... had to flush the browser cache.  Maybe Ctrl-F5 isn't doing what it's supposed to.  Now maybe things will start to make some kind of sense. [Less]

Hallo Biitsch, grundsätzlich sollte Dein Vorhaben mit Ubuntu + Apache funktionieren. Ich habe genau die selbe Konstellation in Benutzung (zwar mit 18.04 statt 16.04 - aber das sollte keine Rolle spielen). Hast Du auf dem Server statt ... [More] http://127.0.0.1/doku.php mal http://192.168.178.20/doku.php versucht - auch wenn es eine Anfrage an den eigenen Rechner ist, sollte das trotzdem funktionieren. Dann weißt Du schonmal, ob das grundsätzlich funktioniert. Es gibt beim Apache-Server auch noch eine Einstellung, dass er nur auf Anfragen von localhost bzw. 127.0.0.1 lauscht - evtl. liegt im DokuWiki-Verzeichnis eine .htaccess drin die dieses Kommando beinhaltet (auch wenn ich das für eher unwahrscheinlich halte...). Statt Listen 80 würde dort dann Listen localhost:80 stehen. Viele Grüße, Christoph [Less]

Hallo Biitsch, grundsätzlich sollte Dein Vorhaben mit Ubuntu + Apache funktionieren. Ich habe genau die selbe Konstellation in Benutzung (zwar mit 18.04 statt 16.04 - aber das sollte keine Rolle spielen). Hast Du auf dem Server statt ... [More] http://127.0.0.1/doku.php mal http://192.168.178.20/doku.php versucht - auch wenn es eine Anfrage an den eigenen Rechner ist, sollte das trotzdem funktionieren. Dann weißt Du schonmal, ob das grundsätzlich funktioniert. Es gibt beim Apache-Server auch noch eine Einstellung, dass er nur auf Anfragen von localhost bzw. 127.0.0.1 lauscht - evtl. liegt im DokuWiki-Verzeichnis eine .htaccess drin die dieses Kommando beinhaltet (auch wenn ich das für eher unwahrscheinlich halte...). Statt Listen 80 würde dort dann Listen localhost:80 stehen. Viele Grüße, Christoph [Less]

Du solltest für Apache einen extra VirtualHost konfigurieren. Darin gibst du u.a. einen (beliebigen) Servernamen und das Basisverzeichnis von Dokuwiki an. Dann muss nur noch dafür sorgen das der Servername auf deine IP-Adresse aufgelöst wird. Der Aufruf des Wikis erfolgt dann über den Servernamen. Grüße Matthias

Du solltest für Apache einen extra VirtualHost konfigurieren. Darin gibst du u.a. einen (beliebigen) Servernamen und das Basisverzeichnis von Dokuwiki an. Dann muss nur noch dafür sorgen das der Servername auf deine IP-Adresse aufgelöst wird. Der Aufruf des Wikis erfolgt dann über den Servernamen. Grüße Matthias