seeddms-code

mirror of https://git.code.sf.net/p/seeddms/code synced 2024-11-26 15:32:13 +00:00

History

Uwe Steinmann a9224b0070 fix some typos		2018-03-26 14:08:12 +02:00
..
.htaccess	prohibit access	2016-09-22 17:24:57 +02:00
adddoc.php	pass list of category objects to addDocument instead of cat ids	2018-02-20 06:35:16 +01:00
createfolder.php	check version of database, do not call deprecated functions	2013-06-06 14:41:12 +02:00
indexer.php	do not expect a return value from $indexer->delete()	2016-04-05 17:03:03 +02:00
README.md	fix some typos	2018-03-26 14:08:12 +02: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	take out include on missing file	2017-03-06 10:53:20 +01:00
xmlimport.php	issue warning instead of info if object already exists	2017-03-09 07:39:46 +01:00

README.md

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>. If you run the adddoc.php script make sure to run it with the permissions of the user running your web server. It will copy files right into your 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.

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.