[
http://www.jahia.org/jira/browse/JAHIA-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Papez resolved JAHIA-2763.
-----------------------------------
Resolution: Fixed
Check added, warning on deprecated non-container fields is logged. If none are
used, some methods and SQL query parts are not used.
Index in jahia_fields_data had to be added due to performance issue in the
select, which determines existing non-container fields.
> Call some noncontainer-field methods only if deprecated noncontainer-fields
> are used
> ------------------------------------------------------------------------------------
>
> Key: JAHIA-2763
> URL: http://www.jahia.org/jira/browse/JAHIA-2763
> Project: Jahia Content Management Server
> Issue Type: Improvement
> Reporter: Benjamin Papez
> Assignee: Benjamin Papez
> Fix For: 5.0 SP4
>
>
> On Jahia startup we could check, whether the site(s) are using fields without
> containers (deprecated since Jahia 5). If not, then we do not need to try
> retrieving them in:
> ContentPage.getChilds
> ContentPageKey.getChilds
> PageBean.getFields
> inside ContentPage.checkAccess methods
> JahiaPageBaseService.clonePage
> JahiaFieldBaseService.areNonContainerFieldsValidForActivation
> As soon as JahiaFieldSet.declareField method is called and the startup check
> retrieved no fields-without-container objects, the status to disable the
> checks should be set to enable them again, but we should write a WARNING in
> the log, that this is going to be REALLY deprecated in the next major release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
