admin: add utility functions

[batopa]

Add "Utility" to left menu in Admin module.

This section has to contain some utility functions that are present in some shell script.
List of useful functions:

• cleanup (bedita shell: delete tmp files)
• export (bedita shell: specify in UI if export has to be done with or without media)
• import (bedita shell)
• modules (bedita shell: enable/disable core module)
• rebuildIndex (dbadmin shell: rebuild search text indexes)
• cleanup (dbadmin shell: remove old items from log/job tables)
• others....

[batopa]

Fare parte UI

[qwerg]

gestione core modules come plugin modules

alrti comnadi come pulsanti

[qwerg]

utility view added,

commands:

cleanup files /
cleanup logs /
rebuildindex /
updatestreamfield /
clearmediacache

126c216

importData view added as {bedev} in menuLeft.tpl,
may have same behaviour as import command in "publications/section".

[qwerg]

Core module management.

View for turning OFF/ON core modules (just on/off, not plug/unplug) (TODO: controller, of course)

Admin and Publications(areas) modules should not be turned off

Questions: are we assuming that superusers/admin only have access on this area? so further check on modulesList permission is not necessary?

2f31fee

[batopa]

Modules should not be turned off

• Admin
• Users

Add drag and drop to reorder modules priority

[batopa]

1083b6b toggle core modules

[batopa]

0c684fc, fc5d08f, 73ab12a, 9f58a8f

Implemented utility updateStreamFields and generic workflow.

Clicking on "GO" button an ajax call is launched. If operation has success an informative alert is triggered. If an error occurs an alert and BEdita error msg are triggered. Andrea choose if you want only alert or only BEdita error msg.

[batopa]

af2d1ab

added rebuildIndex (missing creation of log file with results)

[batopa]

09e9112 added parameter at SearchIndex::rebuildIndex() to avoid to return array of success items

[batopa]

79cfd1d

impemented the utility functions cleanup cache_', '''empty logs''', '_clear media cache.
Added an Utility model class to handle common operations used both in UI and in shell scripts.

For now both alert and standard BEdita info/warn/error messages are triggered. (What should we use? Andrea?)

• Error => triggered if the operation can't continue
• Warning => triggered if the operation was done but some errors occured. In this case the standard BEdita message detail show the log (is it ok?)
• Info => triggered if the operation was done successfully

[batopa]

(In 46c78bd) trunk - sort modules see #295

[batopa]

0aac854

I decided that we use standard info/warning/error of BEdita. Alert removed.
For other utility functions we'll open new specific tickets.