Closed (fixed)
Project:
Extended Path Aliases
Version:
8.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Apr 2017 at 13:47 UTC
Updated:
19 Nov 2018 at 15:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
garnett2125 commentedComment #3
kala4ekThe patch does not work for me.
$source = $this->aliasManager->getPathByAlias($candidate_alias)$source will always contains smth. It may be source path, if it exist or it may be alias. See description of getPathByAlias method.
I rewrite the path and it works for me.
Comment #4
imyaro commentedHello,
Guys, thanks for your patches, but it isn't work if we have, for example, one node that has path "foo" and another "foo/bar"
In this way node with alias "foo" will be found and URL for second one will be
/node/1/bar(instead of the/node/2)I have changed a search "direction" it works better now.
Comment #5
martins.bertins commentedFound a scenario where the processInbound() function returned incorrect path for standard taxonomy term path taxonomy/term/{taxonomy_term} (this might apply for any entity). Added a fix for this.
Also the processOutbound() function must take into account language code when looking for path alias.
Comment #6
martins.bertins commentedAdded validation for path.
Comment #8
adriancidThanks @fellows for the patch
Comment #9
adriancidComment #11
okin commentedThe validation of the path should validate the path regardless the current user has access to it or not. Otherwise a not found is triggered and not an access denied.
\Drupal::service('path.validator')->getUrlIfValidWithoutAccessCheck($return_path)
Comment #12
adriancid@okin can you provide a patch for this?
Comment #13
okin commentedHere it is
Comment #14
adriancidThank @okin the patch was applied it should be shown here in the next minutes I think.