seeddms-code/utils
2020-09-29 16:42:09 +02:00
..
.htaccess support for apache 2.4 2019-07-30 06:38:54 +02:00
adddoc.php replace all ˝\n" by PHP_EOL 2020-09-04 09:21:40 +02:00
createfolder.php replace all ˝\n" by PHP_EOL 2020-09-04 09:21:40 +02:00
indexer.php get $index and $search before foreach loop 2020-09-29 16:42:09 +02:00
README.md more info on scripts in utils folder 2018-11-13 08:48:00 +01:00
seeddms-adddoc add support for uploading new document version 2020-05-25 14:45:55 +02:00
seeddms-createfolder replace all ˝\n" by PHP_EOL 2020-09-04 09:21:40 +02:00
seeddms-indexer do not check for db version if disabled 2020-06-03 18:21:56 +02:00
seeddms-xmldump get SEEDMS_HOME from parent dir if not set 2020-09-04 09:34:45 +02:00
xmldump.php replace all ˝\n" by PHP_EOL 2020-09-04 09:21:40 +02:00
xmlimport.php replace all ˝\n" by PHP_EOL 2020-09-04 09:21:40 +02:00

Running one of the scripts

Scripts in this folder are ment to be called on the command line by either executing one of the shell wrappers seeddms-* or by calling php -f <scriptname> -- <script options>. Most scripts have an option -h or --help which list the available script options.

Be aware that this scripts are not officially supported. Use them with care and always ensure to have a backup of your data before running any of them.

Do not allow regular users to run this scripts!

None of the scripts do any authentication. They all run with a SeedDMS admin account! So anybody being allowed to run the scripts can modify your DMS content.

Adding documents

Single documents can be added with seeddms-adddoc. The script is just for adding new documents but not for adding a new version. As the script is just a small wrapper around the controller for adding documents by the web gui, it will also trigger all hooks, but it will not send any notification to the users.

If you run seeddms-adddoc make sure to run it with the permissions of the user running your web server. It will copy files right into the content directory of your SeedDMS installation. Don't do this as root because you will most likely not be able to remove those documents via the web gui. If this happens by accident, you will still be able to fix it manually by setting the propper file permissions for the document just created in your content directory. Just change the owner of the document folder and its content to the user running the web server.

Instead of regulary updating the full text index from the web gui, you can as well run seeddms-indexer in a cron job. It will either update or recreate the full text index.