btreece84
Forum Replies Created
-
On line 438 in
class.clients.autolinks.php, removing the argumenttruefromtaxopress_html_character_and_entity(true)for using the entity code as the key fixes the apostrophe/single quote issue. I do not know what other unintended consequences this has on the auto link feature, but going through my content I’m not seeing anything else off so far.Probably has to do with the fact that WP is already outputting the decimal code for this character – though it is being replaced properly in the browser. With zero active plugins and any of WP’s default themes active, the apostrophe character is still output to the browser as the decimal code. So, this method in
functions.inc.phpactually causes the wrong replacement to the HTML entity. The first call to that method (line 320) passes no argument, so they sort of stack on each other.@stevejburge I’m using v3.6.4 and just tracked this issue down to the auto links feature. Apparently, the fix applied didn’t work. Kind of a pain because Safari on iOS doesn’t convert the HTML entity
’to anything, but leaves it in the text. Google Search Console also shows that as text content, and is indexing that entity for my site. Kind of a big deal.Can only see it on some devices by viewing Application > Frames in dev tools; PC and Android at least. Thanks.
Forum: Fixing WordPress
In reply to: Apostrophe appearing as ’Interesting. Creating a fresh clone of my site now to do some plugin testing. Never heard of BIALTY though.
Forum: Fixing WordPress
In reply to: Apostrophe appearing as ’As mentioned above, this unit will be a coin flip, but don’t be bad in every phase of your job.I can confirm this issue as well. That line is entered as
don'tbut you see what shows. The editors do not show it (classic; visual and text). PHP 7.4 and WP 6.0.1 & 6.0.2. Doesn’t show up in Chromium or FireFox browsers on PC (Win 10). Doesn’t show up on Android 12 with FireFox or Chrome browsers.Is does show through Google’s index crawler. It does show on iOS 14+ Safari browser when requesting the mobile site, but not the desktop site. It does show in a text-to-speech reader plugin I have on the site.
The URL I pulled that line from is: https://insidethestar.com/expect-the-unexpected-offensive-line-set-for-week-1/
Feel free to check it out, but it won’t show in dev tools. It only happens in the cases I listed above. Multiple authors using Windows and Mac, FireFox, Chrome, and Safari browsers across two versions of WP. Didn’t start until WP 6.0.1.
Forum: Fixing WordPress
In reply to: Confirmed Saved Post Vanished Completelyfor support.
I can cherry-pick text, too.
Forum: Plugins
In reply to: [Breeze Cache] Major problem, not able to loginI can confirm, disabling either WordFence or Breeze fixes the issue; tried it both ways. And I’m a hosting customer as well. WP 5.7.1, HF Vulter. Stable years old site. Login button has no action while both plugins are enabled. Following.
Began with Breeze 1.2.0 and WF 7.5.3, both updates released and installed yesterday, May 10.
- This reply was modified 5 years, 4 months ago by btreece84. Reason: Added plugin versions
Same issue here. Disabling either WF or Breeze fixes the issue with the login page. Following.
Began with Breeze 1.2.0 and WF 7.5.3, both updates released and installed yesterday, May 10. WP 5.7.1 on PHP 7.4.
- This reply was modified 5 years, 4 months ago by btreece84. Reason: Added plugin versions
Forum: Plugins
In reply to: [GAinWP Google Analytics Integration for WordPress] Project is over Quota.Thanks! That did it.
Forum: Plugins
In reply to: [GAinWP Google Analytics Integration for WordPress] Project is over Quota.Solved? What fixed it, or did it just start working again and you mistakenly called that fixed? Identical error here.
And now it’s gone one further. Had a stats update sometime before 0800 this morning (5,958 sessions) and then another around noon-1300 (24k or so). Sometime since 1400 today, it has reverted back to the 5,958 number. This thing is going crazy all of a sudden. Still no errors or other changes to the site (at all, let alone anything connected with this) and caches and authentication isn’t helping either.
Nobody?
Tried, cleared site cache as well just to be thorough. The hard refresh has been working for days, but that gets incredibly tedious when it’s affecting the edit link modal. Worked this time as well, for one load. Once I save draft it’s broke again with all versions after 1.16.14. Tested this time with 1.17 as you requested. No change, tried twice.
Your suggestion works in theory, except it doesn’t account for the fact that when I upload 1.16.14, the conflict with Yoast disappears entirely and everything works as it should (including OneSignal notifications). I’m also disabling cache through the inspector in Chrome. If it were a caching issue then it wouldn’t work with any version (a changed file is a changed file, regardless if forward or backward changes).
Update: I will give Nginx and Memcached a restart later today when traffic dies down, and see if 1.17 works then. It’s getting a bit specific to my setup, but I’ll reply with my results.
- This reply was modified 7 years, 6 months ago by btreece84.
1.17.0 does not fix the issue.
v1.16.14 does correct the issue.
My Site:
php 7.0
WP 5.1.1
Yoast 10.0 & 10.0.1 (tried both Yoast versions with OneSignal versions 1.16.16 and 1.17, issue remained – OneSignal v1.16.14 fixes issues on both)Linking a screenshot of the console error present during this issue: https://i.imgur.com/SHgQJZd.png
Actually, I’d say it’s OneSignal causing the error. Yoast is trying to do its keyword analysis on the fly and OneSignal is getting in the way, which breaks not only Yoast’s focus keyword function (the whole snippet meta box actually), but also switching between the visual and text editor and the edit link modal. The issue exists for those of us not using Gutenberg (official “Classic Editor” plugin).
I disable OneSignal and all problems immediately resolve. Going to try the last version listed in this thread and also the upcoming version to see if either corrects the problems. Will post back whatever results I get.
- This reply was modified 7 years, 6 months ago by btreece84.
Actually, general settings for this plugin says there was an error, here’s a shot of it: https://i.imgur.com/nN3z3UN.png
@famarinu – I went to GADWP general settings and cleared the cache (next to the “Clear Authorization” button), then hit the other beside it to report and clear errors. My dashboard widget is working fully now. Maybe that will work for you too. If not, also clear the authorization and reauthorize with Google. That was suggested when it had the above error.
Hope that helps.
As for the plugin author, if you have debug info built in, why on earth did you assume it was a conflict instead of jsut asking for that info first? Terrible tech support.