- This topic has 5 replies, 3 voices, and was last updated 8 years, 5 months ago by Sakin.
-
AuthorPosts
-
July 23, 2015 at 4:58 pm #61382PaulParticipant
While updating from catch flame pro 2 to 3
following message. please advise a solution. this is the 4th ticket in 2 days and only 1 has been answered 🙁—
The update process is starting. This process may take a while on some hosts, so please be patient.Enabling Maintenance mode…
Updating Theme Catch Flames Pro (1/1)
An error occurred while updating Catch Flames Pro: Update package not available.
Disabling Maintenance mode…All updates have been completed.
July 24, 2015 at 9:32 am #61423SakinKeymaster@Paul: The update of Premium/Pro theme will not work like that as these theme are not hosted in WordPress.org. So, for this you need to follow instruction mentioned in theme instructions page at http://catchthemes.com/theme-instructions/catch-flames-pro/
If you want to update from WordPress Dashboard, then first you need to install plugin Catch Updater. You can download this plugin from http://catchthemes.com/wp-plugins/catch-updater/ and install it from “Plugins => Add New => Uploads”
Then download the latest version of Catch Flames Pro zip file from your account at http://catchthemes.com/my-account and then upload it from “Appearance => Themes => Add New => Uploads”
October 28, 2015 at 8:01 am #78645KimParticipantHey Sakin!
I’m having the same problem on my site when trying to update to 3.2. I followed the instructions. I have catch updater but I’m still getting:
October 28, 2015 at 10:18 am #78652SakinKeymaster@Kim: Check the steps that you have missed:
1. First you need to install and activate “Catch Updater” from “Plugins => Add New => Uploads”
2. You need to download the latest zip file from your account at http://catchthemes.com/my-account
3. You can upload the downloaded zip file from “Appearance => Themes => Add New => Uploads”October 29, 2015 at 5:27 am #78717KimParticipantThat’s exactly what I did.
October 29, 2015 at 10:22 am #78725 -
AuthorPosts
- The topic ‘Update failure to 3.0’ is closed to new replies.