Rafael Bracho

@megamurmulis Thanks but the plugin mentioned above (the zip file) works perfectly well with Firefox 115ESR. No need to edit CSS, just load the plugin and activate it.

• This reply was modified 5 months, 3 weeks ago by Rafael Bracho.

After downloading a couple of plugins to add a code snippet and to see the error log, I was able to execute the code:

add_action('admin_init', 'check_post_type_status');
function check_post_type_status () {
	$post_type = get_post_type_object('post');
	if (!$post_type->public) {
		error_log('WARNING: The default "post" type is NOT public!');
		echo 'The "post" type is NOT public!';		// See if it shows up anywhere
	} else {
		error_log('The default "post" type IS public!');
		echo 'The "post" type IS public';
	}
}

The error log has: The default "post" type IS public!

Can anyone think why there is no language panel in posts when it is available in pages?

Rafael

@threadi Yes, it is Firefox 115ESR (I just checked). I am in one of those “third world countries” discussed in the thread you sent. Am I correctly assuming that I should use the latest attachment, i.e., https://core.trac.ww.wp.xz.cn/attachment/ticket/64350/make-checkbox-usable-again.1.1.zip? Or, should I change the CSS file?

Beware that I sound dangerously knowledgeable, I am technically savvy but lack any familiarity with the WordPress environment.

Thanks,
Rafael

• This reply was modified 6 months ago by Rafael Bracho.

Sorry, I didn’t know about the edits. I did a “Purge All” in Lightspeed, enabled Troubleshooting mode and switched to Twenty-Twenty-Five before going to the “All Posts” page and seeing the same behavior as before. I see that Twenty-Twenty-Five has an update I haven’t installed (I use Twenty-Twenty-Three) but I doubt that would fix it, would it?

The reason I zero in on Javascript is that the checkboxes are operating correctly, I can set and unset categories in the posts but without a checkmark showing whether it is set or unset. And the same behavior was introduced in the login page (the “Remember Me” checkbox). Whereas I don’t go checking and unchecking categories often, I have to login a lot because I switch my writing from the desktop to my mobile phone. I first saw the checkbox problem in the login page after moving to 6.9.

Thanks,
Rafael

Thanks for your reply @janemathew. I followed your suggestion of clearing the browser cache and refresh but it did not fix the issue. I also checked the console, cleared it and brought the “All Posts” page without errors. I then changed the categories of a post by clicking and updating in “Quick Edit” (without seeing the marks) and the categories were modified, so the checkbox is working but there is no tick mark. Again, there were no error when I did all that. As for plugins, I did all this under “Troubleshooting mode” which disables all plugins and sets the environment to a default plain theme.

I can almost swear that the problem began when I moved to 6.9 but I’m not positive, it may have already been there just before. What I do know is that the checkboxes had ticks when selected in a very recent past.

Thanks again for your suggestions,
Rafael

Thanks for the reply, @properlypurple. That did the trick, I was looking in the wrong place.

All the best.

I got a reply on the WordPress core forum explaining that my sleuthing, as I called it, was indeed faulty because the gettext functions may only be called with static strings, so the pseudo code in the template home.html:

<!-- wp:query-pagination-next {"label":"Older Posts"} /-->

should be passing the translated string. In other words, they say that the translation has to be done by the theme.

Anybody has any ideas?

Rafael

Thank you for replying, @jordesign

I only have twentytwentythree loaded but other themes may not show the problem because it depends on how the query-pagination blocks are called.

In the template home.html of twentytwentythree, they are called with the strings “Newer Posts” and “Older Posts” which, as I mentioned, are not translated. That said, the default strings are translated, so if another theme didn’t override the default, the bug will not show up.

I don’t have a sandbox where to test changes, but I believe it’s a matter of modifying the blocks query-pagination-next and -previous to call esc_html__() instead of esc_html()

Rafael