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 …

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

5 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="7a8b3d97-697e-4ce8-b423-eac637e8b407"><ac:parameter ac:name="server">eZ Systems JIRA tracker</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution</ac:parameter><ac:parameter ac:name="maximumIssues">20</ac:parameter><ac:parameter ac:name="jqlQuery">project = EZP AND affectedVersion = "Known Issues Legacy Stack" AND affectedVersion in ( "5.1", "5.2" ) AND (resolution is EMPTY OR resolution != Fixed OR fixVersion != "5.2") ORDER BY priority DESC, created ASC</ac:parameter><ac:parameter ac:name="serverId">841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | RAW | = :">server=eZ Systems JIRA tracker|columns=key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution|maximumIssues=20|jqlQuery=project = EZP AND affectedVersion = "Known Issues Legacy Stack" AND affectedVersion in ( "5.1", "5.2" ) AND (resolution is EMPTY OR resolution != Fixed OR fixVersion != "5.2") ORDER BY priority DESC, created ASC|serverId=841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

Loading …

Key	Summary	T	Created	Updated	Due	Assignee	Reporter	P	Status	Resolution
EZP-20115	eZ Identifier FieldType not supported by Public API		Nov 21, 2012	May 12, 2016		Unassigned	André Rømcke		Backlog	Unresolved
EZP-20486	Cleanup eZ Matrix FieldType repo so it can be made public		Feb 20, 2013	Sep 25, 2014		Unassigned	André Rømcke		Closed	Fixed
EZP-20782	As a 5.x User I expect better info when I lack access to content		Apr 26, 2013	May 27, 2014		Unassigned	Nicolas Lescure		Backlog	Unresolved
EZP-20800	Configure Legacy Storage engine in Symfony service container		May 02, 2013	Jul 13, 2014		Unassigned	Matthieu Sévère		Closed	Fixed
EZP-20898	wrong ezurl behaviour in a legacy template loaded through new stack with ESI		May 21, 2013	Dec 19, 2014		Unassigned	Matthieu Sévère		Closed	Fixed
EZP-20902	Cache is not expired when content is deleted with REST v2 call		May 21, 2013	Aug 19, 2016		Unassigned	Łukasz Serwatka		Closed	Fixed
EZP-22898	Date FieldTypes does not support time beyond 2038		May 21, 2014	Oct 12, 2015		Unassigned	Pedro Resende		Confirmed	Unresolved
EZP-20118	eZ Password Expiry FieldType not supported by Public API		Nov 21, 2012	May 12, 2016		Unassigned	André Rømcke		Backlog	Unresolved
EZP-20112	Some Shop FieldTypes are not supported by Public API		Nov 21, 2012	May 12, 2016		Unassigned	André Rømcke		Backlog	Unresolved

9 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="92cce49b-d287-4459-93f3-af55ea625043"><ac:parameter ac:name="server">eZ Systems JIRA tracker</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution</ac:parameter><ac:parameter ac:name="maximumIssues">20</ac:parameter><ac:parameter ac:name="jqlQuery">project = EZP AND affectedVersion = "Known Issues 5.x Stack" AND affectedVersion in ( "5.1", "5.2" ) AND (resolution is EMPTY OR ( resolution = Fixed AND fixVersion not in ("5.1", "5.2-alpha1", "5.2-beta1", "5.2-rc1","5.2"))) ORDER BY priority DESC, created ASC</ac:parameter><ac:parameter ac:name="serverId">841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | RAW | = :">server=eZ Systems JIRA tracker|columns=key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution|maximumIssues=20|jqlQuery=project = EZP AND affectedVersion = "Known Issues 5.x Stack" AND affectedVersion in ( "5.1", "5.2" ) AND (resolution is EMPTY OR ( resolution = Fixed AND fixVersion not in ("5.1", "5.2-alpha1", "5.2-beta1", "5.2-rc1","5.2"))) ORDER BY priority DESC, created ASC|serverId=841cf523-cc54-30bc-bc5d-89e63192498a</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.