We don't want to include a full build of locales, so for now since we
needs it only for french, we include the localization inline here.

HACK: This needs more thinking about what is the right way. This way
works for now.

This is done using the obsolete/slow translate/translateHtml because we
needed this for a customer project where we are not yet using the new
techniques for translation.

HACK because we'll do this with domsugar in erp5 master

The "New ${portal_type} created." is impossible to translate in
languages using genders for nouns, for example in french, New is
translated as "Nouveau" for masculine portal types and "Nouvelle" for
feminine portal types.

Instead, translate the full "New Support Request created." sentence.

    The separation aims to reduce the dependency required to use the macros, where:

       * erp5_web_renderjs_ui_test contains the tests and the dependencies to run the tests
       * erp5_web_renderjs_ui_test_core contains the reusable macros, that can be used on other projects to write their own tests.

to match the button on the front page

With virtualhosting, there can be an empty path element at the beginning
of the path.

We fixed login forms to use consistently "Username", some translation
did not have message for "Username", but only for "user name".
Add missing "Username" messages, with same translation as existing one
for "User name"

fix a problem when that commit was cherry-picked here

KeyError: 'module.erp5.GeneratedAmountList'

in test_rebuild_erp5_core

what's wrong with this anyway

Without it, it is not possible to upgrade instances since:
48c45fbd

This gets rid of:
  WARNING ERP5Type.dynamic Cannot find a portal type definition for 'ERP5 Form', trying to guess...

testUpgradeInstanceWithOldDataFs: Upgrade erp5_upgrader too (it was in keep
list until now) as old Data.fs contains ERP5UpgraderUtils Extension with import of
Products.ERP5Type.Log. Although, erp5_upgrader should probably be automatically
upgraded before even starting the upgrade...

Otherwise "conflicts" happen when a web site is configured to use
anotehr translation gadget

It may not be the case if there is only one view, as defined by the hateoas spec

upload document and run all activities around this upload takes time, so we use a larger timeout

erp5_officejs_support_request_ui_test: Add test to make sure we have all expected actions to access support request web site

* Check if each portal_type has the expected view action
* add test to cover all possible attachments in a Support Request

HACK erp5_officejs_support_request_ui: Simplify code to render the expected action to preview any attachement document

Some portal types don't have preview action reference. In such case, we get html_view

erp5_web_renderjs_ui: Refactor code to support more than option as page

Sometimes we can display "preview" or "html_view"

erp5_web_renderjs_ui: Small changes on router to follow latest erp5 master

This improve the compatibility with ERP5JS

This is something we can do in TALES, it was supported in the old UI, so
we keep compatibility in HAL JSON API.

Replace it by domsugar.

This speed up gadget class generation (handlebars template parsing is
slow).

Introduce the object_jio_jump action category to mark all compatible actions.

erp5_xhtml_style supports object_jio_jump.

A correct redirection is needed to jump in both UI.

ERP5JS will display modules on the current document context,
as if the jump was instead a object_view action.

erp5_officejs_support_request_ui: Add begin date to the query when user click on "Last Month Activity"

The filter when the user click on the "Last Month Activity" chart filter Support Request only by status (Submitted / Open / Suspended / Closed). So on the table "Recent updates", all the support request with the chosen status appear. There is no filter by "Begin Date" for the last 30 days, which is no coherent with the "Last Month Activity". => It should appear only the support request with the chosen status with a begin date < D - 30 days

Make sure we have gadget.state.form_id

It seems that with ${here/portal_url} returns the ERP5 url , for example http://nohost/erp5 instead of

http://nohost/erp5/web_site_module/renderjs_runner/

Table columns to be displayed by default in the following (from the left to the right of the screen) :

Title
Visa Files Reference
Type
Requester
Begin Date
Comment Date (with possibility to sort the table by this column desc and asc)
Comment Author
State

According to Google's branding guidelines [1], using zocial like we did is not
OK because the logo is different.

To comply with Google's branding guidelines, we simply use an image from
"Download files" section of the Sign-In Branding Guidelines page. Using a png
image is not really good, but a vector version would require to download a
font, so the image way is easier.

1: https://developers.google.com/identity/branding-guidelines