The following two lists of issues are for legacy (4.x) and Symfony (5.x) stack respectively as eZ Publish 5.x contains both.
The bug tracker for eZ Publish, from which these lists are extracted, is available at https://jira.ez.no

Loading …

Legacy kernel issues (5 issues)

T	Key	Summary	Assignee	Reporter	P	Status	Resolution	Created	Updated	Due
	EZP-22309	5.x kernel & legacy kernel does not share db connection	Unassigned	André Rømcke		Closed	Won't Fix	Feb 06, 2014	Feb 06, 2014
	EZP-22898	Date FieldTypes does not support time beyond 2038	Unassigned	Pedro Resende		Confirmed	Unresolved	May 21, 2014	Oct 12, 2015
	EZP-19541	Login with DebugByUser enabled is not possible in ezp500	Unassigned	João Pingo		Closed	Won't Fix	Jul 23, 2012	Jan 26, 2016
	EZP-21744	Documentation: twig templates cannot be previewed in back end	Unassigned	Joaquim Cavalleri		Closed	Fixed	Oct 14, 2013	Feb 06, 2014
	EZP-22112	Link to change password should be displayed based on permissions	Unassigned	Paulo Bras		Open	Unresolved	Dec 19, 2013	Jun 03, 2014

5 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="3e789cd5-bcb7-4ebe-bbdc-308f0e865133"><ac:parameter ac:name="cache">off</ac:parameter><ac:parameter ac:name="anonymous">true</ac:parameter><ac:parameter ac:name="title">Legacy kernel issues</ac:parameter><ac:parameter ac:name="url">https://jira.ez.no/sr/jira.issueviews:searchrequest-xml/12303/SearchRequest-12303.xml?tempMax=1000</ac:parameter><ac:parameter ac:name=": = | RAW | = :">cache=off|anonymous=true|title=Legacy kernel issues|url=https://jira.ez.no/sr/jira.issueviews:searchrequest-xml/12303/SearchRequest-12303.xml?tempMax=1000</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

Loading …

5.x kernel (Public API, REST API v2 &amp; Symfony stack) issues (20 issues)

T	Key	Summary	Assignee	Reporter	P	Status	Resolution	Created	Updated	Due
	EZP-20111	eZ Commentes FieldType is not supported by Public API	Unassigned	André Rømcke		Closed	Won't Fix	Nov 21, 2012	Nov 07, 2013
	EZP-19766	Missing base templates blocks and config for demo design supported fields	Unassigned	Bertrand Dunogier		Closed	Obsolete	Jul 16, 2012	Jan 29, 2015
	EZP-20115	eZ Identifier FieldType not supported by Public API	Unassigned	André Rømcke		Backlog	Unresolved	Nov 21, 2012	May 12, 2016
	EZP-20116	eZ SubtreeSubscription FieldType not supported by Public API	Unassigned	André Rømcke		Closed	Won't Fix	Nov 21, 2012	May 12, 2016
	EZP-20196	Running ezpublish/console as root user will make install fail	Unassigned	Gaetano Giunta		Closed	Obsolete	Dec 03, 2012	Mar 03, 2015
	EZP-20197	eZ5 Setup generated config not working with empty MySQL password	Unassigned	Jérôme Cohonner		Closed	Obsolete	Dec 03, 2012	Mar 03, 2015
	EZP-20486	Cleanup eZ Matrix FieldType repo so it can be made public	Unassigned	André Rømcke		Closed	Fixed	Feb 20, 2013	Sep 25, 2014
	EZP-20579	REST login (create session resource) is not protected against CSRF attack	Unassigned	Petar Spanja		Closed	Obsolete	Mar 18, 2013	Mar 03, 2015
	EZP-20782	As a 5.x User I expect better info when I lack access to content	Unassigned	Nicolas Lescure		Backlog	Unresolved	Apr 26, 2013	May 27, 2014
	EZP-20800	Configure Legacy Storage engine in Symfony service container	Unassigned	Matthieu Sévère		Closed	Fixed	May 02, 2013	Jul 13, 2014
	EZP-20898	wrong ezurl behaviour in a legacy template loaded through new stack with ESI	Unassigned	Matthieu Sévère		Closed	Fixed	May 21, 2013	Dec 19, 2014
	EZP-20902	Cache is not expired when content is deleted with REST v2 call	Unassigned	Łukasz Serwatka		Closed	Fixed	May 21, 2013	Aug 19, 2016
	EZP-21292	Missing API Depth Criterion	Unassigned	André Rømcke		Closed	Duplicate	Jul 18, 2013	Nov 07, 2013
	EZP-21495	(Persistence) cache does not support multi repository setup	Unassigned	André Rømcke		Closed	Fixed	Sep 02, 2013	Oct 07, 2013
	EZP-21501	Support object state group limitation in API	Unassigned	Filipe Dobreira		Closed	Fixed	Sep 03, 2013	Oct 03, 2013
	EZP-21914	New stack DB link must be reset in asynchronous publishing daemon	Unassigned	Bertrand Dunogier		Closed	Fixed	Nov 07, 2013	Nov 14, 2013
	EZP-21950	Persistence/Stash Filesystem cache does not work on Windows (path length)	Unassigned	André Rømcke		Closed	Duplicate	Nov 14, 2013	Feb 20, 2014
	EZP-22338	Hidden content returned from REST API	Unassigned	André Rømcke		Closed	Won't Fix	Feb 12, 2014	Jan 06, 2015
	EZP-22898	Date FieldTypes does not support time beyond 2038	Unassigned	Pedro Resende		Confirmed	Unresolved	May 21, 2014	Oct 12, 2015
	EZP-19664	(eZ Find) Autocomplete is not working on eZ Demo frontend	Unassigned	Vidar Langseid		Closed	Obsolete	Sep 25, 2012	Mar 03, 2015

Showing 20 out of 25 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="b5ff7be6-ed14-4fe4-b002-608d6017c321"><ac:parameter ac:name="cache">off</ac:parameter><ac:parameter ac:name="anonymous">true</ac:parameter><ac:parameter ac:name="title">5.x kernel (Public API, REST API v2 &amp; Symfony stack) issues</ac:parameter><ac:parameter ac:name="url">https://jira.ez.no/sr/jira.issueviews:searchrequest-xml/12304/SearchRequest-12304.xml?tempMax=1000</ac:parameter><ac:parameter ac:name=": = | RAW | = :">cache=off|anonymous=true|title=5.x kernel (Public API, REST API v2 &amp; Symfony stack) issues|url=https://jira.ez.no/sr/jira.issueviews:searchrequest-xml/12304/SearchRequest-12304.xml?tempMax=1000</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

Known limitation

First level folders or other container objects in your content structure can't have the same name as the existing siteaccesses if you configured your site to use URL access method.
Considering an existing "ezflow_site" siteaccess exists, if you create a folder with the same name and try to access it using http://<your_site>/ezflow_site you will be redirected to the siteaccess instead on accessing your "ezflow_site" folder.
This is actually a known limitation of the URI siteaccess matching.

If you need to use first level folders or other container objects with the same name as any of your siteaccesses we suggest you to use hostname matching instead.
For more details on configuring hostname matching, please check the Siteaccess Matching documentation.