is called in Web Sections or Web Sites.

These expected that absolute_url returned no trailing slash,
so updates in code and page templates were needed

Also, url that is published in
test_14_AccessWebSiteForWithDifferentUserPreferences
iotherwise the response is the redirect, making the test fail

from double slashes. This to give compatibility with definition
in actions on Web Section and Web Site portal types, for which now
absolute_url returns a trailing slash, so definitions like:

string:${object_url}/WebSection_xxx

would create a url with double slashes

in case we publish with different languages

Better for Search Engine Optimization

Also, raise redirect to add trailing slash only if request is GET

renderJS gadget HTML uses relative URLs to link to there javascript/CSS files.
Absolute URL calculation is resolved dynamically by the browser when loading the gadget.

When accessing an ERP5 web section without a trailing / in the URL, the browser will calculate absolute URL from the parent document and not the web site itself.

Example:
In http://foo.com/web_site_module/bar , the relative URL couscous.js will be resolved http://foo.com/web_site_module/couscous.js
If couscous.js is a document from DMS (Web Page for example), such URL can not be resolved and leads to a 404 error.

One solution to solve this is to redirect (302) the browser when accessing a Web Section (Web Site is a web section) directly in ERP5.
Example:
http://foo.com/web_site_module/bar ->  http://foo.com/web_site_module/bar/
But  http://foo.com/web_site_module/bar/view should not redirect

@Nicolas uses worklist as one of many gadgets in one page thus stackable empty worklist is necessary (before it was positioned as an fixed element).

/reviewed-on nexedi/erp5!387

fixes #20170911-1AD62FB

Reports is easier to read if lines are sorted by third party name then
by date.

We also sort by transaction title to keep stable ordering of lines.

Use portal_membership.getAuthenticatedMember().getUserValue() instead.

This issue was reported by Nicolas. When embedding the
support request application in other App. The `options`
parameter in the `render` function is undefined, so the
`field_listbox_begin_from` can not be found. Use
`getUrlParameter` to retrieve it from URL.

The commit 1fbf9ba9 put
the title in wrong order. Correct it. This commit is not
a revert, it is a fixing.

- "Restore Filter" button.
Allow to remove the filters applied on the homepage
listbox. Disabled when no filter applied.

- Generate RSS button.
Generate the RSS link. Click this button will generate
a RSS link for an anchor tag and hide the button itself.

- Create Support Request button.
Make the appearance same in desktop and iphone browser.

/reviewed-on nexedi/erp5!386

Currently, the domain selection is implictly on node_category

`portal_catalog/erp5_mysql_innodb/SQLCatalog_makeFullTextQuery` is
provided by full text implementation business template.

The scriptable key definition is intentionnaly left in this business
template because we don't have a mechanism like template_keep_path_list
to prevent uninstalling the scriptable key when business template is
updated.

/fixes #20170620-8BDEBE
/reviewed-on nexedi/erp5!300

state_dict.items doesn't exist and trying to access it raises an error

And update appcache

/reviewed-on nexedi/erp5!381

[officejs_monitoring] Some performances improvement, speed up hosting subscription list page rendering

Speed up display of hosting subscription list by reducing the amount of queries.
If a document is not synced (due to an error) change the status of that document to WARNING so that monitor will
tell when instances/servers are offline.

Since by default insecure and unrestricted code execution is disabled
and manual intervention by the user is required reflect this in
description.

Before executing any code check if server side is configured to execute
unrestricted code.

Before:

  self.portal_components.reset(force=True,
                               reset_portal_type_at_transaction_boundary=True)

After:

  self.portal_components.reset(force=True)

If the reset_portal_type_at_transaction_boundary is True, it does reset
component only once at the end of transaction.
(In detail, it reset component document module on the fly, and reset
 the component portal_types in the end of the transaction)

However, it is possible that those components are required in the middle of
the transaction while installing the business templates. For exmaple:
 - A method of a component is triggered while installing
 - A document component is required in a different business template,
   and those buisiness templates are installed inside a single transaction
   by upgrader.

Thus reset here on the fly.