Hello. I can activate BuddyPress Group Email Subscription fine in my dev environment but when I try in my staging and live environments, the admin page reloads with the message, “Plugin could not be activated because it triggered a fatal error”.
Error message:
require(): Failed opening required ‘/code/wp-content/plugins/buddypress-group-email-subscription/vendor/autoload.php’ (include_path=’.:/usr/share/pear:/usr/share/php’)
in include_once called at /code/wp-admin/includes/plugin.php (2389)
in plugin_sandbox_scrape called at /code/wp-admin/includes/plugin.php (675)
in activate_plugin called at /code/wp-admin/plugins.php (60)
My host locks down certain directories in the staging and live environments that are writeable in the dev environment. Here’s what the host’s docs say: “For WordPress sites, /wp-content/uploads is the default location for files. All other locations are considered part of your codebase, and under version control…Extensions that create files within the codebase (e.g., wp-content/plugins/plugin-name/some-other-directory , or /sites/all/modules/module-name/some-other-directory ) incorrectly assume write access that is not granted on the Live and Test environments…The best solution is to communicate with the maintainer of the module, plugin, or custom code/configuration and request that hard-coded, nonstandard paths be fixed. Alternatively, you can create a symbolic link (symlink) as a workaround to avoid failures on Test and Live.”
Is the symlink my best option here? What file(s) are the plugin trying to write to or create, and where? Thanks for any guidance you can provide.
The page I need help with: [ log in to see the link]
