You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to modernise some of our codebase by vendoring option-tree with composer. The composer.json file is located at the root of the project (e.g. same dir as wp-config.php).
There are a couple of issues:
Option tree does not seem to be getting registered with the autoloader.php from version 2.7.0 OptionTree version 2.7.0 #695. I can get round this by including vendor/valendesigns/option-tree/ot-loader.php
I am getting issues with the admin resources including the directory and not getting loaded correctly (this also happens in 2.6.0): [domain]/wp-content/plugins/nas/content/live/[installname]/vendor/valendesigns/option-tree/assets/js/ot-admin.js?ver=2.7.3
As far as I can tell the 2nd issue is because OT expects it to be in a specific theme or plugin directory, not a root vendor directory. If this is the case, I'm not sure how we can use composer.json without copying the files?
The text was updated successfully, but these errors were encountered:
I am trying to modernise some of our codebase by vendoring option-tree with composer. The composer.json file is located at the root of the project (e.g. same dir as wp-config.php).
There are a couple of issues:
vendor/valendesigns/option-tree/ot-loader.php
[domain]/wp-content/plugins/nas/content/live/[installname]/vendor/valendesigns/option-tree/assets/js/ot-admin.js?ver=2.7.3
As far as I can tell the 2nd issue is because OT expects it to be in a specific theme or plugin directory, not a root vendor directory. If this is the case, I'm not sure how we can use composer.json without copying the files?
The text was updated successfully, but these errors were encountered: