Alternative plugin directory issues

  • Resolved dodedodo33

    (@dodedodo33)


    7 years, 6 months ago

    Hi guys,

    In a recent change on our wordpress installation by our hoster we experienced some issues with the events calendar. Now our hoster is a bit hipster in technologies sometimes and quite focussed on security. He relocated our plugins directory to <site_root>/addons. Now this works fine for most plugins, except for this one.

    It seems that resource url’s are loaded by resolving the path and a WP_CONTENT_DIR / content_url string replacement. This works fine when using a default wordpress installation. But not when your plugins directory is not inside the content directory. I’ve tried changing the url replacement to work with WP_PLUGIN_DIR and plugins_url() but could not really get it to work reliably (I’ve only changed the tribe_resource_url() method).

    Is there a specific reason why the url’s are resolved this way instead of using plugins_url() in some way? The method that is used now expects the plugin to be installed inside the wp content directory, which might not be the case in every wordpress installation.

    For now we have reset the locations to wordpress defaults. Is there a way to fix this in a future release?

Viewing 1 replies (of 1 total)
  • Plugin Contributor Victor Zarranz

    (@vicskf)

    Hi there!

    I’m sorry for the delay in getting back to you.

    We had a bug related to the WP_PLUGIN_DIR but was already fixed in one of our latest maintenance release.

    Please make sure you update to the latest version of our plugin and see if it works for you.

    Let us know if you have any other questions or issues!

    Best,
    Victor

Viewing 1 replies (of 1 total)
  • The topic ‘Alternative plugin directory issues’ is closed to new replies.