search

cloudverve / wordpress-cloud-media-offloader-plugin

A simple plugin that allows you to serve your WordPress Media Library files from the Backblaze B2 cloud storage service.
GNU General Public License v2.0
65 stars 14 forks source link

Packagist Install Errors #6

Closed nathanaelphilip closed 5 years ago

nathanaelphilip commented 6 years ago

Hi Hi!

When I try to require it, it gives me this error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for cloudverve/wordpress-cloud-media-offloader-plugin ~0.7.3 -> satisfiable by cloudverve/wordpress-cloud-media-offloader-plugin[0.7.3].
    - cloudverve/wordpress-cloud-media-offloader-plugin 0.7.3 requires dmhendricks/wordpress-toolkit dev-master -> satisfiable by dmhendricks/wordpress-toolkit[dev-master] but these conflict with your requirements or minimum-stability

But when I move my minimum stability to dev, i get this error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for cloudverve/wordpress-cloud-media-offloader-plugin ~0.7.3 -> satisfiable by cloudverve/wordpress-cloud-media-offloader-plugin[0.7.3].
    - cloudverve/wordpress-cloud-media-offloader-plugin 0.7.3 requires dmhendricks/b2-sdk-php dev-master -> no matching package found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

What am I doing wrong? :)

dmhendricks commented 6 years ago

I will check it out. Thank you for the report.

nathanaelphilip commented 6 years ago

thank you!

dmhendricks commented 6 years ago

Ok, I added the forked B2 SDK to Packagist. I've never managed WordPress with Composer before, so hopefully it will work for you.

nathanaelphilip commented 6 years ago

i’ll check it! :)

nathanaelphilip commented 6 years ago

that helped install the package, but it seems like you’re looking for your local vendor install when bootstrapping the plugin, which causes my activation to fail. (i already have a root vendor that has all of the packages installed there, so maybe just check to see if your local vendor directory exists before requiring it?

something like:

if (file_exists(__DIR__ . '/vendor/autoload.php')) {
  require( __DIR__ . '/vendor/autoload.php' );
}

That let me activate the plugin, but then I got a weird Carbon error.

dmhendricks commented 6 years ago

I will look at that - thank you.

What Carbon error did/do you receive, or was it just one time upon activation? Can you reproduce it and maybe post the text or do a screenshot (I use snag.gy).

Thanks again, Daniel