Also, fix a logging context name.

erp5_officejs_support_request_ui: Let the search bar only search the items which type are 'Support Request'

Add some support requests to let the listbox have enough items to paging.

When the homepage refreshed with "field_listbox_begin_from", the
listbox always on loading state.

We should not call child gadget's "changeState" directly. Instead,
we need to call child(listbox) render in parent render.

Which can let the child listbox aware of the parameter change in the parent gadget.

This fixes an issue :
When we work on two web apps in two different domains
but using the same erp5 as storage backend,
the allow origin response header was equal to one sole
domain for the two web apps.

This way it is easier to further extend it without risking key conflicts
in catalog parameters, which in turn would either lead to simple TypeErrors
("multiple values for parameter ...") or to criterion being accidentally
ignored.
Update callers.
These methods are young enough that no other callers should exist yet.

* This kind of query: 'foo:("bar", "couscous")' is currently not supported by query storage

follow_up | Related Object
creation_date | Creation Date
translated_validation_state_title | State

This action should only be possible if user have View History
permission.

erp5_data_protection relies on removing the "View History" permission to
make sure users cannot see the properties before protection in the
history tab. This was supported by Base_viewHistory, but not by ZODB
History

If we call Base_translateString before storing the message in the
history, the message will be translated when this action is used and
stored as translated using the language of the user executing this action.

The proper way is to store a message in history, so that it is rendered
when displayed.

Clone of nexedi/erp5!339

/reviewed-on nexedi/erp5!391

Also, document that value order in base_category_dict is meaningless.

@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