Merge branch Issue#151 with master

See merge request !88

# Conflicts:
#   ui/nG6/class.tx_nG6_eid.php

Same as last commit.

issue #151

There was a if( xxx = yyy) instead of a if( xxx == yyy) in
class.tx_nG6_eid.php .

PS: If asked, I will deny everything.

issue #151

I don't see any difference yet, but the master version of this file
return no result table, and this version does.

I might revert this commit if it is useless.

issue #151, for the new tag V3.2.5.3

Merge branch issue #151 with master

See merge request !85

# Conflicts:
#   ui/nG6/lib/class.tx_nG6_utils.php

2 functions were missing from my version of this file, get_save_dir()
and get_project_data_save_dir().

A function was missing from the last commit + merge,
get_available_space_ids() from tx.nG6_utils.php.

issue #151

Merge branch Issue#151 with master

See merge request !84

Merge branch Issue#129 with master

See merge request !83

# Conflicts:
#   ui/nG6/pi6/administration_view.tpl

Same branch as the old issue151, and same commit as
c5f5c618 .
I have deleted the branch and commits earlier this week, I thought the
merge was already done.

Also, this time I pushed the (much needed) updated ng6_database.sql
file.

(Once again, when this update goes live, an update to the DB structure
will be needed. See the related issue.)

Issue #151

# Conflicts:
#   ui/nG6/lib/class.tx_nG6_utils.php

(Both lines looked the same to me. RT)

"The user you entered doesn't have the rights to perform[...]"

issue #129

Before launching a project space migration (from the new form in the
single project view), we ask for a user+ pwd and run the following test:
We use the given user+pwd to run a "touch+rm" in the current project's
space's data directory. In production, only ng6, root and users in the
apache group can perform this action.
(So only people with access to those credentials will be able tu run the
switch_space_id workflow from there)

More infos in the issue.

Issue #129

The 'switch_space_id' migration workflow is now displayed for the
current project's administrator users.
(table fe_rights, right_level = 2)

Superadmin users can still launch the migration of any project.

(issue #129)

The "switch_space_id" migration workflow form, in the single project
view, will only be displayed to the project's administrators
(right_level '2' in the 'fe_rights' database table).

It stays available to superadmin users on all projects.

(issue #129)

I removed two useless comments, that I left for no reason.

issue #151

- The "size" filter criteria has been replaced by a "space" filter.
- The default value is "no filter".
- The result table has one more column, "Project space".
-The search algorithm has been updated.

WARNING : Check the issue #151 to find the SQL commands to update the
views's structures.

(Issue #151)

#156 correct style

See merge request !77

Merge branch Issues#143 with master

See merge request !79

Big update for the switch_space_id workflow

See merge request !80

#155 convert bool to int to avaoid warning

See merge request !78

-The workflow now handles empty (no data) runs and analyzes, and more
errors.
-A lot of user cases have been tested.

issue #129

-New better logs, in MoveProject.stdout and (if the workflow fails) in
ng6.log
-The workflow now handles empty analyzes and runs.
-A lot of user cases have been tested.

issue #129

The available spaces can now be displayed and selected via a select
field instead of a simple textfield.

issue #151

Merge branch issue#150 with master

See merge request !74

Merge branch issue#153 with master

See merge request !75

The get_directories_structure_and_content() function has been reworked
to make the projects, runs and analyzes names normalization way more
consistent. This will solve the differences between sources and
destinations in this function.

issue #153

issue #150

Merge issue#129 with master

See merge request !72

- I have removed the "local = True" parameter to execute the workflow on
the computing cluster instead of ng6's host.
(It was a test parameter, only meant for testing.)

issue #129

Merge branch issue#129 with master

See merge request !69

Merge branch issue#119 with master

See merge request !71

single analysis views.

issue #119