seeddms-code/utils
2020-02-03 18:28:45 +01:00
..
.htaccess support for apache 2.4 2019-07-30 06:38:54 +02:00
adddoc.php set dms and user in controller 2018-03-12 18:34:17 +01:00
createfolder.php check version of database, do not call deprecated functions 2013-06-06 14:41:12 +02:00
indexer.php modernize script 2020-02-03 18:28:45 +01:00
README.md more info on scripts in utils folder 2018-11-13 08:48:00 +01:00
seeddms-adddoc fіx argument passing to php file 2016-01-31 11:20:11 +01:00
seeddms-createfolder fіx argument passing to php file 2016-01-31 11:20:11 +01:00
seeddms-indexer fіx argument passing to php file 2016-01-31 11:20:11 +01:00
seeddms-xmldump fix calling php file 2016-09-07 16:49:52 +02:00
xmldump.php fix typo in attribute name 2017-03-09 10:22:38 +01:00
xmlimport.php fix typo in variable name 2020-01-22 14:26:43 +01: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.