Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-23051

URI based matchers that implement URILexer do not account for basePath

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: High High
    • Resolution: Unresolved
    • Affects Version/s: 2014.01
    • Fix Version/s: 2014.03, 5.3
    • Component/s: Platform stack
    • Labels:
      None

      Description

      URIElement->analyseLink() does not take the basePath into consideration nor can it as it uses it uses SimplifiedRequest that does not support basePath.

      This looks like it would be the same for the other URI matcher that implement the URILexer.

      This causes the wrong urls to be generated if your installation is in a subdirectory like http://example.com/subdirectory/web/siteaccess

        Issue Links

          Activity

          Hide
          Jérôme Vieilledent (Inactive) added a comment -

          Hi Douglas

          AFAICT, it's not up to the matcher to do such thing, but to the URLGenerator. This is the case as of 2014.03 / 5.3. I guess you're using an older version?

          Show
          Jérôme Vieilledent (Inactive) added a comment - Hi Douglas AFAICT, it's not up to the matcher to do such thing, but to the URLGenerator . This is the case as of 2014.03 / 5.3. I guess you're using an older version?
          Show
          Jérôme Vieilledent (Inactive) added a comment - This has probably been fixed in https://github.com/ezsystems/ezpublish-kernel/commit/3921cb5d94b226225b743b6f12e0edc61053e253 (commit related to EZP-20305 ).
          Hide
          Jérôme Vieilledent (Inactive) added a comment -

          Can you please confirm Douglas?
          Thanks

          Show
          Jérôme Vieilledent (Inactive) added a comment - Can you please confirm Douglas? Thanks
          Hide
          Douglas Hammond added a comment -

          I still have this issue. I'm using latest dev master. I have to use a custom URIElement matcher that has access to the httpRequest and corrects analyseLink to take the baseUrl into account.

          You can see this at https://gist.github.com/wizhippo/ad216e0867fff7490a97

          Show
          Douglas Hammond added a comment - I still have this issue. I'm using latest dev master. I have to use a custom URIElement matcher that has access to the httpRequest and corrects analyseLink to take the baseUrl into account. You can see this at https://gist.github.com/wizhippo/ad216e0867fff7490a97

            People

            • Assignee:
              Unassigned
              Reporter:
              Douglas Hammond
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: