Rename AccountingZuite_CommonTemplate to ERP5Site_viewAccountingZuiteCommonTemplate

Rename AccountingZuite_createAccountingTransactionList to AccountingTransactionModule_createAccountingTransactionList

Rename AccountingZuite_createAccountingTransactionListSalesAndPayments to AccountingTransactionModule_createAccountingTransactionListSalesAndPayments

Rename AccountingZuite_createAccountingTransactionListWithPersons to AccountingTransactionModule_createAccountingTransactionListWithPersons

Rename AccountingZuite_createDocument to AccountingTransactionModule_createAccountingTestDocument

Rename AccountingZuite_createReportDataset to AccountingTransactionModule_createAccountingTestReportDataset

Rename AccountingZuite_createReportJournalDataset to AccountingTransactionModule_createAccountingTestReportJournalDataset

Rename AccountingZuite_deleteAccountingTransactionTemplate to ERP5Site_deleteAccountingTransactionTemplate

Rename AccountingZuite_initializeAccountingTransactionReportTest to AccountingTransactionModule_initializeAccountingTransactionReportTest

Rename AccountingZuite_initializeAccountingTransactionTemplateTest to AccountingTransactionModule_initializeAccountingTransactionTemplateTest

Rename AccountingZuite_markChanged to AccountingTransactionModule_markAccountingTestDataChanged

Rename AccountingZuite_reportMacros to Zuite_viewAccountingTestReportMacros

Rename AccountingZuite_reset to ERP5Site_resetConfigurationForAccountingTest

Rename AccountingZuite_setAccountReferencePreference to PreferenceTool_setAccountingTestAccountReferencePreference

Rename AccountingZuite_setDocumentSectionPreference to PreferenceTool_setAccountingTestDocumentSectionPreference

Rename AccountingZuite_unsetDocumentSectionPreference to PreferenceTool_resetAccountingTestDocumentSectionPreference

erp5_project does not depend on erp5_budget, so instanciating project
cell fail unless erp5_budget is installed.

Project Cell are not used by default, so it's still a bit unclear, but
with erp5_budget we can directly define budgets by project / project
lines in a more flexible (but also more complex).

Project Line uses OrderLine, so it's consistent to use OrderCell for Project Cell.


/reviewed-on nexedi/erp5!980

erp5_trade_ja: 軽減税率8% tax line in summary must always be present (official specification) but is not used in Nexedi so hardcode it.

erp5_trade_ja: AttributeError was raised when default_image (to display logo at the top left) was not defined.

- views/actions meant for officejs should use "object_jio_x" categories to avoid conflicts with erp5js
- using object_jio_search instead of common object_jio_view because the base form for rendering depends on the category (form_list, form_dialog, form_view, etc)
- changes are also in bts officejs_jquery_app and officejs_ooffice

- do the calculations while officejs router set settings

speedup

 - run `testXHTML` on business templates "one by one"
 - fix all the problems with the currently tested business templates
 - because `erp5_ingestion` was containing some tests skin folder depending on other business templates and because I did not want to add dependencies to `erp5_ingestion` I moved the tests in `erp5_ingestion_test`.

/reviewed-on !989

Some document subobjects have a workflow, and so, can be only be deleted from some state
If the listbox does not display them, do not add the state filter parameter

This skeleton became cloudooo several years ago and we don't need this
here anymore.

/reviewed-on nexedi/erp5!966

Note that Set type setter still keeps the default one if exists.

/reviewed-on nexedi/erp5!862

This property sheet was missing, but test passed because both the
setSourceReference and getSourceReference were acquired

/reviewed-on !998

/reviewed-on !999

This will allow to find problems when only business templates and their
dependencies are installed. When we run testXHTML with all business
template installed we don't see problems that may happen only when some
business templates are not installed.

pylint complained about indentation

this was removed in 2138aee5

This bt has too many coding style problems for now

  'ticket_view_selection'
	'Tickect_viewRelatedRecordList/listbox': set(['erp5_hr_request'])
	'Ticket_view/listbox': set(['erp5_crm'])

  'web_page_module_view_web_page_list_selection'
	'DocumentModule_viewDocumentListAsJioForOofficeSpreadsheetEditor/listbox': set(['erp5_ooffice_spreadsheet_editor'])
	'DocumentModule_viewDocumentListAsJioForOofficePresentationEditor/listbox': set(['erp5_ooffice_presentation_editor'])
	'WebPageModule_viewWebPageList/listbox': set(['erp5_web'])
	'DocumentModule_viewDocumentListAsJioForOofficeTextEditor/listbox': set(['erp5_ooffice_text_editor'])
	'WebPageModule_viewWebTableListAsJioForWebTableEditor/listbox': set(['erp5_web_table_editor'])

  'image_selection'
	'ImageModule_viewImageList/listbox': set(['erp5_dms'])
	'ImageModule_viewImageListAsJioForImageEditor/listbox': set(['erp5_image_editor'])
  'web_page_module_view_web_page_list_selection'
	'DocumentModule_viewDocumentListAsJioForOofficeSpreadsheetEditor/listbox': set(['erp5_ooffice_spreadsheet_editor'])
	'DocumentModule_viewDocumentListAsJioForOofficePresentationEditor/listbox': set(['erp5_ooffice_presentation_editor'])
	'WebPageModule_viewWebPageList/listbox': set(['erp5_web'])
	'DocumentModule_viewDocumentListAsJioForOofficeTextEditor/listbox': set(['erp5_ooffice_text_editor'])
	'WebPageModule_viewWebTableListAsJioForWebTableEditor/listbox': set(['erp5_web_table_editor'])

There are no testVifib (at least not in nexedi/erp5 repository) and
there is only one testLive that there is no reason to skip.

This test never ran because we skip testLive*

erp5_ingestion contained a skin folder for tests, with some proxy fields depending on erp5_web.
There was a proper test dependency to erp5_web, but in static analysis check we now check the skin folders, so it's no longer allowed to have some skin folder that are broken without test dependencies but not supposed to be used outside of tests.

Since this was using proxy fields from erp5_crm, add dependency on CRM.
Update to the new name of CRM field library.

nuvalidator complains that:
  Bad value “true” for attribute “autoplay” on element “video”

This could probably be switched to VideoField now.

Unlike other attributes managed in video field, preload [1] is not a
boolean attribute, so setting preload="preload" was invalid HTML5.

On the field, we can only configure video_preload as a boolean
attribute, setting preload="auto" when true and not setting preload when
False seems the closest meaning of True/False.

[1] https://html.spec.whatwg.org/multipage/media.html#attr-media-preload

IntegrationSite_view/my_source_payment is a proxyfield to a field in
erp5_accounting.

It uses proxy fields from erp5_crm

   'base_view_document_selection'
	'Base_viewDocumentList/listbox': set(['erp5_core'])
	'Project_viewDocumentList/listbox': set(['erp5_web_project'])
   'project_module_selection'
	'ProjectModule_viewProjectList/listbox': set(['erp5_project'])
	'ProjectModule_viewProjectManagementList/listbox': set(['erp5_web_project'])

These selection names were already used in other business templates:

   'web_page_module_view_web_page_list_selection'
	'WebPageModule_viewWebPageListAsJioForCodemirror/listbox': set(['erp5_officejs_codemirror'])
	'WebPageModule_viewWebPageListAsJioForTextEditor/listbox': set(['erp5_text_editor'])
	'WebPageModule_viewWebPageList/listbox': set(['erp5_web'])
	'DocumentModule_viewDocumentListAsJioForPdfViewer/listbox': set(['erp5_officejs_pdf_viewer'])
   'image_selection'
	'WebPageModule_viewWebPageListAsJioForSvgEditor/listbox': set(['erp5_officejs_svg_editor'])
	'ImageModule_viewImageList/listbox': set(['erp5_dms'])