I am trying to:
symlink `plugins/wp-views` via a deployment system hidden link
Goal:
`plugins $ ln -s ~/deploy/plugins/wp-views/current wp-views`
...where:
`current` is also a symlink to a timestamped directory like `~/deploy/plugins/wp-views/releases/20181230.141522-leho`
Link to a page where the issue can be seen:
gutenberg editor screen
I expected to see:
`TOOLSET_COMMON_PATH` and `WPV_*` constants resolve correctly
Instead, I got:
JS assets fails to load 404, because `__FILE__`-based constants resolution can't deal with symlinks. Result `hidden link.../wp-content/plugins/20181230.141522-leho/.../some-asset.min.js` cannot be operated with.
You should avoid resolving absolute paths, if you want to stay relevant with the widest possible developer audience.
Related issues:
Probably https://toolset.com/forums/topic/javascript-urls-wrong-if-theme-dir-is-a-symlink-and-types-is-embedded/
Hi,
There isn't such a built-in feature to use symlinked with Views plugin, I suggest you add a feature request for it:
https://toolset.com/forums/forum/professional-support/#feature-request
Currently, you will need to follow our document to install Views plugin:
https://toolset.com/faq/how-to-install-and-register-toolset/
> There isn't such a built-in feature to use symlinked with Views plugin, I suggest you add a feature request for it:
It would be nice if support staff would take care of such busywork, but I filed the feature request myself now.
Our workflow requires to fill the "feature-request" form, sorry if there is any inconvenience .
