February 13, 2014 at 12:28 am #151680
after responsive free 22.214.171.124 update (my theme was just the version prior to this + wp 3.8.1): widgets disappeared after update. No sweat, I can reconfigure. But in the dashboard under ‘appearance’ I have no widgets at all? Where are they?
please advice, I love this theme.
February 13, 2014 at 12:37 am #151681
I have the same problem.
“The theme is not widget aware”.
I assume that this will be fixed soon.
In the mean time, you can downgrade your Responsive theme http://wordpress.org/themes/download/responsive.126.96.36.199.zip
February 13, 2014 at 12:56 am #151683
Thanks, great instant solution. I was worried because I just now posted a few things, before I noticed the missing sidebar content and.. no backup yet for that! Thanks for the link- :-)
February 13, 2014 at 2:20 am #151692
This issue has been forwarded to Development and there will be a fix released soon.
In the meantime, if you need the previous version, you can get it here:
February 13, 2014 at 2:55 am #151701
Is your Pro version is also breaking on every new update ?
February 13, 2014 at 3:06 am #151703
No there is no problem with the Pro version on update.
February 13, 2014 at 3:24 am #151709
same problem here – too – am downgrading – sadly a bit shocking that something so required was dropped off – however there have been so many updates with reponsive I really hope its not getting ditched :(
February 13, 2014 at 3:41 am #151716
I would like to ask CyberChimp to remove the upgarde until it is fixed
So people will not waist their time
February 13, 2014 at 3:47 am #151718
Unfortunately there is a problem in the latest update and it is already fixed on our side. Just waiting for the release. We are advising users to use the previous version in the mean time for keep them away from the problem.
February 13, 2014 at 4:13 am #151728
With Responsive theme updates I have experienced problems with header, gallery, menus and home widgets.
My last version wil be 188.8.131.52. I don’t want anymore upgrade this theme on live website in fear if it breaks or not.
Rookies should not try this theme at all unless developers understands what is “beading edge” and “stable” means.
If you ( theme users ) want to be beta-testers before it goes Pro .. Good luck then.
February 13, 2014 at 4:22 am #151734
All problems are sorted and that in the latest update 184.108.40.206.
February 13, 2014 at 4:23 am #151736
Help please! I am new to WordPress and chose the Responsive theme as it was easy to use (update) and looks nice! But this widget issue is killing me! How to I downgrade to the older version of Responsive. I’m not good with html or website chat – so I really need it to be in very basic terms – PLEASE! My website is http://www.quadtourscyprus.com – I’m hoping that when the Widgets are reinstated that my website will go back to normal?
February 13, 2014 at 4:36 am #151742
You can find the previous version here:
You have to install it manually:
The fix is going to release soon, after that you can update to that. (version 220.127.116.11)
February 13, 2014 at 4:43 am #151746
Thanks Jitendra – I’ve downloaded the previous version but do I need to manually add each separate file & folder?
February 13, 2014 at 4:52 am #151748
No you don’t need to add separate file & folder. You have to add the total theme folder. All details are there in the guide provided above.
February 13, 2014 at 5:28 am #151756
GitHub indicates the Widget issue is now fixed on version 1951 but not available yet…
would using the old version pose a security issue?
February 13, 2014 at 6:37 am #151770
I tried adding the downgrade theme using the ZIP file and every time it failed. Any suggestions. Alternatively I would like to upgrade to the corrected version 18.104.22.168 as I would like to use the home widgets. How?
February 13, 2014 at 7:32 am #151795
I downloaded the older version 22.214.171.124 and have unzipped the file – I’ve then uploaded every single file manually and hey presto – my site is fixed and the Widgets are there! Just to be aware that if you do this – WordPress will tell you that there is a newer version available – remember not to download it as it is still 126.96.36.199 and your widgets will disappear. I’m now very wary as to whether to upgrade to the newer version or not – I cannot risk this happening again!
February 13, 2014 at 9:00 am #151821
The fix is out. You all can update to the latest version (v188.8.131.52) which is already available.
February 13, 2014 at 9:08 am #151824
February 13, 2014 at 9:10 am #151827
February 13, 2014 at 9:10 am #151828
I have just upgraded to 184.108.40.206 and it has broken my site again!
Will be switching back to 220.127.116.11 again…
2 failed upgrades in same day
Is this a subtle hint to make me spend $34.99?
February 13, 2014 at 9:11 am #151829
hmm how did it “break” don’t want to try just in case
February 13, 2014 at 9:12 am #151831
February 13, 2014 at 9:20 am #151833
It would appear the content of style.css in this latest update is actually empty!
below is output of style.css
/* Theme Name: Responsive Theme URI: https://cyberchimps.com/responsive-theme/ Description: Responsive Theme is a flexible foundation with fluid grid system that adapts your website to mobile devices and the desktop or any other viewing environment. Theme features 9 Page Templates, 11 Widget Areas, 6 Template Layouts, 4 Menu Positions and more. Powerful but simple Theme Options for full CMS control with easy Logo Upload, Social Networking and Webmaster Tools etc. Responsive is WooCommerce Compatible, Multilingual Ready (WPML), RTL-Language Support, Retina-Ready, Search Engine Friendly, W3C Markup Validated and currently translated into 45 languages. Cross-Browser compatible. <a href="https://cyberchimps.com/forum/free/responsive/">Official support forum</a> (https://cyberchimps.com/forum/free/responsive/) Author: CyberChimps.com Author URI: http://cyberchimps.com Version: 18.104.22.168 Tags: white, black, gray, light, custom-menu, custom-header, custom-background, one-column, two-columns, left-sidebar, right-sidebar, theme-options, threaded-comments, full-width-template, sticky-post, translation-ready, rtl-language-support, responsive-layout, fluid-layout License: GNU General Public License v2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html Text Domain: responsive Responsive WordPress Theme, Copyright (C) 2003-2014 Emil Uzelac, CyberChimps Inc -------------------------------------------------------------- WARNING: (BEFORE YOU MAKE ANY CHANGES) -------------------------------------------------------------- Please do not edit style.css or any other Theme files or Templates directly. If you do, your customizations will be lost as soon as you update Responsive. WordPress and CyberChimps highly recommends Child Theme. Read More: - http://codex.wordpress.org/Child_Themes - https://cyberchimps.com/guide/child-theme-example/ - https://cyberchimps.com/guide-tags/child-theme-2/ */
February 13, 2014 at 9:23 am #151837
wow yeah that is bad – I won’t upgrade then – and will tell all my clients not too either – such a sad state of affairs – I know its free – however you expect free to be done decently, I rarely ask for help so pro isn’t really for me as why pay for something every month you do not use :( – I think I might start looking around for a new base theme for my childs – as I feel we are being forced into the “pro” version for a long time – and well after the two bad updates and the amount of updates recently something has gone quite wrong in their testing procedures – which is very very sad – as was such a reliable company and theme
February 13, 2014 at 9:27 am #151840
Downgraded to 22.214.171.124 again…
February 13, 2014 at 9:32 am #151844
When I applied the 126.96.36.199 update manually from the GitHub Repo I noticed that the CSS directory was empty. Simply avoided overwriting that directory, and the update worked fine.
If you have root access to your web server and have already applied a bad 188.8.131.52 update, you should be able to restore just the CSS directory to fix it.
February 13, 2014 at 9:33 am #151845
I’ve simply replaced style.css from 184.108.40.206
February 13, 2014 at 10:19 am #151859
Forwarding this issue again to development.
February 13, 2014 at 10:47 am #151873
The style.css is supposed to be empty. The styles are now being loaded from core/css/style.css
Sorry for the confusion and any issues. Please share your sites when reporting issues.
February 13, 2014 at 11:00 am #151879
This is my test site
This is the base stylesheet that shows the version
This is the css that is being used.
You can see the changes here between 220.127.116.11 and 18.104.22.168
February 13, 2014 at 11:05 am #151883
many thanks. Very much appreciated. Thank you for all your hard work and your support.
February 13, 2014 at 11:08 am #151884
I have not upgraded any of my sites since the “widgets” disappeared as I am not trusting this on a live site just yet :)
The styles issue – great – ONLY If the users have not included the css in their child theme – which I wonder if that was the issue by the guy above – again just doesn’t seem to have any continuity any more and this CSS move is really breaking peoples websites – for example this is how we did css in child themes
which as you can now see is breaking cos you moved it …
Is there anything included in that CSS file which tells it its move – in your theme vs the child theme I mean?
Agree that “now” the correct way is to NOT include the CSS file in the child theme but I can imagine that a number of people have done and that is why this is breaking things
February 13, 2014 at 11:13 am #151888
Yes, sorry, can I double check on the CSS issue:
I am using the child theme – I have my own CSS in the child theme without the
If I apply the latest update (which moves the parent CSS into the core folder,
I take it that my own CSS in the child theme will still apply – in other words, is this still allowed
after the latest update?
February 13, 2014 at 11:14 am #151889
This will fix your Child theme.
February 13, 2014 at 11:19 am #151891
February 13, 2014 at 11:21 am #151894
February 13, 2014 at 11:26 am #151899
alicecampbell – I have not tested it BUT if you do not use
in your own CSS
then it should work as normal as its not replying on the responsive CSS in that place…. BUT not tested
one of my sites does have this @import and its still breaking :( so I really do not know (and no added the newer css link doesn’t help for me either)
February 13, 2014 at 11:27 am #151900
February 13, 2014 at 8:23 pm #152002
Ok, I updated quite standardly to 22.214.171.124 and … voilà! it worked perfectly. Everything is there. Thank you and it was fast.
One note: you often have messages on updates, things one should do manually. I would love to have a note alongside the update link: alerting me when I need to be careful about ‘that’ specific update / when something more is required. That would really be helpful. :-)
February 13, 2014 at 9:06 pm #152007
I went back to version 126.96.36.199 and that did not change back my child version. Is there something I need to manually add to my child version that was changed when I downloaded the new update?
February 13, 2014 at 9:17 pm #152010
February 13, 2014 at 10:21 pm #152032
February 13, 2014 at 6:34 am #151766
I kept clicking refresh on the theme updates page to see if the 188.8.131.52 update would push through before the workday began, so that when my co-workers started clicking the link to the dev site I sent them at the end of yesterday it would look as intended. Was up early tinkering with a couple of final details when I noticed there was a theme update. :(
Anyway, as the start of the workday approached I grew impatient for the update to publish. So I went to the GitHub repository (https://github.com/cyberchimps/responsive), downloaded 184.108.40.206 from there and installed it manually. Worked like a charm.
February 13, 2014 at 9:23 am #151838
I will try the new update 220.127.116.11 ONLY on development testing environment.
I urge you NOT to update a live site to 18.104.22.168.
Use stable version 22.214.171.124 instead and keep away from bugs.
The bug shows that the development process is lacking sufficient testing.
(making us, the users, the testers…)
Loosing the widgets is too major & critical issue not to be noticed.
Therefore I expect high chances for finding more bugs. (see the empty style.css file above)
YOU WILL SEE VERY SOON additional sub-versions with more bug fixes.
So why hurry and waist time?
Finally keep in mind that the developers & testers are under huge stress, they need the
time to recover.
February 13, 2014 at 10:54 am #151877
I am afraid that I have to add my voice regarding the latest updates. I have not updated anything from 126.96.36.199 until it is confirmed that all the errors have been fixed once for all.
I appreciate all the work that has been put into this theme and I do hope that this will continue in spite of the very unsubtle push that we should opt for the Pro version which some of us don’t need. Sadly, the free support has changed for very obvious reasons.
I would prefer to see exactly which files have changed between the updates and where, as I don’t want to rush into any updates without knowing what’s what. This is usually available on wordpress.org – but I can’t see anything for 188.8.131.52 and 184.108.40.206.
Can you, please, let us know which update is absolutely safe to apply and whether the changes are documented on wordpress.org.
The topic ‘update 220.127.116.11 : widgets disappeared from dashboard?’ is closed to new replies.