carlhancock

We definitely don’t recommend editing core WordPress files.

Gravity Forms is sold as a yearly subscription. The renewal for the Developer License is 50% off the $199. What you are paying for is support and software updates. This discount expires if your license has been expired for more than 60 days.

If your license is no longer eligible for the renewal discount let me know and I can update it so that it is.

You should always run the latest version of WordPress and any WordPress plugins you are using so if you are using commercial plugins I definitely recommend making sure you renew them each year. Updates are very important. Not just for WordPress compatibility reasons like this, but also from a security standpoint.

Are you running the latest version of Gravity Forms?

This issue was resolved in Gravity Forms v1.9.12 prior to the release of WordPress 4.3 while WordPress 4.3 was still in beta.

Make sure you keep everything up to date. If this issue is occurring with WordPress v4.3 AND the latest version of Gravity Forms then please submit a support ticket on the Gravity Forms support site.

Downgrading isn’t the solution. Upgrading Gravity Forms is.

WordPress v3.6 introduced a new version of jQuery. Gravity Forms, like all plugins and themes, utilized the version of jQuery that is built into the WordPress core.

This change necessitated updates to Gravity Forms to maintain compatibility. So in order to run WordPress v3.6 and Gravity Forms you must have the latest version of Gravity Forms.

This is why renewing Gravity Forms in order to continue receiving software updates is important. You should ALWAYS run the latest version of WordPress AND the latest version of all WordPress plugins for security and compatibility reasons.

Downgrading the version of WordPress you use in this situation could leave your site vulnerable to any security fixes applied in the WordPress v3.6+ release. Same goes for running old versions of Gravity Forms.

Invested interest? Nothing couldn’t be further from the truth.

I couldn’t comment without providing a rating. I could care less about this plugin. My comments aren’t about this plugin they are clearing up the gross misconception that is being perpetuated by some of the comments made here that then made their way into blog posts bashing this plugin.

I came across the plugin because of numerous blog posts that were written about it based on Franz public statements and those blog posts all pointed to the fact that this plugin “phones home” as some sort of malicious evil thing.

There was a lot of misinformation being spread about this plugin based on how people were complaining about it that impacts the SaaS community as a whole. One of the things that this plugin was being bashed for was “phoning home”, which is absurd because if a plugin interacts with a SaaS service it’s going to “phone home”.

So if you take that time to actually read what I wrote you’ll see that i’m clearing up the misinformation about plugins “phoning home” because that in and of itself is not a negative and is not something a plugin should be bashed for nor pointed to as being malicious.

But what do I know. I’ve only developed one of the most successful commercial WordPress plugins in existence today. So i’m obviously full of crap.

That makes perfect sense. I didn’t notice the “Requires 3.5” higher when installing the plugin. I just figured given all the publicity it has received with articles in TechCrunch, etc. that it would work with the latest public release as WordPress 3.5 isn’t even in beta yet… you’ve probably had a lot of users do the same and encounter the same issue.

I encountered the same behavior as the user above. Users do not see the liveblog updates and when logged in as an admin and posting liveblog updates… if I refresh the page those liveblog updates disappear. They do not appear to be actually getting saved.

Here are some screenshots illustrating what is happening…

I have created a new live blog entry on a post where i’ve enabled the liveblog plugin. See this screenshot:

https://skitch.com/carlhancock/et18r/test-liveblog-gravity-forms-v1.6

I then refresh the page and my live entry disappears. While it appears to be published in the screenshot above… refreshing the page makes it go away, never to appear again. See this screenshot:

https://skitch.com/carlhancock/et18c/test-liveblog-gravity-forms-v1.6

As for a non-logged in user browsing the page, they never even see the liveblog entry that I created and published. It never appeared, just like it disappears when I refresh the page as an admin after creating it.

I’ll have to leave this one for the developer of the Directory Add-On, i’m not familiar enough with it to know for sure what is going on. The Notices aren’t the problem, it’s the Fatal Error at the end that is going to be the issue.

This sounds like a PHP memory issue or there is some sort of error. My hunch is this is it’s PHP memory related. Partial page loads like this frequently happen when your site runs out of available PHP memory and is unable to complete the process.

I would suggest increasing your available PHP memory. Here is a tutorial that explains how to do this:

https://www.nerdgrind.com/increase-wordpress-and-php-memory-limit/

You may need to contact your web host for assistance.

Another option is for you ro turn WordPress debug mode on in your wp-config.php and then browse to the page and see if an error is returned.

If no error is present and increasing PHP memory does not resolve the issue then it is also possible it could be MySQL memory related.

Does Gravity Forms show a renewal message in the Admin Notification email (not the User Notification) if you have an expired license key? Yes.

But you are incorrect that it can’t be removed, and this has already been explained to you via email when you attempted to enlist Joost de Valk in some sort of campaign to damage our reputation. But you left that part out, primarily because Joost had no problems with how we handle the license expiration message once it was explained.

Removing this renewal message is simple: remove your license key from the settings page of Gravity Forms. Problem solved.

An expired key is an expired key, so disabling the message while you have an expired key entered isn’t possible without editing code… which you are free to do of course because it’s GPL. HOWEVER removing the license key means you have no license key, so there isn’t going to be a message about an expired license key. There won’t be any message because you wouldn’t have a key. If your key is expired and you don’t want to renew it, then there is no reason to have it entered on your Settings page.

The message in the Admin Notification is one of the ways we try to get out in front of users to make sure they are aware that their license key has expired and give them an opportunity to renew. We provide users with a substantial discount to renew their license, but only for the first 60 days after the key expires.

We try to give users every opportunity to renew, in order to do that we need to be able to make them aware that the license has expired. The notice in the Admin Notification (NOT the User Notification) is one of the ways we do this. Relying on the user logging going to the Settings page of Gravity Forms isn’t the most efficient means of notifying them… they may never go to the Settings page again after they initially install Gravity Forms.

Wouldn’t you be upset if you wanted to renew your license at a 50% discount (for Developer and Business Licenses) but weren’t aware your license had expired and now you are out of the 60 day discounted renewal period so you can’t get the 50% discount anymore?

Again, to get rid of this “nag” is simple… remove your license key from the settings page.

Your comment that you don’t nee software updates is entirely a personal choice. But I will say that it isn’t a good one to make. A perfect example is the release of WordPress 3.2. WordPress changed the version of jQuery that comes bundled with WordPress. This change made older versions of Gravity Forms incompatible with WordPress 3.2 and require us to release updates to resolve this issue prior to the release of WordPress 3.2. There is a lot of value in having access to software updates because we don’t control WordPress so sometimes we have to release updates to ensure compatibility with new releases.

So if you don’t renew your license key and WordPress releases an update that changes core functionality… you may not be able to update your version of Gravity Forms to ensure compatibility unless you have a valid license key.

We provide users with a substantial discount when they renew. It’s a small price to pay to ensure Gravity Forms will continue to work with each new WordPress release.

The reason why you are unable to upgrade Gravity Forms using the automatic upgrade feature is because you are running an old version of Gravity Forms (v1.3.9) on a WordPress 3.0+ site.

Gravity Forms released an update before WordPress 3.0 was released to fix a compatibility issue with the WordPress 3.0 automatic upgrade system. WordPress changed the hooks available to do upgrades and older versions of Gravity Forms were not compatible.

Because you did not keep your Gravity Forms plugin up to date when we released updates, the version you are running is not compatible with the 3.0.1 automatic upgrade functionality.

You will have to upgrade manually by registering and logging in at the support site here: https://www.gravityhelp.com using the same PayPal email address you used to purchase Gravity Forms. You can then download the latest version of the plugin and install/upgrade manually.

I would upgrade to the latest version and then test to see if you still experience a conflict with the Multiple Galleries plugin.

Here’s a tip. Something anyone using WordPress should live by…

If you download a WordPress theme or plugin that has obfuscated code in it, don’t use it. Delete it. Use something else.

Support developers who don’t obfuscate their code and always download your themes or plugins from reputable sources such as the WordPress repository or directly from the premium theme or premium plugin developer.

Also keep in mind, WordPress GPL licensing debate aside, if a theme or plugin you are obfuscated is not released under the GPL and was released under a non-GPL license… you could be violating their license agreement by de-obfuscating it and using www.remarpro.com to facilitate that license violation.