Ed Gifford

Sorry I didn’t notice that this was fixed in the newest version, 4.3.51.

Our post content is coming through perfectly, now.

Thanks!

Version 4.3.50 fixed this issue for me.

I am seeing the same issue as airdrummer on versions 4.3.48 and 4.3.47. I’ve rolled back to 4.3.46.

Thanks!

Thanks for getting my fix into your code. I appreciate it!

I don’t believe this fix made it into 1.25. After updating, I’m still seeing the following PHP notice in my log files:

[09-Jun-2017 21:31:43 UTC] PHP Notice: ob_end_clean(): failed to delete buffer. No buffer to delete in wp-content/plugins/minimal-coming-soon-maintenance-mode/framework/public/include/functions.php on line 21

Granted, it is just a PHP notice, but these can clog up the PHP log file and do indicate a minor programming error.

• This reply was modified 7 years, 9 months ago by Ed Gifford.

@chriscct7, Great job on the quick turn around with the fix.

I confirm that version 6.0.13 fixes the issue for me on multiple sites.

Thanks!

@chriscct7

I found the issue on another of our sites. I haven’t turned off the setting for “Track outbound clicks and download links” so the issue is still happening. I left it like this intentionally in case you need to see it in action.

If it helps, take a look at this page:
https://www.delawarelivablelawns.org/certified-businesses

The click on the link for R&L Irrigation Services, Inc. is being consumed by Javascript.

I imagine the other links on the page work because they are internal or target=_blank.

Thanks and great plugin! Let me know if you need any other debugging.

I’m also having this issue but with outbound links, only.

In my case, setting “Track outbound clicks and download links?” to “No” in this plugin’s settings resolves the issue.

When the setting is set to “Using Javascript (recommended)” I see the following output in the browser debug console and the click event is consumed:

__gaTracker.hasOwnProperty(loaded)
true
__gaTracker.loaded
true
Event.which: 1
El: 
<span>Order Today!</span>
Will track: true
Link: Outbound URL
Extension: 
Protocol: https:
External: true
Current domain: sparkellc.com
Link domain: www.amazon.com
Type: external
Control Key: false
Shift Key: false
Meta Key: false
Which Key: 1
Target: false

I edited the line that starts with “Link:” to avoid placing an amazon.com URL to our product in this forum.

• This reply was modified 8 years ago by Ed Gifford. Reason: I added browser console output to my message

FYI: A member of the Yoast team has indicated that this will be fixed in version 4.4.

https://github.com/Yoast/wordpress-seo/issues/6540#issuecomment-281310339

Also reported at GitHub:

https://github.com/Yoast/wordpress-seo/issues/6540

I was searching for a resolution to this and landed here.

It looks like Automattic knows about the issue and has plans to fix it:
https://github.com/Automattic/wp-super-cache/issues/7

There just doesn’t seem to be an ETA on it.

Looking at how this section of plugin works, this is tricky problem. The site’s domain name isn’t stored in the plugin’s configuration file (wp-cache-config.php) and the plugin doesn’t want to look in the options table (to avoid DB hits during cache resolution), so the plugin is trying to tease out the domain name from various constants and environment variables. This gets more complicated because this plugin works with multisite.

To sidestep this, maybe the plugin could detect CLI mode (cron jobs, WP-CLI, etc) and bail on loading the plugin:
https://stackoverflow.com/a/2421484

Looks like configCache.php was removed in 6.1.15 in favor of some other caching mechanism.

Thanks, Wordfence!

I can confirm that version 1.7 doesn’t work. When I import, the plugin ignores my CSV file and imports what looks like demo or testing data.

I’ve posted my copy of 1.6.4 to GitHub: https://github.com/blueblazeassociates/import-users-from-csv-with-meta/archive/1.6.4-p01.zip

I don’t know if that ZIP file can be uploaded to a WordPress install. You may need to unzip and repackage.

But the 1.6.4 code is inside.

—
Edited to a link to GitHub.

Hi Marcin,

Thank you for fixing the error.

I updated and tested with both 1.7.1 and 1.7.2 and can confirm that the issue is resolved.

Thank you,

Ed

I’m going to move our discussion fully over to the WP Types forum. There are a few more posts over there.

For any folks coming to this support topic, we’ve taken the discussion over to the following link:

https://wp-types.com/forums/topic/updated-to-types-1-7-notice-use-of-undefined-constant-icl_sitepress_version/