jakemc

If it helps anyone else, I discovered almost by chance that the problem was fixed by ensuring that my CPT supported “page-attributes” (which I’d assumed wouldn’t be necessary since it was defined as “hierarchical”).

So, changing
'supports' => array( 'title', 'editor', 'excerpt', 'custom-fields', 'thumbnail', 'revisions' ),
to
'supports' => array( 'title', 'editor', 'excerpt', 'custom-fields', 'thumbnail', 'revisions', 'page-attributes' ),
fixed the display problem for my query block variation in the block editor.

Not sure if this counts as a Gutenberg bug. I’ll be happy to submit it to Github if someone thinks it is…

Thank you, Helena. I think my issue is different: the issue you’ve linked to appears to be about one query block variation’s parameters affecting other queries on the front-end whereas my query block variation sits happily on the front end with other queries from other query block variations all with the desired output. The problem is that it’s not working in the block editor: the block appears but the results of the query are not displayed, just the block loading gif. No console errors are displayed either.

Please let me know if I’ve misunderstood, otherwise I’ll raise the issue on Github.

Thanks again.

Can anyone tell me where I would report this as a bug?

It was caused by jquery being included twice.

… or I should say that it *didn’t* then work for me, but it stopped the error occurring…

The two slashes should be separated by the content of a variable $theme. However, when setting up your feed in wp-admin, the default theme isn’t automatically selected. Select and update and it worked for me.

Thank you James. It was indeed a theme-specific issue. I’d used the admin_head filter hook to insert a CSS declaration. No idea why that caused the problem, but removing it solved the problem. Thanks again.

Excellent! Thank you.

Thanks Devon. Very happy to help with beta testing. Is there a way I can send you my email address privately?

Thanks Devon.

The site I’m working ondoes have categories, but not all are relevant to blog posts, so it could be confusing. For the moment, I’ve commented the relevant lines in public/views/post-notif-public-display-sub-prefs.php. Would it be possible to wrap the categories functionality in an action hook (which can be removed in functions.php) in the forthcoming release?

Thanks again.
Jake

P.S. I have a feature request! Are you happy for me to post here or would you prefer a feature request somewhere else?

Thanks jkhongusc.

I honestly can’t remember where I got that information. Thanks for correcting me though.

In case anyone else has the same problem:

I checked my wp-config.php again and noticed I had set
define( ‘DISALLOW_FILE_MODS’, true );

removing this line allowed updates to be ‘noticed’ and performed.

I understood that this definition switched off the ‘edit’ menu for plugins and themes, not auto-updates. Could this be a bug?

Thank you jkhongusc.

But, as I said, turning on debugging by setting define(‘WP_DEBUG’, true); hasn’t yielded any useful information. No errors are displayed in wp-admin.

Thank you jkhongusc, but no PHP errors are reported in the admin area, and nothing useful I can see on the front of the site.

This is a serious problem because it means that I have to manually upload the full WordPress installation every time there’s an update (and there have been several in the past couple of weeks alone!)

Any more suggestions? Please?

Many thanks for your reply Mika.

I’ve manually reinstalled 4.1.3 but it’s still not aware that 4.2 is available.

Any further suggestions?