Plugin Paths Issue

I am using a plugin which has several instances where it is using a hardcoded path rather than using the WP function to find a path. The problem here is that it’s referring to wp-content but I’ve changed the WP_CONTENT_FOLDERNAME setting in the wp-config file (there was a past requirement to do that).

Anyways, is there a way to achieve this without updating the plugin codebase itself (i.e. allow it to be upgradable in the future). I guess this goes with the whole idea of extending a plugin without having to edit the codebase.

Related posts

Leave a Reply

3 comments

  1. The plugin developer might include the changes into the core plugin if you submit the changes or offer a patch. You can’t be the only one out there with the issue.

  2. Not that I know of, this is the very reason why hardcoding this into a theme or plugin is bad. I think your best option is to fork it using git/hg then merge any new changes yourself, which is not always practical.