PapaTango

Yes, thank you! I found what I needed in the configuration panel and a minor edit in the gb-form.php file.

Thanks for such a great platform!

@t-p thank you for the ‘Health Check’ recommendation. It was an installed item in my plugins, but I have never really used or explored its capabilities. Before posting my query, I checked the performance in Chrome, Iridium, Firefox, and Edge. No joy. I am not using server side caching on my VPS, so that was not a consideration.

In addition to changing the PHP files with fresh downloaded from WP, checks were made to see if something errant had happened in the .htaccess file. Nope. A compatibility check for plugins via PHP Everywhere revealed no problems. I was about to go back to a previous version of the site (made before the 5.4 update) when I wrote here. I use UpdraftPlus Pro for all my sites–so there are always several versions plus the respective databases.

The site this happened on is a heavily customized one bundled with TNG genealogy software as the research engine. An Avada child theme (heavily CSS customized) brings everything together. Combined with other features making this a complex platform, I look at any malfunction with a sense of dread…

Here is the outcome. I put the site into Troubleshooting Mode, and the Comment admin page displayed correctly on refresh in all browsers. Taking it back out of this mode with the intention of manually turning all 50 plugins off and back on again one at a time until the problem replicated, it worked perfectly!

I have no idea why this cured the issue–unless deactivating and then reactivating the plugins changed the order of how they were being loaded and called up by the core. In any event, things are all good again.

• This reply was modified 4 years, 7 months ago by PapaTango.

Too bad. I was looking forward to using this plugin–but default to the Gutenberg block editor was the deal breaker. Perhaps I will check back in the future and see if there has been a reconsideration of support for Classic/TinyMCE advanced editing. Many of us will continue to use that, and a number of specialized plugins rely on it to provide editing in front-end applications.

Removed, and sent off to the digital dustbin…

OUTSTANDING!

Andrea, thank you. After a 3AM bedtime from kludging custom hacks into a new vB install, a very bleary eyed me replaced the .htaccess with your suggested file at 9AM. The new file bears a strong resemblance to a single blog WP 2.6+ script, no?

All links are now functional–on both old and newly created sites. Tempting fate (as was part of the original plan) I changed the permalinks from date canonical to /%postname%.html for friendly SEO. Flawless…

Now, if I could just find a decent XML sitemap to replace Google XML Sitemaps in 3.0 network mode, I would be one happy publisher…

P

blogmudgeon.com

For some reason the link did not post…

P