mirror of
https://git.code.sf.net/p/seeddms/code
synced 2025-10-30 20:51:22 +00:00
42 lines
2.1 KiB
Plaintext
42 lines
2.1 KiB
Plaintext
Allow operations like delete, move, approve, etc. on a list of documents
|
|
|
|
Do not allow any operation on a document if is locked.
|
|
|
|
Do not use sanitizeString anymore. LetoDMS_Core should take care of
|
|
escaping chars when saving to database. LetoDMS should make sure to replace
|
|
html when the data is output. Check all places where data from the database
|
|
is shown on the page or put in javascript code (like href="javascript: ...").
|
|
|
|
Upload of multiple documents without an applet
|
|
|
|
Delete document from full text index when document is deleted
|
|
|
|
Do not show documents which are not reviewed or approved or rejected
|
|
|
|
installation script:
|
|
- user simply unpack the tar.gz in a server folder and access that folder
|
|
- on startup if there are installation problems php automatically run the configuration script
|
|
- the data folder creation can be automatic (user/password for server) or manual (yet ready folder)
|
|
- same for the db and the db user
|
|
- db creation (run of create table.sql) shoul control if db is yet filled and control for update to do
|
|
- the inc/inc.Setting.php is filled asking user entry
|
|
- the script can be used to test installation problem without affecting the current installation
|
|
|
|
The document state is currently not updated when a user is deleted from users list.
|
|
For example user A is the only pending approver for a document, then the document is in draft state.
|
|
When A is deleted the document should pass automatically in release status.
|
|
This could be done with a new function controlling the existance of all the pending approver/reviewer
|
|
and eventually updating the status of the document. This function will be called by user-remove function.
|
|
|
|
Sometimes in the DB are written messages strings in plain language whose
|
|
language depends on the current user and will never be translated.
|
|
This can be avoided using only coded messages
|
|
|
|
The mail language is translated using the current user language but should use
|
|
the receiver language (not easy).
|
|
|
|
In my Documents->all documents there should be two lists: one (the current) with
|
|
the user's document, and another with the user's updated document (that's because
|
|
one user could have updated a document not owned by himself)
|
|
|