websevendev

I think it’s because some assets from 1.0.1 are in your browser cache and they are not compatible with other assets from 1.0.2 due to updates in my build tools.

Opening the browser (Chrome) dev tools (F12) and hard reloading the page (Ctrl+Shift+R) should make 1.0.2 work.

But you can also try 1.0.3 from here, in which I’ve changed the cache busting to be more reliable.

I’ve updated the plugin to version 1.0.2. Let me know if that version works for you.

It should be a known issue that I haven’t gotten around to fixing. I’ll need to update the plugin. Hopefully within a couple hours, if not, tomorrow.

Can you confirm the issue is only happening when animating a dynamic block (for example “Latest Posts” block) but not for normal blocks (like “Paragraph” block)?

• This reply was modified 3 years, 3 months ago by websevendev.

If that’s an issue with the AOS library then you can open an issue there, this plugin simply adds Gutenberg controls for that library, so I can’t really fix it.

But if you can send me a link to your site ([email protected]) I can check in detail what the cause may be and if there’s some custom CSS that can help.

Not sure how default attributes could work, but if it’s repetitive to add them it should be possible to make it accept a list of attributes such as data-one&data-two&data-three which you could just paste in and create all attributes at once, perhaps even with predefined values data-one=val1&data-two=val2&data-three=val3.

https://github.com/websevendev/attributes-for-blocks

I’ll do that, later today.

If it didn’t save a revision of the post upon previewing you would be previewing an older version of the post hence rendering the preview button useless.

I can definitely see a reduction in autosaves, but it certainly isn’t disabled which is what I have the plugin set to.

It does seem to do an autosave at about a minute in for some unknown reason, but after that it’s not doing any more for me.

the autosave bug in WP where once it starts, it gets stuck

Is there a GitHub issue for that?

If you need any info or logs from me, please let me know, thanks.

What does your autosave request respond with?
Open your browser dev tools (F12), go to Network tab, filter by XHR, navigate to a block editor page, make a change, wait for the /autosave request. What’s the status code, what’s the response?

Do you mean WP 5.4.2? Still works for me.
Does the plugin show up for you in the editor if you click the 3 dots in the top right corner? https://i.imgur.com/ThO1ln5.png

Any errors in the console?

Anyway, if there is a 5.4.3 release I doubt it would break the plugin, how ever I did push an update to fix a warning with 5.5 Beta 3.

I still keep getting the Update warning at the top of the screen

Or do you mean you’re getting the message “There is an autosave of this post that is more recent than the version below.” or “The backup of this post in your browser is different from the version below.” when you open the editor? This plugin doesn’t dismiss these messages, but they should go away once you save. Nor does this plugin prevent keeping a backup of the edited post in the browser storage if you navigate away without saving. It just prevents making the autosave XHR requests every 10 seconds that disable the Publish/Update button.

Notice gone, thanks!

Seems to be working fine to me.

In the JavaScript console. F12 on Google Chrome, then switch to Console tab.

Looks like the function was renamed when merging Gutenberg to WordPress core. Updated the plugin to use the new function name when old one is not available. Thanks!

While the it says “Defer unused CSS” it also says “Remove unused rules from stylesheets to reduce unnecessary bytes consumed by network activity.” so I think it means if your stylesheet includes (too many) rules that are not used on the current page then you’re gonna get that message.
I guess Google doesn’t like 1 stylesheet for all pages and instead wants you to load a different, albeit tiny, stylesheet for every page on your site.