-
Notifications
You must be signed in to change notification settings - Fork 28
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
* is not a zip archive. #1
Comments
Hey @david-treblig ! I'm glad you find this plugin useful. From the look of it, it looks like the ACF archive isn't downloaded correctly. Are you using the ACF plugin? If so, have you entered the correct key in the You can just remove any of the Pro plugins you aren't using from your This plugin has been tested on Mac, Windows and Linux - so I'm pretty sure it works well. So I'm hoping it's just a small thing like that. |
Mmm I tried again today and it doesn't seems to work. I only added polylang pro and ACF pro, the only two I need, with the vcs repo at the top and added all the info necessary to my .env file. It seems to be loading everything correctly, but then tells me the zip file doesn't exist. I'm on a Mac btw. I've been using ACF pro installer for years, but I've been looking for an alternative since I'm a Polylang Pro user as well. |
Got it! Same issue that was mentioned many times here : PhilippBaschke/acf-pro-installer#19. Prestissimo is the culprit. You can look at the proposed PR here so that this plugin runs after Presstissimo https://github.com/PhilippBaschke/acf-pro-installer/pull/20/files. |
Thanks for pointing this out! Let me take a deeper look into this and make sure I implement a solution which not only patches this problem, but also prevents further plugin conflicts. |
I have the same problem with me as well. 😞 |
Just wanted to chime in here. I am having the same issue when trying to deploy my Trellis > Bedrock > Sage project on my server. Everything seems to work fine on my local dev. |
I had the same problem! |
Hello, I recently came across this very same issue. Upon running
Double My
|
@andrade1379 I've come across that issue with WP All Import / Export. They seem to have an issue with their configuration of Easy Digital Downloads. Try changing the version number to an earlier version number. It has helped me in the past. |
Getting the same problems. This error shows for ACF but if I remove ACF then the same thing happens with GravityForms:
I am also on the Roots framework and I've tried Twansparant's suggestion to deploy first before adding packages to composer, but it hasn't worked.
|
@stuartcusackie Do you use Prestissimo? This plugin doesn't currently support Prestissimo |
Yes, it seems I am using Prestissimo. It's the first time I've heard of it but I can see it in my Roots Trellis packages. It seems composer 2.0 will use an alternative method and Prestissimo will be obsolete. I will try your package again when that day comes. Thanks for your help! |
Okay, great thank you @stuartcusackie ! |
Sorry about that, you're right, it still does not work. I'm also using the Roots stack with Prestissimo so that's the reason it fails... |
So I thought this error was also related to Prestissimo because Trellis includes it here as a global package, but when I disable this line and re-provision my local and my remote server, it still happens. When I ssh into my remote server and check for the global packages: Running |
@Twansparant Do you use |
Hi @junaidbhura, locally I always use |
Hi! Thanks for creating this plugin, this is exactly what I would need for Polylang pro. There seems to be a problem right now though and your repo seems pretty recent, so I thought I'd leave an issue either way.
I get this error when using "composer update" :
'web/app/mu-plugins/advanced-custom-fields-pro//77d11e6a97cd4d47687579fa4009c261' is not a zip archive.
It seems like there's a double "//" somewhere in your code so that the zip file isn't found... but I'm saying that without having taken the time to look at it properly.
Let me know if you know what this is about!
(Using Bedrocks as WP install)
The text was updated successfully, but these errors were encountered: