Home › Forums › Calendar Products › Events Calendar PRO › Update Error – Unrecognized content encoding
- This topic has 17 replies, 4 voices, and was last updated 6 years, 2 months ago by Wendy Limauge.
-
AuthorPosts
-
December 19, 2017 at 12:26 pm #1409080Wendy LimaugeParticipant
I received this message when trying to update the plugin to version 4.4.20
Download failed. cURL error 61: Unrecognized content encoding type. libcurl understands deflate, gzip content encodings.
Return to Plugins page
========================
PLEASE LEAVE FOR SUPPORT
Reporting the same issue as: https://theeventscalendar.com/support/forums/topic/curl-error-61-unrecognized-content-encoding-type-libcurl-understands-deflate/December 20, 2017 at 10:35 am #1410084Jaime MarchwinskiKeymasterHi Wendy,
Thanks so much for reaching out!
I’m sorry that you are experiencing this issue when trying to update your plugin. It is possible that something must have timed out during the retrieval process. Can you try updating it manually through ftp? Just remove the current copy on your server and upload a version from your My Account > Downloads page.
Let me know how that goes!
Thanks,
Jaime
December 23, 2017 at 12:05 am #1412129Wendy LimaugeParticipantThis reply is private.
December 23, 2017 at 12:22 am #1412133Wendy LimaugeParticipantThis reply is private.
December 23, 2017 at 12:34 am #1412135Wendy LimaugeParticipantThis reply is private.
January 1, 2018 at 5:02 am #1415576Jaime MarchwinskiKeymasterHi Wendy,
Happy New Year!
I’m glad to hear that you have been making some progress with your site. As a next troubleshooting step, can you try switching to a default WordPress theme, such as ‘Twentyseventeen’ and see if the issues still exist?
Let me know how that goes!
Thanks,
Jaime
January 3, 2018 at 1:14 am #1416784Wendy LimaugeParticipantI just switched to Twenty Seventeen, Twenty Fifteen, and Twenty Twelve the and layout issue is still the same. I also enabled WP Total Cache and cleared Page Cache. I disabled WP Total Cache again because that often causes issues with the site.
January 3, 2018 at 8:11 am #1416971Jaime MarchwinskiKeymasterHi Wendy,
As a next step, let’s try to rule out if there is a conflict at play. I know that you have already tried switching to a default theme, but can you try going through our full testing for conflicts procedure?
Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.
But, before you do that, there are 2 things I would advise:
1. Make a backup of your database
2. Consider activating a “Maintenance Page” plugin if you are doing this on your live site (to minimize impact on your visitors)
If that does not resolve the issue, can you try flushing your permalinks by going to Settings < Permalinks and Save Changes.
Let me know how that goes!
Thanks,
Jaime
January 3, 2018 at 4:07 pm #1417506Wendy LimaugeParticipantThis reply is private.
January 3, 2018 at 4:47 pm #1417538Wendy LimaugeParticipantThis reply is private.
January 3, 2018 at 4:58 pm #1417548Wendy LimaugeParticipantThis reply is private.
January 4, 2018 at 4:32 am #1417800Jaime MarchwinskiKeymasterHi Wendy,
I apologize for all of the extra work and inconvenience that this issue has caused you on your site. It seems that this is a known issue among users currently who are unable to update the plugin.
For now, to update your plugins I would recommend you to follow the steps suggested in the following article:
https://theeventscalendar.com/knowledgebase/manual-updates/
I’ve added the issue to our internal bug report and you will be contacted as soon as a solution is available.
Thank you for your patience and understanding and if you have any other questions in the meantime, please let me know!
Thanks,
Jaime
January 9, 2018 at 3:45 am #1421138PatriciaMemberThis reply is private.
January 9, 2018 at 8:30 pm #1422057Wendy LimaugeParticipantThis reply is private.
January 10, 2018 at 10:24 am #1422710PatriciaMemberThis reply is private.
-
AuthorPosts
- The topic ‘Update Error – Unrecognized content encoding’ is closed to new replies.