Global navigation

 •  Documentation Center
 •  eZ Studio & eZ Platform
   •  User Manual
   •  Technical Manual
   •  Glossary
 •  eZ Publish 4.x / legacy

 
eZ Publish (5.x)

eZ Publish 5.x | For eZ Platform & eZ Studio topics see Technical manual and User manual, for eZ Publish 4.x and Legacy topics see eZ Publish legacy

Versions Compared

Old Version 3

changes.mady.by.user André Rømcke

Saved on

compared with

New Version Current

changes.mady.by.user André Rømcke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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

JIRA
servereZ Systems JIRA tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = 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
serverId841cf523-cc54-30bc-bc5d-89e63192498a

 

JIRA
servereZ Systems JIRA tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = 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
serverId841cf523-cc54-30bc-bc5d-89e63192498a

 

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.