Currently, Linkit seems to include the base_path to the Drupal install in the urls it generates.
This renders a great combination of Linkit with Pathologic useless?
Not only that, but we develop our projects in different environment which all have different base paths. Which creates even a larger problem, since when our projects are about to be launched and deployed into production, we use a deeper base_path (/base/path/to/drupal/in/dev/) and the production mostly has a empty base_path (/) which breaks all the links created by linkit.
I've read through the issue queue and noticed there has been some discussions possibly related to this issue, though I never found a true resolve for the above problems and am expecting there has never been a true fix.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | 2894594.linkit.Exclude-Drupal-base-path-add-base_path_14.patch | 1.04 KB | gigimaor |
| #7 | 2894594.linkit.Exclude-Drupal-base-path.patch | 802 bytes | au_dave |
| #6 | 2894594-6.linkit.Exclude-Drupal-base-path.patch | 802 bytes | pingers |
| #4 | 2894594-4.linkit.Exclude-Drupal-base-path.patch | 641 bytes | singularo |
Comments
Comment #2
nvakenComment #3
nvakenComment #4
singularoCame across this same issue, attached patch seems to resolve it.
Comment #5
anonThe patch in #4 will not work.
In 5.x the url returned by the match should always be a canonical url (node/123).
The url is not used anyway IF you have the Linkit filter enabled.
If the filter is not enabled, the links would still link to the correct resource.
However if the filter is enabled Linkit will read some "data-attrs" from the a-tag and transform it to an alias.
This issue is thereby a 4.x issue, not a 5.x issue.
Comment #6
pingers commentedRe-roll for 5.x
Comment #7
au_dave commentedReroll so that it still works on Drupal 9.
Comment #8
liam morlandComment #9
joseph.olstadthis pathologic specific behaviour should be optional, a settings option in linkit or else a if module exists pathologic then modify behavior accordingly
Comment #10
mibfire commentedThis patch just puts url alias instead of raw path. This is not good...
Comment #11
mark_fullmerFor some time now, as indicated by the Linkit project page, the 8.x-4.x branch of Linkit is not undergoing active development.
To help the maintainers of the Linkit module better steward tasks under active development, I'm going to mark this issue as closed (wontfix). Sites using 8.x-4.x can certainly continue to do so, but should make plans for updating to the latest supported version of Linkit.
Even better: Drupal core will soon provide link autocomplete suggestions in CKEditor similar to what this module does. Sites using or considering using Linkit should follow this core issue to evaluate whether they can use the core solution instead of Linkit. See feature differences below to compare what Linkit includes that will not initially be in Drupal core.
If this issue relates to a problem or feature request that is applicable to the latest supported version of Linkit, please create a new issue, associated with that branch, describing the bug or enhancement.
For participation and information in Linkit's roadmap, see #3345480: LinkIt Release Roadmap and Issue Prioritization.
Thanks, community, for you collaboration and consideration!
Comment #12
gigimaorDrupal 10.3.1
In case a website has a subdirectory to its path (base_path()), we would like to include it in the path
https://www.website.com/subdirectory/...
Comment #13
gigimaorComment #14
gigimaorComment #15
gigimaor