nick_byrd

We’re have the same issue on the Verbosa theme at philosophyofbrains.com.

Mike Eckman posted a temporary workaround to the thread you linked to:

Go into Appearance, Customize, then when in the Customizer, go to Post Information, Meta Information, and uncheck the box for Display Comments.

Disabling that option will make the itemprop=”discussionURL” text go away, but it also takes away the count of how many comments are on each post. If you can live with losing that number, you can get rid of the text that is showing up now.

https://www.cryoutcreations.eu/forums/t/comment-problem-after-updating-to-wp-6-3#post-141562

Hi @whitsey. I must have been insufficiently clear.

The image URLs that are being generated (e.g., the second bullet point in original post) are erroneous: they are not the attachment URLs that WordPress creates (and allows me to customize). They do not lead to attachments. They lead to error pages—e.g., “THERE HAS BEEN A CRITICAL ERROR ON YOUR WEBSITE. LEARN MORE ABOUT DEBUGGING IN WORDPRESS.” Hence, the search console errors.

The site’s attachment pages work as they are setup to (in WordPress settings). I am not having issues with attachment pages.

So it’s the error-producing, non-attachment URLs (e.g., the second bullet in the original post) that I want the site to stop generating and/or including in sitemaps.

Alas, I cannot find any setting in the WordPress dashboard that makes sense of why these non-attachment, error-producing URLs are being generated in the first place.

Hi @kentbrew!

Yes, I think that is a safe assumption–at least, that assumption obtains on all the WordPress sites that I manage.

Thank you!

My diagnosis of the same (or similar problem) so far is here. (It seems like an issue with Social Warfare’s inability to handle the latest tinyMCE standards in 4.9.6, as far as I can tell.)

• This reply was modified 6 years, 10 months ago by nick_byrd.

I’ve contacted the plugin developers. I’m just posting this to (a) save other Social Warfare users some troubleshooting and (b) see if others have a better idea than the obvious one (i.e., deactivating the problem plugins).

Thanks for your reply!

Thanks for reproducing this for Pinterest, @dwcouch! I look forward to hearing more (if more happens).

Thanks @dwcouch. That makes sense. Two updates:

1. I was able to recover the content from the Way Back Machine: https://web.archive.org/web/20170826184218/byrdnick.com/archives/11793/christopher-peacocke-reflective-self-consciousness

2. I had migrated my site to a new host about a month after this post went up. Perhaps —?related to your hypothesis —?this post reverted back to an earlier revision as a result of that migration process. I’m hoping that this is the only post that was reverted/corrupted. I’ll check the rest ASAP.

I’d say your hypothesis is the current best explanation. If I can conclusively support one or another hypothesis, I’ll post an update.

In the meantime, I remain open to additional thoughts and ideas.

A colleague found the following workaround for Chrome users:

…if you go to the end of your comment and hit “tab”, you should jump to the next boxes and see the “post comment” button again.

A colleague found the following workaround for Chrome users:

…if you go to the end of your comment and hit “tab”, you should jump to the next boxes and see the “post comment” button again.

@fivejs: I am editing in Safari with the Pinterest extension installed.

That seems to support your hypothesis that the problem is Safari and/or the Pinterest extension.

@petredobrescu: Are you posting/editing in Safari and/or with a Pinterest extension installed?

I seem to be still getting the error despite switching to Php 5.6

[07-Jul-2017 14:47:37 UTC] PHP Warning:  Illegal string offset 'width' in /home1/byrdnick/public_html/wp-content/themes/twentyfifteen/inc/template-tags.php on line 115
[07-Jul-2017 14:47:37 UTC] PHP Warning:  Illegal string offset 'height' in /home1/byrdnick/public_html/wp-content/themes/twentyfifteen/inc/template-tags.php on line 116
[07-Jul-2017 16:34:18 UTC] PHP Warning:  Unknown user in /home1/byrdnick/public_html/wp-content/plugins/jetpack/class.json-api-endpoints.php on line 1117
[09-Jul-2017 00:46:11 UTC] PHP Warning:  Illegal string offset 'width' in /home1/byrdnick/public_html/wp-content/themes/twentyfifteen/inc/template-tags.php on line 115
[09-Jul-2017 00:46:11 UTC] PHP Warning:  Illegal string offset 'height' in /home1/byrdnick/public_html/wp-content/themes/twentyfifteen/inc/template-tags.php on line 116
[09-Jul-2017 07:26:59 UTC] PHP Warning:  Illegal string offset 'width' in /home1/byrdnick/public_html/wp-content/themes/twentyfifteen/inc/template-tags.php on line 115
[09-Jul-2017 07:26:59 UTC] PHP Warning:  Illegal string offset 'height' in /home1/byrdnick/public_html/wp-content/themes/twentyfifteen/inc/template-tags.php on line 116

Done. Thanks! I’ll come back in 24 hours to report whether I am still receiving these errors. If I’m not, I’ll be sure to mark this as resolved (and give @gauravpadia credit).

You are right, @gauravpadia: I am running PHP 7 after all.

I just contacted my host. Here are my PHP 5 options:

PHP 5.4
All files with the extension .php will be handled by the PHP 5.4 engine.
Legacy PHP with security updates. Compatible with most environments.

PHP 5.4 (Single php.ini)
Same as PHP 5.4, but all subdirectories will use ~/public_html/php.ini

PHP 5.4 (FastCGI)
All files with the extension .php will be handled by PHP 5.4 FastCGI processes.
FastCGI for PHP makes all your PHP applications run through mod_fastcgi instead of mod_suphp. This eliminates the overhead of loading the PHP interpreter on every hit. Since it is always in memory ready for the next hit, the responses will be generated faster.

PHP 5.6
All files with the extension .php will be handled by the PHP 5.6 engine.

PHP 5.6 (Single php.ini)
Same as PHP 5.6, but all subdirectories will use ~/public_html/php.ini

PHP 5.6 (FastCGI)
All files with the extension .php will be handled by PHP 5.6 FastCGI processes.
FastCGI for PHP makes all your PHP applications run through mod_fastcgi instead of mod_suphp. This eliminates the overhead of loading the PHP interpreter on every hit. Since it is always in memory ready for the next hit, the responses will be generated faster.

Any idea which of these PHP 5 options would be best?

[deleted]

• This reply was modified 7 years, 8 months ago by nick_byrd.
• This reply was modified 7 years, 8 months ago by nick_byrd.

Hi @xkon and @gauravpadia. I’m listing the plugins I have installed below. Feel free to point out candidates to start with. Otherwise I will try to check some of them myself.

Advanced Ads

Akismet Anti-Spam

AMP (Accelerated Mobile Pages)

Anti-Malware Security and Brute-Force Firewall

Google Analytics Dashboard

Featured Images in RSS w/ Size and Position

Select Frame Buster (not activated)

Jetpack by WordPress.com

Links Shortcode

Social Warfare (not activated)

Social Warfare – Pro

Spreaker Shortcode (for embedding podcasts)

UpdraftPlus – Backup/Restore

Visualizer: Charts and Graphs Lite

Wordfence Security

WP Force SSL

WP-Optimize

WP-Polls

Yoast SEO (not activated)

Yoast SEO Premium

And in case this is worth adding, I’m now noticing an error that has been occurring between the illegal string errors:

[04-Jul-2017 12:38:23 UTC] PHP Warning: Unknown user in /home1/byrdnick/public_html/wp-content/plugins/jetpack/class.json-api-endpoints.php on line 1117

And this error showed up yesterday after I posted this;

[04-Jul-2017 12:02:20 UTC] PHP Warning: mkdir(): File exists in /home1/byrdnick/public_html/wp-content/mu-plugins/endurance-page-cache.php on line 218

I didn’t install that plugin. I suspect that my host installed it (after some spikes in traffic that were causing performance issues). I don’t even see the plugin on my Plugin page.

• This reply was modified 7 years, 8 months ago by nick_byrd.