Title: micromaze's Replies | WordPress.org

---

# micromaze

  [  ](https://wordpress.org/support/users/micromaze/)

 *   [Profile](https://wordpress.org/support/users/micromaze/)
 *   [Topics Started](https://wordpress.org/support/users/micromaze/topics/)
 *   [Replies Created](https://wordpress.org/support/users/micromaze/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/micromaze/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/micromaze/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/micromaze/engagements/)
 *   [Favorites](https://wordpress.org/support/users/micromaze/favorites/)

 Search replies:

## Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Contact Form 7] Class ‘WPCF7_FormTag’ not found error](https://wordpress.org/support/topic/class-wpcf7_formtag-not-found-error/)
 *  [micromaze](https://wordpress.org/support/users/micromaze/)
 * (@micromaze)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/class-wpcf7_formtag-not-found-error/#post-8536588)
 * I renamed the contact-form-7 folder in filezilla to contact-form-7-1
    The site
   was accessible with an error saying contact form 7 was deactivated, so I reactivated
   it and it is all working now. Not sure why but it is a workaround.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Contact Form 7] Class ‘WPCF7_FormTag’ not found error](https://wordpress.org/support/topic/class-wpcf7_formtag-not-found-error/)
 *  [micromaze](https://wordpress.org/support/users/micromaze/)
 * (@micromaze)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/class-wpcf7_formtag-not-found-error/#post-8536572)
 * Me too
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [There were failures during background updates](https://wordpress.org/support/topic/there-were-failures-during-background-updates/)
 *  Thread Starter [micromaze](https://wordpress.org/support/users/micromaze/)
 * (@micromaze)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/there-were-failures-during-background-updates/#post-4381637)
 * Firstly we use the plug-in Advanced Automatic Updates, secondly the wordpress
   updates and then thirdly iThemes has an automatic update system as well.
 * This is the issue we are having see below:
    I’m definitely not using alpha beta
   as it comes up with you are using the latest version ie 3.7.1 of WordPress at
   least I know how to check that now and know that I am definitely not using it.
   For ages iThemes/Builder plugins have been having a message come up have your
   plugins automatically updated through the iThemes licensing section and for a
   long time it didn’t work and then I realised that I was using old versions of
   Builder so I updated to the latest version of Builder and now have them all licensed
   in their licensing section under the settings tab and this is supposed to automatically
   update all of those. It updates the Plugins and the Builder Core not the actual
   Builder Theme as that way you may lose changes you have made. We had some advice
   from the iThemes people but that didn’t work so my business partner tried un-
   licencing all the plugins and themes and he thinks that he has got them to automatically
   update. Nobody on the iThemes boards has said “Hey we don’t do automatic updates”
   and we have had a couple in the past work – just now majority of them aren’t 
   working. I will cut and paste from an email when it did work just so that you
   can see that I am not confused. Here is a copy of the email that has shown that
   a Builder update has occurred during the Automatic updates see below:
 * WordPress site: [http://kangaroovalleykayaks.com.au/](http://kangaroovalleykayaks.com.au/)
   
   The following plugins were successfully updated: * SUCCESS: Recent Facebook Posts
 * The following themes were successfully updated:
    * SUCCESS: Builder
 * UPDATE LOG
    ==========
 * Recent Facebook Posts
    ——————— Updating plugin: Recent Facebook Posts Downloading
   update from [https://downloads.wordpress.org/plugin/recent-facebook-posts.1.8.4.zip&#8230](https://downloads.wordpress.org/plugin/recent-facebook-posts.1.8.4.zip&#8230);
   Unpacking the update… Installing the latest version… Removing the old version
   of the plugin… Plugin updated successfully.
 * Builder
    ——- Updating theme: Builder Downloading update from [https://s3.amazonaws.com/downloads.ithemes.com/products/themes/builder/Builder-5.0.16.zip?AWSAccessKeyId=AKIAI5UDI5LNTO2U5YBQ&Expires=1386057848&Signature=eUW2OT%2FD8QyenWA4O5HE5svT72M%3D&#8230](https://s3.amazonaws.com/downloads.ithemes.com/products/themes/builder/Builder-5.0.16.zip?AWSAccessKeyId=AKIAI5UDI5LNTO2U5YBQ&Expires=1386057848&Signature=eUW2OT%2FD8QyenWA4O5HE5svT72M%3D&#8230);
   Unpacking the update… Installing the latest version… Removing the old version
   of the theme… Theme updated successfully.
 * I just wanted to show that I wasn’t crazy and that I wasn’t expecting miracles
   and that there is an ability for the iThemes stuff to do an Automatic update.
   If there is anything else I need to provide you with to assist with these queries
   please let me know as I would love to fix the problem as updating 30 sites and
   growing really isn’t fun as I could be spending the time much more productively.
   I would appreciate more than words can say any help that you can provide on this
   thanks so much, Have a great day!!!
 * What we have worked out is that the licensing code is expiring before the update
   has a chance to go through. Looking at the Unix Time stamp converter and the 
   time that we get the failed email the code has expired anywhere from 6-12 hours
   before the request comes through. We are hoping that iThemes are going to send
   us a fix for it. As it is happening on almost all of our 25+ sites but then we
   did have 1 site update successfully from 5.0.15 to 5.0.16 so we are hoping we
   have found the solution. Will keep the post updated.
 * If anyone else is having this issue please post here

Viewing 3 replies - 1 through 3 (of 3 total)