Advanced search on Audit portlet has duplicate ID's

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, 7.1.X, 7.2.X, 7.3.X, Master
• Fix Version/s: 7.0.0 DXP FP100, 7.0.X, 7.1.10 DXP FP23, 7.1.10.6 SP6, 7.1.X, 7.2.10 DXP FP13, 7.2.X, 7.3.7 CE GA8, 7.3.10 DXP FP2, 7.3.X, 7.4.1 CE GA2, Master
• Component/s: Portal Services > Auditing
• Labels:
  • 7.4-known-issues
  • ee-ts
  • liferay-dxp-71-sp6
  • liferay-fixpack-de-100-7010
  • liferay-fixpack-dxp-13-7210
  • liferay-fixpack-dxp-2-7310
  • liferay-fixpack-dxp-23-7110
  • liferay-ga1-ce-740
• Branch Version/s:
  7.3.x, 7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 4
• Git Pull Request: https://github.com/liferay-appsec/liferay-portal/pull/344

Steps to reproduce
1) in portal-ext, set:
audit.message.com.liferay.portal.kernel.model.Layout.VIEW=true
setup.wizard.enabled=false
2) startup liferay
3) login as default admin
4) generate 6 audit events
(eg. by visiting localhost:8080 6 times in the authenticated session)
5) visit Audit portlet and set its pagination to 5 (control panel -> Security -> Audit)
6) open advanced search
7) left click on the first date input -> inspect
8) see id="com_liferay_portal_security_audit_web_portlet_AuditPortlet" on the input field
9) search for the id with "com_liferay_portal_security_audit_web_portlet_AuditPortlet"

Actual result: both of the input fields have the same id
Expected: The id is not duplicated

Steps to Reproduce 2 - JS Warnings

1. Follow steps 1-5 above
2. Open developer tools in browser
3. Look at console tab

Actual result: warnings are displayed regarding the DatePicker and TimePicker components being registered twice

• Component with id "_com_liferay_portal_security_audit_web_portlet_AuditPortlet_DatePicker" is being registered twice. This can lead to unexpected behaviour in the "Liferay.component" and "Liferay.componentReady" APIs, as well as in the "*:registered" events.
  
  Component with id "_com_liferay_portal_security_audit_web_portlet_AuditPortlet_TimePicker" is being registered twice. This can lead to unexpected behaviour in the "Liferay.component" and "Liferay.componentReady" APIs, as well as in the "*:registered" events.
  

Expected result: warnings regarding the DatePicker and TimePicker components being registered twice are not thrown

Reproduced on:
7.0 (de-91)
7.0.x private, commit 1d461a26fb1906d5fdb2333484c753580b258d58
master @9275a579449189691160bf2dbf5786fd64d1afab