donshirer

Unfortunately, while the previous fix (resetting the Permalink setting to Post Name) restored the post views, it has now bollixed up the Permalinks of new pages. For example, I just added a new page with the title Show:2003-Gondoliers and the Permalink on the edit page showed as https://ctgands.org/2003-show-gondoliers/ as I expected. When I viewed the page it displayed correctly but clicking on the address revealed its URL was actually https://ctgands.org/show-2003-gondoliers/?wppa-occur=1&wppa-cover=0&wppa-album=22&wppa-photo=240,and using the listed Permalink of /2003-show-gondoliers/ produced a 404 page not found error.
We are using WP 5.03, and Classic Editor plug-in and I permanently deleted the trash so there would be no interference from previous attempts with similar names.

Why does WP add the extra ?wppa junk to a page Permalink?

Thank you all. It does appear that something corrupted our Permalink settings, changing them so some strange custom version. I reset this on both our sites and now new posts show the correct permalink and the old post permalinks are restored once they are updated.

I appreciate your objections about eliminating posts, but we do not use the RSS feed and have had trouble with hackers attacking our posts in the past, so although we are rethinking it, I would still prefer to limit posts to training new authors and using only pages for content on our site.

Thanks for the tip, but my “three dots” menu does not have an “Edit as HTML” option. It only has:
Editor
Visual editor
Code editor
Plugins
Yoast SEo
Tools
Manage All Reusable Blocks
keyboard Sortcuts
Copy all Content
Options
(and the Options tag does not have it either, nor does the Settings icon).
I’m using Safari on a Mac.

Sorry we have so little info. Our sysop is new at this and didn’t press the host techie for details. All we know is that he disabled the plug-in and we were then able to sign in. He said the screen showed an http 500 error message.

I sill would like an Add Media button on the code/text editor. If they can put one on the visual editor they could put one on the text editor just as easily. Taking away a useful option is not progress.

Thanks for the quick reply. I just discovered the “additional options” myself. Can you still call the three dots an ellipsis if they are vertical?

Next problem. The Add Media link has disappeared from the both the text and visual editor windows. The Visual editor has a small icon that apparently does the same thing but I can’t find a similar action on the code/editor window. Having to flick back and forth from code to visual editor is inconvenient. It is very inconsiderate of WP to remove options or make them more difficult to access when they update?

Found part of the problem. Somehow the backup had changed the Settings:Permalinks option to “Custom” whereas it had always been set to “Post Name” since the site was created in 2011. Changing that setting back seems to have fixed most of the post error problems, but we will have to check all of several hundred posts to be sure. Ugh.

So I am marking this topic fixed, but still unresolved is why the backup changed that, and whether it changed any other settings that will come back to bite us later.

Running the inspection console after right-clicking on a link to a post (in Chrome) we get what appears to be some javascript with “Uncaught ReferenceError” messages as below:

jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 1.4.1
wppa-utils.min.js:1 At: 0:6:58.950 message: wppa-utils.js version 6.6.28 loaded.
wppa-utils.min.js:1 At: 0:6:58.950 message: wppa.js version 6.7.09 loaded.
wppa-utils.min.js:1 At: 0:6:58.951 message: wppa-slideshow.js version 6.7.09 loaded.
wppa-utils.min.js:1 At: 0:6:58.951 message: wppa-ajax-front.js version 6.7.07 loaded.
wppa-utils.min.js:1 At: 0:6:58.951 message: wppa-popup.js version 6.1.9 loaded.
wppa-utils.min.js:1 At: 0:6:58.951 message: wppa-touch.js version 6.6.06 loaded.
princess_ida_650.jpg Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING
wp-fade-in-text-news.js:35 Uncaught ReferenceError: FadeIn_SetFadeLinks is not defined
at FadeIn_FadeRotate (wp-fade-in-text-news.js:35)
FadeIn_FadeRotate @ wp-fade-in-text-news.js:35
29864wp-fade-in-text-news.js:47 Uncaught ReferenceError: FadeIn_bFadeOutt is not defined
at FadeIn_Ontimer (wp-fade-in-text-news.js:47)
FadeIn_Ontimer @ wp-fade-in-text-news.js:47
setInterval (async)
FadeIn_FadeRotate @ wp-fade-in-text-news.js:32
—-
Similar results when we try this with other browsers.
This is beyond our level of knowledge. Do you think this is a WordPress problem or something wrong with our Server?

After analyzing the transmuted post url’s, we realized that they appear to be hexadecimal representations of the original. We’re still uncertain as to why that occured or how to fix it. The permalink field on the post edit form does not have a way to edit the url, and although we can select it, nothing happens when we attempt to type in a new permalink.

Thanks for the responses, they un-mystified the post id. Actually, I had already figured out an alternate way to do it, create a unique category, assign only that post to the category and then tell the widget to display in that category. More than one way to skin a cat, I guess.

@displaywidget :
I updated to the new version of your DisplayWidget plug-in and have verified that it also fixed the problem with the location list not displaying.

I don’t want to get involved in your argument with Dave. Both of you have obviously spent considerable time and effort in creating your plug-ins and I applaud you both. I’ll keep both your plug-ins around just in case the WP gurus disable something else in their next version.

Updating to Display Widgets SEO Plus restored the location options in the widget editor.
Thanks for the tip, Dave.

Updating to Display Widgets SEO Plus restored the location options in the Widget editor.

I think I figured it out…
use in_category(‘category name’) instead of is_category

I am disappointed that the widget was changed without an explanation for us poor folk who are mostly ignorant of php.

I was finally able to contact the author, who suggested the following fix:

On the form edit page for that form. Go to the Styles tab
Change Clear DIV setting: change the clear:left; to clear:none;
Change Field Left DIV setting: just change the clear:left; to clear:none;
Change Submit DIV setting: just change the clear:left; to clear:none;
Click the Save Changes button.

This did the trick. I still don’t know whether the problem was due to his new FSCF version or the new WordPress version, or why the previous clear settings suddenly didn’t work in widgets, but a fait accompli is better than nothing.