https://forum.opendocman.com/ Thu, 04 Jun 2026 20:11:20 +0000 MyBB https://forum.opendocman.com/thread-1040.html Sat, 01 Feb 2020 16:03:10 -0500 adminla]]> https://forum.opendocman.com/thread-1040.html Hello,

We are moving our support discussions to our new Discourse site at https://discourse.opendocman.com/ . Please visit there if you have a questions and/or comment about OpenDocMan. This forum site will remain for archival purposes only.]]> Hello,

We are moving our support discussions to our new Discourse site at https://discourse.opendocman.com/ . Please visit there if you have a questions and/or comment about OpenDocMan. This forum site will remain for archival purposes only.]]> https://forum.opendocman.com/thread-874.html Tue, 20 Oct 2015 00:13:35 -0400 andreas_64]]> https://forum.opendocman.com/thread-874.html
new to this forum + coming up with a language customisation question:

I was able to edit the german.php (which contains remainders of English strings in version 1.3.4) to get rid of / modify most of these.

However: top of each page, there is a string "You are here" which is persistently displayed in English and - seemingly - not controlled by german.php (not by english.php either, as it seems, the string is not contained in either language file)

Found the string hardcoded in header.tpl of tweeter template and patched it also hardcoded meanwhile (works well for my small installation but of course breaks language independence of code)

Is there a better way to do this?]]>
new to this forum + coming up with a language customisation question:

I was able to edit the german.php (which contains remainders of English strings in version 1.3.4) to get rid of / modify most of these.

However: top of each page, there is a string "You are here" which is persistently displayed in English and - seemingly - not controlled by german.php (not by english.php either, as it seems, the string is not contained in either language file)

Found the string hardcoded in header.tpl of tweeter template and patched it also hardcoded meanwhile (works well for my small installation but of course breaks language independence of code)

Is there a better way to do this?]]> Thu, 04 Jun 2026 16:11:20 -0400 ]]> Trying to upgrade from 1.2.6.3 to 1.2.6.5 using following article:
<!-- m --><a class="postlink" href="http://www.opendocman.com/dokuwiki/doku.php/upgrading_opendocman">http://www.opendocman.com/dokuwiki/doku ... opendocman</a><!-- m -->
On step 7 I can not see appropriate upgrade link that matches my version (1.2.6.3).
The closest version is 1.2.6.2 which less than my version.
How to upgrade?]]> Trying to upgrade from 1.2.6.3 to 1.2.6.5 using following article:
<!-- m --><a class="postlink" href="http://www.opendocman.com/dokuwiki/doku.php/upgrading_opendocman">http://www.opendocman.com/dokuwiki/doku ... opendocman</a><!-- m -->
On step 7 I can not see appropriate upgrade link that matches my version (1.2.6.3).
The closest version is 1.2.6.2 which less than my version.
How to upgrade?]]> https://forum.opendocman.com/thread-417.html Tue, 07 Jun 2011 00:51:43 -0400 Mikeyy]]> https://forum.opendocman.com/thread-417.html In attachment there is plug-in for individual file expiration.
Attachment has been tested in non productional enviroment, all bugs that we found removed. If you notice any other bugs please lets us know in this topic.

InExp adds 2 new fields, expiration date and notification date. On notification date every user that has r (read) permission will be notified that file is about to expire in X days.
On expiration date file will be handled acording to ODM global settings for expired files with one difference, every expired file will get new text in front of DESCRIPTION , [EXPIRED]. We done this so expired files could be easily found in large sistems via search option.

Also, 3rd global ODM option, "Notify reviewer only" will still notify all users with R permission, but will not change file status like other options.

Thanks Stephen for changing plugin code so this plugin could work. Now you know what you need to change for all other plug-ins.

If you have any questions about usability ask here.

EDIT: It seams forum migration killed attachments. Updating last 2 versions.

  InExp-1.4.zip (Size: 22.8 KB / Downloads: 41)

  InExp 1.3.tar (Size: 69.5 KB / Downloads: 13) ]]> In attachment there is plug-in for individual file expiration.
Attachment has been tested in non productional enviroment, all bugs that we found removed. If you notice any other bugs please lets us know in this topic.

InExp adds 2 new fields, expiration date and notification date. On notification date every user that has r (read) permission will be notified that file is about to expire in X days.
On expiration date file will be handled acording to ODM global settings for expired files with one difference, every expired file will get new text in front of DESCRIPTION , [EXPIRED]. We done this so expired files could be easily found in large sistems via search option.

Also, 3rd global ODM option, "Notify reviewer only" will still notify all users with R permission, but will not change file status like other options.

Thanks Stephen for changing plugin code so this plugin could work. Now you know what you need to change for all other plug-ins.

If you have any questions about usability ask here.

EDIT: It seams forum migration killed attachments. Updating last 2 versions.

  InExp-1.4.zip (Size: 22.8 KB / Downloads: 41)

  InExp 1.3.tar (Size: 69.5 KB / Downloads: 13) ]]> Thu, 04 Jun 2026 16:11:20 -0400 Stephen]]>
Thanks.]]>
Thanks.]]>