composer autosave running amock and making site useless
How can I disable this? and why do I even need autosave? Can't I just click the 'save' button?
This seems to be new in 575rc as I used 574 and previous a lot, but 575rc is so slow it is almost useless... 30 seconds to open a homepage with nothing on it .. from localhost! the exact same setup with 574 loads a very complex page in half that time.
Just tried to create a blog page through composer in 5.7.5RC1. I have no issues similar to yours.
I 'fixed' the problem by increasing the autosave timeout from 5 seconds to 500 seconds.. with no obvious side effects. The better official option would be to have autosave as a configurable option.
I think there's a good argument for turning off Autosave - or at least having the option to do this in a global setting.
Even with your proposed update to save only 'on change', there are times when you might make a small update then change your mind. Normally you would leave the page without saving, or maybe you've even deleted this quick update in Composer. In such instances, autosave makes a new version which then needs publishing or discarding - even though nothing has visibly changed.
I don't have a problem hitting the save button when I've made a change and neither do my clients. It would be nice to have the choice.
this is a virgin install (no code changes), with the theme Fundamental and the Problog add-on.
If I had the option to increase the time between calls that would fix it, and this would not be 'taking out the batteries'. There could be a number of reasons why this might be happening having nothing to do with C5 but rather the local test environment which might me the reason why it can not get a return in less that 5 seconds.
I am not claiming this is a bug with C5... I am saying it should should be a configurable option