Page/Post Metabox not showing anything

Figured it out.

Disabling ‘autosave’ for pages/posts causes this.

Is there any way for the plugin to work when autosave is disabled?

Hi @vcchappell,

I hope you are keeping well and sorry to know that you are experiencing this issue.

To further troubleshoot the issue, I tested this on a test website on my end but couldn’t replicate the problem. The SmartCrawl MetaBox functions correctly when the Classic Editor plugin is active on my website.

I understand that you’ve deactivated all the plugins, but could you also verify if you’ve tested this using a default WordPress theme?

Can you please verify that you are using the most recent versions of SmartCrawl and Classic Editor on your website?

Could you please share a screenshot of the issue so that we can better understand the issue?

Kind Regards,
Nebu John

Try adding this code into your theme’s functions.php file:

function disable_autosave() {
wp_deregister_script('autosave');
}
add_action('admin_init', 'disable_autosave');

This is the code to disable autosave on a site, per numerous online sources.

When this code is present, the wds-* js scripts are not enqueued in the footer of the Edit Post / Edit Page when using the Classic Editor. For some reason, they are present when using the blocks/Gutenberg editor.

I’m using the latest versions of the Classic Editor (1.63) and SmartCrawl (3.8.3) plugins.

Here’s why:

Line 769 in /includes/core/controllers/class-assets.php

        $metabox_deps[] = 'autosave';

Sets the ‘autosave’ script as a dependency of the wds metabox script. I guess you are piggybacking on some function provided by the autosave script?

Anyway, deregistering the autosave script means the dependency is missing, thus the wds metabox scripts aren’t loaded.

I’ve implemented a work-around, but this might help if you have other people reporting a similar problem.

• This reply was modified 11 months, 3 weeks ago by V Chappell.

Hello @vcchappell ,

Thank you for the detailed steps to replicate. I tested it and was able to confirm the bug.

I’m creating a report to the developers about it, so they are notified.

kind regards,
Kasia

Hi @vcchappell,

Since the bug was acknowledged, reported and tasked to be fixed, we are marking this as resolved, but feel free to let us know if you have any additional questions.

Kind regards,
Zafer