DokuWiki

Mr. Andreas, valued DW-team, valued user, currently an error appears, using a syntax similar to other pages with similar media-content: {{gallery>user:johann:gallery:archiv2014:?showname&2&datesort}} Error: Fatal error: Allowed memory ... [More] size of 134217728 bytes exhausted (tried to allocate 134217736 bytes) in /var/www/clients/.../web/inc/JpegMeta.php on line 1810 My person wonders of what could be the reason of it and how it could be solved (aside of allowed memory, where there is no accessibility to make changes). Maybe a caching issue? The error would remain even the txt-file is replaced without a gallery-syntax in it via ftp. The img have been uploaded via ftp as well and just saw that there are two cache-issues at issue-tracker of the plugin mentioned. [Less]

IP addresses will not be shown to normal users when there's a login name to display (eg. not on anonymous edits). Admins and Managers will always see the IP addresses. How can I hide IP address(in revisions page) to manager(group)s?

IP addresses will not be shown to normal users when there's a login name to display (eg. not on anonymous edits). Admins and Managers will always see the IP addresses. How can I hide IP address(in revisions page) to manager(group)s?

Sorry, Myron is right, of course. My answer was incomplete and wrong in that sense. When writing, I did not have in mind the fact that an archiving take place via the media manager when a newer version of a media file is uploaded. That's because I ... [More] have never needed this option. And the reason for this is, among other things, that media files are usually loaded onto the server in their web-optimized secondary format (PDF are created from Word files, JPG and PNG from Photoshop, for example). There must then be a backup of the primary data anyway. But in other scenarios than mine, that might look quite different.  [Less]

Sorry, Myron is right, of course. My answer was incomplete and wrong in that sense. When writing, I did not have in mind the fact that an archiving take place via the media manager when a newer version of a media file is uploaded. That's because I ... [More] have never needed this option. And the reason for this is, among other things, that media files are usually loaded onto the server in their web-optimized secondary format (PDF are created from Word files, JPG and PNG from Photoshop, for example). There must then be a backup of the primary data anyway. But in other scenarios than mine, that might look quite different.  [Less]

Ah, okay. Thanks. I figured Doku was doing some sort of indexing or something. It does.  It records image data, keeps a history of changes including storage of old versions.  Much the same as it does for pages.  You can see this if you open the ... [More] top-level media manager.  If you click on an image, at the right there will be tabs for image data and history. It's useful if you ever want to recover a previous version of an image. [Less]

Ah, okay. Thanks. I figured Doku was doing some sort of indexing or something. It does.  It records image data, keeps a history of changes including storage of old versions.  Much the same as it does for pages.  You can see this if you open the ... [More] top-level media manager.  If you click on an image, at the right there will be tabs for image data and history. It's useful if you ever want to recover a previous version of an image. [Less]

usually I set the option 'userewrite' to DokuWiki internal'. That's ok redirected to the Login page. Those are not related. When you log out you're sent to the login page. There's no config for that. ...

On Tue, Oct 9, 2018 at 12:14 PM Kai Peter kp@xxxxxxxxxxxxxxxxxxx wrote: to stay on the page I edited last. Yes that's hard-coded to redirect to login: ...

On 2018-10-11 18:40, Andreas Gohr wrote: usually I set the option 'userewrite' to DokuWiki internal'. That's ok to me, but there is one caveat: if I logout from a page I will be redirected to the Login page. Those are not related. When you log out you're sent to the login page. ...