Did you install this from GitHub or from the WordPress directory? It looks like the composer library for logging is not installed, which suggests maybe you installed from GitHub?
If you’re installing from GitHub, see the setup documentation here: https://github.com/MinnPost/object-sync-for-salesforce/blob/master/docs/initial-setup.md, and check the install for developers section. You can certainly use composer to install the library.
Actually, I installed from the WordPress directory.
After my first message, I realized that I am able to activate the plugin in my hosting provider’s dev environment (Pantheon.io for reference). The error is occurring when I activate on, an identical, test environment.
I am reaching out to my hosting provider for additional support, but if you have thoughts I will share with them.
Hm. I do think the issue is the composer library not being present, although the file is certainly present in the WordPress directory (here it is). You might could just try deleting the plugin and installing it again.
If it doesn’t work re-installing the plugin, you might try a couple other things:
1. Download it from the WP directory manually. See if it includes the file. Better yet, if you can run it on a local WordPress install, but that might not be necessary.
1a. If the file is there, try uploading whole plugin directory to the Pantheon server via FTP or whatever they use.
2. If the file is still missing for some reason, you could try using composer with those GitHub instructions to install it. You could try this on a local WordPress install, or on Pantheon itself.
2a. If you can get it all installed from source, basically, you could then either upload the directory via FTP, or it would already be there via Pantheon.
My expectation (though I’m not positive) is that all of the composer managed files are missing from your download for some reason (there aren’t that many, but there’s more than one) and the solution will involve getting all of those files back somehow.
I think the ideal would just be reinstalling the plugin from the WP directory, but I’m not familiar enough with Pantheon to know if that would be successful.
Issue seems to be coming from a couple gitignore files here: /object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing/.gitignore and here: /object-sync-for-salesforce/vendor/developerforce/force.com-toolkit-for-php/.gitignore
The version of the plugin I downloaded from WP.org had the missing files, but the version I pulled from my dev environment (added via WP admin) did not have the files. When moving the plugin from dev to test the same thing was happening.
After removing the gitignores/git directories within the vendor directories the problem went away.
These are added by the composer install process, which itself runs every time the plugin is added to the WordPress directory.
I think it’s interesting that it worked when you downloaded it manually, but not via the admin. I don’t know why that would be the case, but I haven’t seen it happen installing via admin in the past. Without a way to reproduce that, I think I’d assume it was a fluke, unless it is specifically related to something Pantheon itself does (which is certainly possible as well).
The files were present when I added the plugin via the admin. Issue occurred when moving between environments after that. Pulling the changes to my local or when moving to test resulted in the missing files.
Thanks for your help with this. Hope I don’t need too much more handholding to get everything set up.
That makes sense. I’d be interested to hear if Pantheon has any response to that which we could act on.
Not sure if this helps (I’m new to composer), but Pantheon support had this note:
I know when adding modules to Drupal 8 sites using composer, we can add the “--prefer-dist” flag to the composer command to avoid installing any submodules (.git folders). I wonder if he can do something similar when adding the plugin to WordPress?
-
This reply was modified 8 years, 3 months ago by
joepahl.
I’ll add that to the plugin’s deploy script, and see what it does on the next release. From what I’ve seen when I install the plugin from admin, there are no .git directories, but I’m no composer expert, and this seems like a helpful/definitely not harmful thing to add to the script. Thanks.
