Tagged: x
-
AuthorPosts
-
May 22, 2016 at 10:16 am #1003912
GabrielParticipantAn error occurred while updating WPML Multilingual CMS: “The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature”. A few things I’ve checked:
I have a license and I’ve revoked the key from WPML’s admin interface, and then added it again.
There is enough memory assigned to WP:
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );The plugin directory does not have an inappropriate name with version number such as “sitepress-multilingual-cms.3.1.8.5”.
I did not want to update the plugin manually since this guy got all his links broken trying to resolve the same problem:
https://wpml.org/forums/topic/cant-update-all-plugins/The update worked fine on the dev site BUT there I couldn’t update X because of validation problems, se here. It’s been suggested that it may be a conflict with the theme, and since it worked to update the plugins before X it seems likely.
Please have a look.
May 22, 2016 at 10:19 am #1003914
GabrielParticipantThis reply has been marked as private.May 22, 2016 at 10:57 am #1003946
RupokMemberHi there,
Thanks for writing in! It sounds like you might be having an issue with a third party plugin or script. Regretfully, we cannot provide support for third party plugins or scripts as our support policy in the sidebar states due to the fact that there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script. Because of this, any questions you have regarding setup, integration, or troubleshooting any piece of functionality that is not native to X will need to be directed to the original developer.
If you think it’s somehow related with X, then try to activate a default theme and proceed with the update.
Thank you for your understanding.
May 22, 2016 at 11:11 am #1003956
GabrielParticipantI know, but since it worked on dev version of the same site, where I hadn’t yet updated X, there seemed to be a connection to the theme itself. If it’s a conflict with X then you should be aware of it.
Ok, I could perhaps try what you’re suggesting. But deactivating the theme on the live site will not be a popular thing for this very sensitive client. Especially if there is a conflict and WMPL or the theme won’t work after. On the dev site I can’t test it.
May 22, 2016 at 11:42 am #1003989
RupokMemberHi there,
Updating a plugin should not rely on a theme so I don’t think it’s somehow related with X or any theme rather the plugin itself. I have suggested you that so we could know if there really any issue regarding X.
Thanks
May 22, 2016 at 11:47 am #1003991
GabrielParticipantI see, ok I’ll try it somehow.
Thanks.May 22, 2016 at 12:00 pm #1003999
RupokMemberYou are welcome.
May 22, 2016 at 4:37 pm #1004154
GabrielParticipantI usually remove all unused themes, including the default. So re-installed Twenty Sixteen without activating it. Then the update of WPML worked just fine!?
Ok, thanks for leading my thoughts in the right direction.
May 22, 2016 at 9:44 pm #1004488
Rue NelModeratorYou are most welcome!
If you need anything else we can help you with, don’t hesitate to open another thread. -
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1003912 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
