It seems that this plugin only works with typical setups. Advanced setups don’t work due to assumptions made in the code. The function:
get_files_includesis an example. The plugin uses:
ABSPATH . WPINCwhich is a bad assumption. I have wordpress installed in a separate directory and use a symlink to include it in the project. This check will break on projects that are not using WPINC in their webroot. Is this intentional to force paid support? Seems like a very serious flaw in logic.
Basically, I cannot upload any of the includes folder assets due to this bug.
Also, how can I not have all my items be PUBLIC???? I want it to be private by default. I have roles in use so I do not want direct access to the bucket… another bad design…
- The topic ‘BUG wp-includes pathing is relative, should be absolute’ is closed to new replies.