Graham Smith

Just to update, after checking for JS errors, in Chroms, after Disabling JS PROcessing, and clearing all caches, the JS error that Gravity Forms Tech mentioned, doesn’t show up.

So seems like there is a ‘conflict’ when JS Processing is Enabled for ‘some users trying to submit forms’.

Obviously I’d love to be able to benefit for JS Processing in general for all other aspects of my site, so hoping you can work your magic ??

• This reply was modified 8 years ago by Graham Smith.

Whilst I’m here, I did have one very little question:

When I make CSS changes to my site etc, do I need to delete the existing processed files like I would empty WP ROcket and CLoudFlares cache? Or is this not necessary?

Wanted to send you a private note, but couldn’t find a way on this site to do it.

ALl I wanted to ask was if you’d be OK with me publishing your last response on my blog? It’s just such a great explanation to this whol issues with CSS and JS, that I know it would be a good post.

I’d absolutely make sure it was clear it was written by you,bit like a guest post. But I also wanted to use this example as a way of showing how amazing your support on this plugin is and has been. It’s frankly exceptional support, and blows the socks off even commercial support, and I’d love to use you and your plug-in as a shining example of a great wordpress plugin and how a developer takes the responsibility of being a dev author seriously.

Completely understand if you’d rather not, but I at least wanted to ask. I’d show you a draft first, and you’d be free to make changes etc if you did think it was an ok idea.

Regardless, your plugin has made a terrrific difference to my site, and I had tried lots of differing ways and plug-ins before this. My experience with your support was nothing but exceptional.

You’d do well to offer Donations for your work, I for one would contribute some ￡￡’s to your work. ??

Keep it up…

RE CDN and Cloudflare; can confirm. ??

I’ve been with CLoudflare now for a few years, and I then also signed up to Max CDN a year ago.

After a few tests, realised that I wasn’t getting much additional out of MaxCDN, so terminated that and kept with Cloudflare. If anything, a few annoying issues RE Page Score and Performance have been resolved due to dumping Max CDN.

Cloudflare is a no brainer really…???

My bad. Seems it’s another plug-in that references Open Sans, and obviously your plugin just takes what’s there and bundles it all up. ??

I’m looking at the stylesheets now, and removing them.

Sorry again for the ‘accusation’. ??

Graham

Ah, I see. I now understand, all makes sense. Thank you VERY much for the detailed explanatioin.

I actually have another mystery that has started since installing this plug-in. I keep an ete on my Page Speed and Scores etc, and since installing this plugin I’m seeing that Google Open-Sans is being called and referenced, and this is being caught out by various Speed/Score websites.

I only have one Google font referenec for my site design, which is Google Lato, but I’m seeing the complete Open Sans family being referenced and called, which is affecting my overall speed and score accordiung to Pingdom etc

https://www.dropbox.com/s/kj6thaxr76nhq74/Screenshot%202016-09-19%2017.42.48.jpg?dl=0

I knew that WordPress Admin started calling/using Open Sans for the back-end, so I started finding solutions to address this: using code in functions.php, even using plugins built for the sole purpose of preventing Open Sans being referenced, but nothing has worked.

So it does turn out that your plugin is seemingly making calls for Open Sans, and it’s being tagged with every page on my website (as per screenshot).

Is there anyway we can stop this from happening, as it seems quite a performance hit?

Many thanks

Since updating to 3.0.1 and 3.03, there are problems with the new meta area holding information.

When you go to add the title and meta, and do a post save, the information seems to disappear, and is replaced with the default text as though you hadn’t made any changes at all.

However, looking at Source, the previoulsly added information IS saved with the post, but this means the SEO Score is still out of sync, as it reports based on the visible information in the new meta area.

Confusing initially, any ideas on a fix? I put this out on Twitter yesterday, and i’m not an isolated case.

Unelegant Fix Here for Autosave duration.

Not being a coder, I decided to take a crack myself. I think I have found a make do hack, until it can be solved properly.

Edit your ‘autosave.js’ file which can be found in ‘WP-includes’>’JS’>’autosave.js’

There are some values on line 5-7:

jQuery(function($) {
	autosaveLast = $('#post #title').val()+$('#post #content').val();
	autosavePeriodical = $.schedule({time: autosaveL10n.autosaveInterval * 1000, func: function() { autosave(); }, repeat: true, protect: true});

All i did was take a guess and increase these values to some silly high number.

So far, after creating a post and manually saving it, the autosave has not kicked in. This giving me time to actually write a post etc.

Im not too sure what these values equate to in time wise, milliseconds etc, but it appears to work.

You could try removing the complete ‘autosave.js’ file and see what happens, I may try that later. Just back it up.

Hope that helps for the time being.

[sig moderated]

Its not an issue for everyone, but for those that have it it is seriously painful. It does make using WP almost impossible.

It doesn’t lock as such, but is kept in a perpetual state of activity.

As we explain, once the first Autosave is triggered, the save button keeps reactivating/flashing etc, trying to re-submit the page. You can’t brbeak this sequance, so it basically slows the whole site down whilst it is continually make these ajax requests. During this you can’t make any edits unless you quite out and start over, until the first autosave starts, and then you have it all over again.

It also affects any other browser tabs you have to a point where you cannot use any other web sites. You just have to close the whole browser window down.

I have just fiddled with the autosave.js file and upped the time limit to some obscene number and this is now working. it doesn’t autosave and now I can use WordPress. It’s not ideal, but it seems to fix the issue until it can be resolved properly.

Not being a coder, I decided to take a crack myself. I think I have found a make do hack, until it can be solved properly.

Edit your ‘autosave.js’ file which can be found in ‘WP-includes’>’JS’>’autosave.js’

There are some values on line 5-7:

jQuery(function($) {
	autosaveLast = $('#post #title').val()+$('#post #content').val();
	autosavePeriodical = $.schedule({time: autosaveL10n.autosaveInterval * 1000, func: function() { autosave(); }, repeat: true, protect: true});

All i did was take a guess and increase these values to some silly high number.

So far, after creating a post and manually saving it, the autosave has not kicked in. This giving me time to actually write a post etc.

Im not too sure what these values equate to in time wise, milliseconds etc, but it appears to work.

You could try removing the complete ‘autosave.js’ file and see what happens, I may try that later. Just back it up.

Hope that helps for the time being.

[sig moderated]

This is a common problem that is still causing me huge problems, there is a thread here that you might want to add this post to rather than create more and more posts on the same subject.

https://www.ads-software.com/support/topic/172302/page/2?replies=31#post-746691

But I have exactly the same problem, I have posted my findings on the post below just this morning.

As above, have the problem with AutoSave.
This only appeared after a upgrade from 2.3.1 to 2.5.1, I missed 2.5.0. I used the Automatic Update Plug-In.

Creating a new post is fine, you can even write stuff no problem. The problem appears after the first Save. Thereafter, the site becomes non responsive as does the Browser, in this case FireFox and Safari and Camino. The issue affects the whole browser window including any open tabs. Closing the offending WordPress pages clears up the response time.

The Save button just continually flashes randomly thus locking you out of doing anything productive. YOu can sometimes get the site to save any changes by just bashing the Save button continuously, eventually it notices the trigger, but still becomes unresponsive.

I have removed ALL plugins this had no effect.

I DELETED the above WP-Include and WP-Admin folders and replaced these, sadly this did not solve the issue in my case.

To me, this could be solved by being able to disable the Autosave feature, thus eliminating the problem until the real reason can be established. Even changing the AutoSave time delay to some extraordinary time would help. But the powers that be seem to think there is no valid reason to offer the user the ability to choose to have AutoSave or not. This appears to be one good reason I can think off to have this option.

As it stands, WordPress is unusable for me. It take great patience and time to create one post, much closing windows and reopening. This is clearly a problem for many people.

Someone must be able to find out where in the PHP code, Ajax scripts there the code is to alter the AutoSave?

I am reluctant to have to do another clean install, im not that confident with all of this to be able to do it. But I guess I have little choice right now if I want to use WordPress.

There is a possible link to the Database being the offender. After the update, a warning message came up saying the Database had not been updated neither had the ‘clean -up’ of files taken place. This was all the by-product of using the Automatic Update plug-in. But the flashing save button seems to be quite unrelated to any of this, then what do I know.

New install coming up.

SHARE-IT Plugin
I have found out that in my case, this plug-in causes the problem with the

Visual Editor

options disappearing. So please be wary of this potential clash.

This is a huge problem already documented here in the forums.

Since scouring the WordPress forum’s about this I almost gave up with finding a cure. Simply, for ‘apparently’ no reason (and I use apparently loosley here) the Visual Editor would vanish. Now it seems there are several manifestation’s of this. More…

One is the actual Visual Editor would actually vanish completely, leaving you with just the Code tab.

The other one, which I suffer from, would be that the actual Visual Editor menu options would disapear. So you still had the Visual Editor and Code tabs visible, but any way of actually selecting any of the (I will now use the abbreviation VE) VE options would be impossible, as there were not any to choose from.

Leaving for a very frustrating time.

It’s a very common issue, with many contributory factors. Some are just messed up experimental coding, breaking WordPress. I know, I was a prime example of this.

Others though, seem on the outside to be utterly random. I have seen people go to extreme lengths to remedy this issue, with no luck. There are some htings you can do that sometime’s sorts the problem out, but ultimately, for the number of people, they are stuck without hope.
Im don’t have a miracle solution, but I do have a contributory cause in my particular experience, so it can be added to the one of many external factors.

Simple, it was the Share It plug-in. Deactivate it, the VE would appear. Activate the Plug-in and the VE would disappear. Now I don’t know why I didn’t figure this out earlier. I thought I had de-installed all plug-ins as part of the elimination procedure, clearly not.

But this is a reproducible error and is not a fluke.

Hope this helps
<b>Graham</b>
[sig moderated]

SHARE-IT Plugin
I have found out that in my case, this plug-in causes the problem with the

Visual Editor

options disappearing. So please be wary of this potential clash.

This is a huge problem already documented here in the forums.

Since scouring the WordPress forum’s about this I almost gave up with finding a cure. Simply, for ‘apparently’ no reason (and I use apparently loosley here) the Visual Editor would vanish. Now it seems there are several manifestation’s of this. More…

One is the actual Visual Editor would actually vanish completely, leaving you with just the Code tab.

The other one, which I suffer from, would be that the actual Visual Editor menu options would disapear. So you still had the Visual Editor and Code tabs visible, but any way of actually selecting any of the (I will now use the abbreviation VE) VE options would be impossible, as there were not any to choose from.

Leaving for a very frustrating time.

It’s a very common issue, with many contributory factors. Some are just messed up experimental coding, breaking WordPress. I know, I was a prime example of this.

Others though, seem on the outside to be utterly random. I have seen people go to extreme lengths to remedy this issue, with no luck. There are some htings you can do that sometime’s sorts the problem out, but ultimately, for the number of people, they are stuck without hope.
Im don’t have a miracle solution, but I do have a contributory cause in my particular experience, so it can be added to the one of many external factors.

Simple, it was the Share It plug-in. Deactivate it, the VE would appear. Activate the Plug-in and the VE would disappear. Now I don’t know why I didn’t figure this out earlier. I thought I had de-installed all plug-ins as part of the elimination procedure, clearly not.

But this is a reproducible error and is not a fluke.

Hope this helps

[sig moderated]

I have found out that in my case, this plug-in causes the problem with the

options disappearing. So please be wary of this potential clash.

This is a huge problem already documented here in the forums.

Since scouring the WordPress forum’s about this I almost gave up with finding a cure. Simply, for ‘apparently’ no reason (and I use apparently loosley here) the Visual Editor would vanish. Now it seems there are several manifestation’s of this. More…

One is the actual Visual Editor would actually vanish completely, leaving you with just the Code tab.

The other one, which I suffer from, would be that the actual Visual Editor menu options would disapear. So you still had the Visual Editor and Code tabs visible, but any way of actually selecting any of the (I will now use the abbreviation VE) VE options would be impossible, as there were not any to choose from.

Leaving for a very frustrating time.

It’s a very common issue, with many contributory factors. Some are just messed up experimental coding, breaking WordPress. I know, I was a prime example of this.

Others though, seem on the outside to be utterly random. I have seen people go to extreme lengths to remedy this issue, with no luck. There are some htings you can do that sometime’s sorts the problem out, but ultimately, for the number of people, they are stuck without hope.
Im don’t have a miracle solution, but I do have a contributory cause in my particular experience, so it can be added to the one of many external factors.

Simple, it was the Share It plug-in. Deactivate it, the VE would appear. Activate the Plug-in and the VE would disappear. Now I don’t know why I didn’t figure this out earlier. I thought I had de-installed all plug-ins as part of the elimination procedure, clearly not.

But this is a reproducible error and is not a fluke.

Hope this helps