'add_user' and 'delete_purge_data'.

The code returned in AJAX is now evaluated as an INT instead of STRING.

issue#170

The ajax return codes (0,1,2 and 3) cannot be evaluated as strings.
"if (val == '1') {" becomes "if (val == 1) {" .

Warning : We could also leave this file as it is, and make sure the
value returned in AJAX is a String.

issue #170

Merge branch issue#161.2 with dev

See merge request !97

The get_purge_mail has been reworked to avoid redundancy.

issue #161

New "Send mail without extension" button, that sends the purge demand
mail without the content related to retention extension.

issue#161

Merge branch issue#161 with dev

See merge request !96

The log instruction might only work in the test environment.
I forgot to remove this line in the last commit, my bad.

issue#161

Merge branch Issue#161with dev

See merge request !95

# Conflicts:
#   ui/nG6/res/js/tx_nG6_pi6.js

2 search criterias have been added, filter on space (project space_id)
and delay exceeded (yes or no).

And there is a new "Refresh list" button to handle the new filters.

issue #161

A new "Project space" column has been added to the admin "Process mail
demands" table.

issue #161

Merge branch Issue#163 with dev

See merge request !94

"Process mail demands".

The links now work, and are made dynamically.

issue #163
(linked to issue #146)

"Admin > Process mail demands".

The links now work, and are made dynamically.

issue #163
(linked to issue #146)

Merge branch issue#146 with dev

See merge request !93

This update was made to recover the redirection page id dynamically from
the typo3 template values.

Issue #146

Merge branch issue#146 with dev

See merge request !92

Merge branch issue#137 with dev

See merge request !91

In the "Adminsitration > Extend project", projects links have been
fixed.

Issue #146

We don't display the static "two year" anymore in the purge mail.

Issue #137

Merge branch issue#157 with dev

See merge request !89

Merge branch issue#154 with dev

See merge request !90

The projects count has been updated to ignore the hidden projects if
they do not appear in the list.

issue #154

1 import was missing to use the new data type "ng6space".
(So the space selection is a nice dropdown menu, instead of a simple
textfield.)

issue #157

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