Not logged in. · Lost password · Register
Page:  1  2  3 ... 32  33  34  next 

All posts by schplurtz (502)

topic: Problem with automatic emails  in the forum: General Help and Support Server Setup
Avatar
schplurtz (Moderator) #1
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
Quote by Zapo99:
Sent: MAIL FROM:<>
Got: 550 5.1.8 Sender address rejected

Indeed <> is a reserved email address. It should be instead your email address.
Did you set the mailfrom address in DW config as stated on https://www.dokuwiki.org/plugin:smtp ?
topic: Probleme tableau vide  in the forum: Non-English Discussion French discussion
Avatar
schplurtz (Moderator) #2
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 68081
bonjour,

C'est un bug du greffon wrap qui ne vérifie pas suffisamment la valeur des options de configuration avant de les utiliser. Il faudrait le rapporter sur https://github.com/selfthinker/dokuwiki_plugin_wrap/issues .

En jetant un coup d'œil rapide au code du greffon, je pense que soit la valeur de l'option de configuration noPrefix est vide soit elle est malformée.

administration => paramètre de configuration => Wrap => «Quelles classes (séparées par une virgule) ne devraient pas être préfixées d'un "wrap_" ?»
la valeur par défaut est :
tabs, group

Si la valeur est vide, et que tu l'avais volontairement vidée, essaie de mettre un truc improbable à la place comme "ne_pas_supprimer_cette_valeur" ou "schproutz". Rétablis la valeur par défaut si c'était non volontaire.
topic: Probleme tableau vide  in the forum: Non-English Discussion French discussion
Avatar
schplurtz (Moderator) #3
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 68065
Content que ça fonctionne.

Je ne comprends pas pourquoi cette manip fait marcher le truc mais ca fonctionne.
Quand on enregistre une page, DokuWiki vérifie si la nouvelle page est différente. Si la
page n'a pas varié, DW se dit qu'il n'a rien à faire, à juste titre. En ajoutant un espace,
on s'assure que la page est différente, et en même temps on est certain de ne pas modifier
l'aspect du document, ni son sens. Par contre, comme la page est techniquement différente,
DW relance toute sa machinerie d'analyse, d'enregistrement, de greffons, d'indexation et
sans doute de tout un bazar d'autres bidules et machins. Dans le lot, le greffon data est
sollicité, vérifie et met à jout sa base de données.

C'est en quelque sorte une roublardise qui piège les ordinateurs (fichiers différents =>
au boulot !) sans rien changer pour les humains ni demander d'effort d'imagination.
topic: Probleme tableau vide  in the forum: Non-English Discussion French discussion
Avatar
schplurtz (Moderator) #4
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 68059
Bonsoir,

On y voit plus clair maintenant. Ce ne sont pas des tableaux de base DokuWiki, mais des éléments gérés par le greffon «Structured Data Plugin». Les données de ces tables, sont enregistrées dans une base de données sqlite, et pas seulement dans les pages du wiki. Je n'ai aucune idée de l'endroit où se trouve la BDD sqlite.

En premier lieu, il faut que les greffons sqlite et structured data soient installés. Au besoin, les installer, bien sûr.

Si après l'installation de ces deux greffons, les tables restent vides, c'est que la base sqlite est vide/tu n'as pas transféré la base de données sqlite. C'est pas grave du tout, il suffira de reconstruire cette base. Pour cela, on peut commencer par installer le greffon searchindex. Puis administration => Gestionnaire d'index de recherche => Reconstruire l'index. Je pense que ça ne suffira pas, mais ça ne peut pas faire de mal, à défaut de faire du bien...

Si ça ne suffit pas :
  • purger le cache, administration => paramètres de configuration . Enregistrer les paramètres sans rien changer.
  • après avoir purgé le cache, visiter toutes les pages du wiki qui contiennent un dataentry.
  • Les contenus des datatables devraient s'afficher correctement.

Si ça ne suffit toujours pas
  • editer chaque page du wiki qui contient un dataentry (ajouter un espace en bas de chaque page par exemple)
  • Les contenus des datatables devraient s'afficher correctement.
topic: Probleme tableau vide  in the forum: Non-English Discussion French discussion
Avatar
schplurtz (Moderator) #5
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 68054
Bonjour,

Peut-on voir le code wiki du tableau et de son contenu ? cache les infos sensibles bien sûr...
topic: Updating a hopelessly outdated installation (Angua)  in the forum: General Help and Support Installation and Configuration
Avatar
schplurtz (Moderator) #6
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 68035
Debian 7 wheezy came with php 5.4. You need at least 5.6 for Greebo, the current DokuWiki version. So, before you can upgrade DokuWiki, you'll have to upgrade php. In order to upgrade PHP you'll have to upgrade your debian system, and there is little point in upgrading only to debian 8 which is itself outdated. So you'll have to go the long way to Debian 10. It could be quicker to install a brand new linux based on current turnkey.

There is this backup doc https://www.dokuwiki.org/faq:backup ...

Now, current turnkey has latest DokuWiki in /var/www/dokuwiki, data and DW engine. Assuming that your 2012 turnkey also has everything in /var/www/dokuwiki, here is what you could do :

  • install a new, current turnkey. and (eventually) upgrade the system to debian 10
  • transfer all the data from the old system to the new one. something like this should do it (run as root on the new turnkey):
   rsync -a --delete -v root@oldturnkey.your.domain:/var/www/dokuwiki/data/. /var/www/dokuwiki/data/.
  • transfer /var/www/dokuwiki/conf/users.auth.php and /var/www/dokuwiki/conf/acl.auth.php
  • maybe transfer /var/www/dokuwiki/conf/local.php, but inspect the file and remove anything that could obviously not work on the new
system such as ip address, urls, authentication mechanisim....
  • manually adjust the settings and install the plugins you need
  • switch the old turnkey off, adjust network settings on the new one, reboot, enjoy.

Downtime is very short (the time to adjust network settings and one reboot) and you have all the time you need to setup your new DokuWiki.
This post was edited on 2020-01-03, 09:02 by schplurtz.
topic: How to run Dokuwiki on a Shared Network Drive  in the forum: General Help and Support Server Setup
Avatar
schplurtz (Moderator) #7
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 68016
Hi,

As a a web application, DW is actually run by (or accessed through) a webserver application. For security reasons, webservers are launched under a dedicated system account whose name vary from OS to OS. In this case,  MartinR runs a unix like system, where the system account for web apps is named apache and that system account belongs to the apache group. On unix systems it is common to refer to user and group in this way : user:group. Only the apache:apache system account needs to access the files. Even if you have hundreds of DokuWiki users because hese DokuWiki users are not system accounts, they only exist in DokuWiki
This post was edited on 2019-12-27, 07:48 by schplurtz.
topic: Accidentally messed up DokuWiki (I need some help with how to revert changes in the config settings that messed up my dokuwiki completely)  in the forum: General Help and Support General Stuff
Avatar
schplurtz (Moderator) #8
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67953
open the file dokuwiki/conf/dokuwiki.php with a text editor
No ! You should never change this file.

open dokuwiki/conf/local.php and remove the line that reads
$conf['baseurl']=....
As pop suggested, make a backup first.
topic: Configuring Dokuwiki basedir with Linux and Nginx  in the forum: General Help and Support Server Setup
Avatar
schplurtz (Moderator) #9
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67860
Hi,

• you don't run DokuWiki as a systemd service. DokuWiki is a PHP application and PHP applications don't run as service. PHP applications rely on the webserver to launch various PHP scripts on demand; for each HTTP request. In your case, you have to set up a php-fpm service -- whose job is to actually interpret the PHP scripts -- and configure nginx to pass requests to that php-fpm service. To install php-fpm, refer to your particular distro documentation, but this is usually as simple as installing the php-fpm package. Once done, see https://www.dokuwiki.org/install:nginx to setup nginx. The example is given for dokuwiki at the root of a website. So, you have to change "location /" to "location /wiki", "location /lib" to "location /wiki/lib", "rewrite ^/_media" to "rewrite ^/wiki/_media" and so on...

• Once done, run the installer. (it will be https://order.life/wiki/install.php).  see https://www.dokuwiki.org/installer , this will create the required minimum settings. Among other things, it will create conf/local.php

• Never edit conf/dokuwiki.php, but override default settings in conf/local.php . See https://www.dokuwiki.org/config

• Usually, there is nothing to configure in DokuWiki to tell it it is located at /something. DW autodetects its own URL. If it does not work properly (images not shown for example), then set basedir in conf/local.php. It might help. See https://www.dokuwiki.org/config:basedir

You might also want to read the whole install documentation. https://www.dokuwiki.org/install.
topic: No php support  in the forum: General Help and Support Installation and Configuration
Avatar
schplurtz (Moderator) #10
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67839
Je viens de comprendre  qu'il y avait un forum "french discussion". Merci de me répondre malgré tout :-)
Vraiment ?.

Mon fichier "user.auth.acl" avait disparu
Il n'y a pas de fichier "user.auth.acl". Il y a "conf/users.auth.php" et "conf/acl.auth.php". Créer un fichier "user.auth.acl" ne peut pas avoir d'effet.

en mode navigation privée, tout va bien
avec Brave
L'accès semble correct également
Au final, donc, ça fonctionne. Tant mieux. On ne comprend pas bien ce qui ne fonctionne pas mais c'est juste un soucis avec ton navigateur. DW fonctionne bien.
topic: No php support  in the forum: General Help and Support Installation and Configuration
Avatar
schplurtz (Moderator) #11
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67817
Bonjur Domirock.

Je suis sous xubuntu. Les MAJ sont faites régulièrement
C'est déjà mieux que robocop, lui tourne sous MS DOS.

Normalement, ici on parle anglais. enfin bon.

est-ce que c'est un dokuwiki installé en paquet Debian ?

Pour savoir ce qu'est NoScript, tu peux demander à un moteur de recherche.
Est-ce qu'avec un navigateur sans aucune extension ça fonctionne ?
topic: Sharing login credentials between Pleroma and Dokuwiki  in the forum: General Help and Support Server Setup
Avatar
schplurtz (Moderator) #12
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67801
Hi,
they use postgresql. Try DW authpdo.
topic: Lighttpd + Dokuwiki - Won't start, include file not found  in the forum: General Help and Support Installation and Configuration
Avatar
schplurtz (Moderator) #13
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67734
hum I did not read your post with the attention it needed. Sorry. Is the file readeable by lighttp ?
topic: Lighttpd + Dokuwiki - Won't start, include file not found  in the forum: General Help and Support Installation and Configuration
Avatar
schplurtz (Moderator) #14
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67733
I absolutely don't know lighttpd.
2019-11-09 04:07:15: (configfile.c.1232) include file not found:  conf-enabled/10-cgi.conf
The file is not found. I see 2 possibilities :

1) The file conf-enabled/10-cgi.conf is a symlink that points to a non existent file. Where is this conf-enabled directory ? I guess somewhere between /etc/lighttpd , /usr/share/lighttpd/ , and the current directory. Maybe you are missing a module or lighttpd-foobar package. Maybe this is the remnants of a previous installation that you don't remember clearly... Maybe you should just remove this dangling symlink.

2) You have to change directory before you run your start command so that the conf-enabled/10-cgi.conf can be found ; but I doubt that.
topic: [Solved] Defining Interwiki links in farm-animal wiki site using subdomains  in the forum: General Help and Support Syntax and Usage
Avatar
schplurtz (Moderator) #15
Member since Nov 2009 · 505 posts · Location: France, Finistère
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post ID 67707
If I understand you well, users at your sites will use external link syntax to point to internal page ? Well if you can't educate your users, you can still write an action plugin that catches the IO_WIKIPAGE_WRITE event. In your handler, you have access to the page wiki text, and you have the possibility to change that text before it is written. See https://www.dokuwiki.org/devel:event:io_wikipage_write. A global search and replace could change external links that point to an internal page into a real internal link.


Now the second problem: make external links that match *.myfunkywikis.com internal links. I think you can write your own renderer plugin to extend the Doku_Renderer_xhtml class.

See the documentation on renderer.

In your class, I think you only have to redefine 2 functions : interwikilink and externallink.

In the function externallink(), if the link matches *.myfunkywikis.com, render it as an internal link. The same for interwikilink().


The plugin wizard will create the plugin structure for you. https://pluginwiz.dokuwiki.org/
Close Smaller – Larger + Reply to this post:
Special characters:
Page:  1  2  3 ... 32  33  34  next 
Special queries
Go to forum
Imprint
This board is powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2015 by Yves Goergen
Current time: 2020-01-20, 02:12:08 (UTC +01:00)