Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.0.7, 4.1.4, 4.2.0
-
None
-
Tested in 4.0.0, 4.1.3, 4.2.0 and 4.3 trunk
Description
Given a URL like this: /content/view/full/(valid node id)(misc string)
eZ Publish will display the page as if /content/view/full/(valid node id) had been accessed, but will store the view cache file based on the misc string.
Steps to reproduce
- Make sure you have read access to node 2
- Access /content/view/full/2abcdefg
- Confirm that node 2 is displayed normally (expected: should display a "no such node" error)
- Confirm that var(/site_prefix)/cache/content/(siteaccess)/2/a/b/c/d/e/ is created, and the view cache is stored there as 2abcdefg-(md5 string).cache (expected: nothing should be created)