Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bedrock autoloader edge case #1022

Closed
5 of 6 tasks
slackday opened this issue Oct 5, 2018 · 1 comment
Closed
5 of 6 tasks

Bedrock autoloader edge case #1022

slackday opened this issue Oct 5, 2018 · 1 comment

Comments

@slackday
Copy link
Contributor

slackday commented Oct 5, 2018


What is the current behavior?

This is a case that has hit me in the head a couple of times where MU-plugins are not loaded as expected.

What is the expected or desired behavior?

Mu-plugins are not loaded on remote server

I'm not entirely sure how to replicate this reliably. But the workflow goes roughly like this.

  1. Setup a new site for local development.
  2. Install plugins (affected plugin in my case is ACF).
  3. Develop site / Update plugins etc
  4. Move ACF from plugin to mu-plugin
  5. Finish site
  6. Move to staging/production server and deploy site.
  7. Move development DB to remote server.

Bug report

(delete this section if not applicable)

Please provide steps to reproduce, including full log output:

X

Please describe your local environment:

Ansible version: 2.5.0

OS: 10.12.6

Vagrant version: 2.0.2

Where did the bug happen? Development or remote servers?

Remote server


Please provide use cases for changing the current behavior:

On the local DB

SELECT option_value from wp_options WHERE option_name = 'bedrock_autoloader';

a:2:{s:7:"plugins";a:1:{s:34:"advanced-custom-fields-pro/acf.php";a:11:{s:4:"Name";s:26:"Advanced Custom Fields PRO";s:9:"PluginURI";s:37:"https://www.advancedcustomfields.com/";s:7:"Version";s:5:"5.7.3";s:11:"Description";s:69:"Customise WordPress with powerful, professional and intuitive fields.";s:6:"Author";s:13:"Elliot Condon";s:9:"AuthorURI";s:28:"http://www.elliotcondon.com/";s:10:"TextDomain";s:3:"acf";s:10:"DomainPath";s:5:"/lang";s:7:"Network";b:0;s:5:"Title";s:26:"Advanced Custom Fields PRO";s:10:"AuthorName";s:13:"Elliot Condon";}}s:5:"count";i:1;}

After deploying site and exporting DB to remove server I got error that ACF was not active

SELECT option_value from wp_options WHERE option_name = 'bedrock_autoloader';

a:2:{s:7:"plugins";a:0:{}s:5:"count";i:0;}
@slackday
Copy link
Contributor Author

slackday commented Oct 5, 2018

Sorry this is a bedrock issue and I was going to make a PR fixing it when I realized I created the issue in wrong project...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant