mattstratton

I found that pasting the URL into the Facebook debugger cleared out Facebook’s stale info that was causing the 404…after doing this, the 404 issue on sharing went away.

https://developers.facebook.com/tools/debug/

I’m having the same issue. Site is https://www.arresteddevops.com. All of the stuff coming from the CDN (CloudFront with S3 orgin, set up in W3TC) has no expiration set for the client, even though it is set within the plugin.

For example, here are the headers coming from origin:

* Connection = keep-alive
* Vary = User-Agent
* Pragma = public
* CF-Cache-Status = HIT
* CF-RAY = 10f7a9b832930755-AMS
* Accept-Ranges = bytes
* Content-Length = 43924
* Cache-Control = public, max-age=31536000
* Content-Type = image/jpeg
* Date = Sun, 23 Mar 2014 03:50:07 GMT
* Expires = Mon, 23 Mar 2015 03:50:07 GMT
* ETag = "ab94-4f5241b06d1bc"
* Last-Modified = Fri, 21 Mar 2014 20:55:27 GMT
* Set-Cookie = __cfduid=d8b6a37ac1e911d72154b389cfc5582471395546607392; expires=Mon, 23-Dec-2019 23:50:00 GMT; path=/; domain=.arresteddevops.com; HttpOnly
* Server = cloudflare-nginx
* X-Powered-By = W3 Total Cache/0.9.3

and here are the headers coming from the same image in cloudfront

* Connection = keep-alive
* Age = 34
* X-Cache = Hit from cloudfront
* X-Amz-Cf-Id = rjDTYHTSfWYJaEHnFU_MKb-n3KiOkbb2iIut7s8CjMnAhbh2URA8tg==
* Accept-Ranges = bytes
* Content-Length = 43924
* Cache-Control = public
* Content-Type = image/jpeg
* Date = Sun, 23 Mar 2014 03:48:32 GMT
* Expires = Mon, 23 Mar 2015 03:42:07 GMT
* ETag = "d14f107a21808776af7eecb757463c9a"
* Last-Modified = Sun, 23 Mar 2014 03:42:07 GMT
* Server = AmazonS3
* Via = 1.1 2feaae5abe3e9545d63b67a1381aec70.cloudfront.net (CloudFront)

I don’t consider this “resolved”, as in my case, there ARE no pages/posts/tags/categories that are using that slug.

I suspect there is something wrong with your support form. I log into your premium page and fill out the support request, and get a confirmation page that it was received. I’ve opened two requests. Maybe you can test that? Or provide us an alternate method of contacting you as the support form doesn’t seem to be working?

We are. The point is that this plugin’s author is ignoring the premium support requests. So perhaps a public post pointing out that when you pay for the premium you don’t get support might help them realize they should reply to support requests.

I am having the same problem. I tried to open a support request (I have paid for pro) and it has been ignored.

I have had the same experience. This is ridiculous. The plugin is not working properly, I paid for it, and they ignore support requests.

Same issue. And I discovered that if I mark the username as blank, the list choices disappear as well.

So what am I supposed to do in the meantime? Usernoise is broken for any sites using jquery 1.9…and not just in IE. This happens in chrome too.

I purchased the pro version for my site, and I cannot use it. What is the workaround?

FYI, you can see the issue here:

https://www.whiskeyandboots.com/

Deleting that </script> tag did not do the trick for me. It just caused a different feed validation issue.

What’s odd is that it only occurs on one of my blogs. Must be something flaky with the theme. This is really bad though. My feeds are not working now due to this issue.