Phoenix said
stevebluck said
Just enable them here: http://grab.by/9d2h By default they are now turned off to save clutter.oops sry daniel
no worries phoenix…. 
- Attended a Community Meetup
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 1 and 9 items
- Contributed a Tutorial to a Tuts+ Site
- Exclusive Author
- Has been a member for 4-5 years
- Item was Featured
Daniel_R said
Parallelus said
I somewhat agree with wizylabs. If you don’t have a specific reason to upgrade to 3.1, such as a feature it offers that you absolutely MUST have, I wouldn’t bother. Most of the updates were targeted at developers, not end users. The benefit is minimal (if any) for existing themes...
Just say NO to 3.1
![]()
thanks Parallelus for your details…..
but I will have in some way to disable the notification so my clients wont make the mistake to upgrade
That’s another thing about WordPress that annoys me. Any decent CMS will put the control in the developers hands, not the user. They should get rid of that notification or make it option to enable/disable and from a code level like the .config file. Might be a plugin for this. If not you can target it with CSS
.update-nag { display: none; }Use this plugin to disable the update notification – Far easier than updating all the themes individually
thank you Parallelus and Gareth!! this info is valuable!!
