2012-01-17 08:35:12 +00:00
Add a Search Function to Related Documents. When attaching a related document their should be a search function to easily find the document you would like to relate.
2011-12-21 12:15:07 +00:00
Export/Import content as xml (even for subfolders)
Copy recursivly folders
2011-11-29 07:21:25 +00:00
Allow operations like delete, move, approve, etc. on a list of documents
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
2011-09-25 06:26:29 +00:00
2011-07-21 06:55:53 +00:00
Delete document from full text index when document is deleted
2011-09-25 06:26:29 +00:00
Do not show documents which are not reviewed or approved or rejected
2011-07-21 06:55:53 +00:00
2010-10-29 13:19:51 +00:00
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)
