Wondering if anyone has any advice on how I can revert back on the most recent update that was released today? I just ran the update and it's messed up all of my contact forms.
http://www.servicesanitation.com/request-a-quote
http://www.servicesanitation.com/contact-us
As you can see it added random bullet points to each field and has thrown all the margins out of wack. Any advice?
Thanks!
Sounds like you or someone had edited the forms.css file in the plugin, which you should not do for this reason, it gets overwritten.
Just place the CSS snippet below in your theme's stylesheet (or wherever you are instructed to place custom CSS at the theme level).
[css]
body .gform_wrapper form .gform_body ul, body .gform_wrapper form .gform_body ul li {
list-style-type: none !important;
list-style-image: none !important;
list-style: none !important;
background-image: none !important;
background: none !important;
padding: 0 !important;
margin: 0 !important;
border: none !important;
}Just to add on to what Rob said, reverting back won't help you if someone made such changes, the only way forward is to restore from your own back-ups or fix the issues you have now the right way so that they are future-proof and work with new releases.
I just want to add that the styling on my forms were also messed up by the new update. I have never edited forms.css so the new update is doing something strange with the CSS.
Fortunately, my host allowed me to revert to a backup so I could restore the old version. Can someone explain to me how to prevent the new update from destroying my CSS? Thanks.
@SamChyung
Nothing significant changed on the front end for normal form styling. Can you explain what "destroying your CSS" means? If you can give us an example of what happened, then we might be able to offer some real help. As always, you're welcome to go to the form settings page and set the "output CSS" option to "no". That way you can roll your own CSS and not use any of the defaults that come with the plugin.
Here is what the CSS looks like before the update - http://www.samchyung.com/contact/
Here is what the CSS looks like after the update - http://schyung.staging.wpengine.com/contact/
All the time I put into coding the CSS to look right is destroyed by the update.
@SamChyung
I'm having the same problem with the styles getting lost. We're both using the WP-Minify Wordpress plugin to combine and minify the css files. It looks like GF 1.6.x had all the styles included in the forms.css and now in 1.7 it uses @import statements to pull in the styles. These @import statements are getting dropped when minified by the WP-Minify plugin. To get around the problem you can add forms.css to the WP-Minify CSS options exclude list so it doesn't minify it. When you manage as many sites as I do, however, making this change to accomodate the new GF stylesheet is quite a burden.
@lamanagementco I agree. It's a burden. But the fact that WP-Minify chokes on CSS that utilizes @import statements seems asinine to me. The whole point of the @import statement in CSS is to be able to organize complex CSS so that it is easier to manage and work with. The fact that these minify plugins choke on something as simple and commonly used as the import functionality is absurd.
I appreciate you pointing out this exact issue and cause, other users couldn't provide us with more helpful information and the more information we have the easier it is for us to determine what the issue is and then determine a course of action.
The fact that we are now going to have to either look for a work around or revert back to one giant CSS file to work around the fact all these minify plugin authors are hamstringing us as plugin developers is completely ridiculous. The fact that we need to make our code worse to work around other people's poorly thought out plugins makes me angry.
If you are running a plugin that does any kind of caching or code minimizing you'll need to check to see how you can whitelist the Gravity Forms forms.css so that it is not minified. Also if you are running a caching plugin make sure you clear cache. CACHING IS DESTRUCTIVE WHEN DEALING WITH DYNAMIC FUNCTIONALITY. You shouldn't cache pages containing forms.
I think this is the source of our problem, as well. Will try to make sure to exclude forms.css.
Also, I wish GF support people would be less condescending to other developers. The minify plugins are great, and widely used, so I think GF needs to work with them instead of insulting them as asinine. Just language only makes GF look bad.
@osseonews Minify plugins appear great to you as a user. But the fact that they don't support something as simple and basic as an @import in CSS is completely crazy.
You need to keep in mind that i'm condescending towards these developers because these developers cost us money. They aren't the one's providing support to users encountering issues due to their plugins shortcomings. We as a company are. I as a business owner am incurring these costs.
@import is very basic CSS functionality that is commonly used. It makes me angry that as a developer we need to implement hacks and workarounds to get around the shortcomings of other developers poorly thought out code.
Just as you said this Gravity Forms issue is costing you money, it is costing me money by having my support team having to provide support to users on an issue caused by someone else's plugin not being able to handle commonly used basic CSS functionality.
The developer of the minification plugin on the other hand continues on, oblivious to the problems he has caused. Ignorance is bliss.
Hi Carl,
Understood. But, nearly all the minify plugins conflict with the 1.7 version. We use a different one than mentioned above and I'm sure it's causing us the problems also. I think GF needs to accept the ubiquity of these minify plugins, instead of fighting them right now, so people's sites don't break upon upgrading to 1.7. I looked at the forms.css in an earlier version of GF and it doesn't use @import, so in theory there shouldn't be any reason why at least this part of the issue can't be fixed quickly on GF side. Thanks for all your comments.
FYI, I can now confirm 100% that the issues we faced were due to minify scripts. I think you can just put a notice in the 1.7 download that if you are experiencing a problem, be sure you scripts do not minify forms.css - handle in enqueue of gforms_css
Thanks for everyone's help.
For everyone here and any users who stumble upon this thread, please see this post in regards to 1.7.1: http://www.gravityhelp.com/gravity-forms-v1-7-1-released/
