AA

Hey Mike,

Been following along here since I dropped the OP. So, do you think you solved the problem? I didn’t notice an update since I’ve posted this thread.

Thanks so much for your prompt attention!

CLARIFICATION:

I said

The Delicious alt tag is actually the post image url, therefore, /wp-content/uploads/myphoto.jpg.

To be more specific, when the post includes a photo, the Delicious alt tag is the default post image url, not “Save on Delicious”.

Hope that helps!

Thanks for getting back to me!

Forgot to ask…does the plugin validate in the W3C, at least as much as possible?

And, are the social site links “no followed” by default?

Thanks!

Would be great to hear from the devs on this.

Thanks!

pmccarthy1,

Thanks for the reply!

So is stat tracking is only available to the end user/publisher? In other words, in my case, me?

Hi,

Thanks! You actually actually answered this via email as well. Appreciate the replies.

Thanks for the replies Matt!

I read the privacy policy & understand that there well be tracking.

The data about your site is intended for you when you log in, either to your WP console or AddThis.com

I can disable site stat tracking though, yes?

Hi Matt & thanks for the reply. Much appreciated!

Do you mean disabled by an end user or the website owner?

Website owner

If stat tracking can be disabled, is there any other tracking going on once stat tracking is disabled by the website owner?

And what do you mean by validation, exactly? The W3C validator?

Yes, the w3c, sorry for the lack of clarity.

… should you so choose, and in our analytics interface on AddThis.com with more detail.

Is this info available publicly or only to the website owner via login? There is another popular sharing plugin out there that unfortunately reports this data publicly!

I’ll read the privacy policy as well. Thanks!

Ditto Mook73, dblacombe, & fredmag

Needed to uninstall…Hope this gets fixed soon.

Also, Digg not working, but this seems to be a problem with many sharing plugins.

Thanks!

@jerleung,

I’m curious, do you use, or have you ever use the plugin WPTouch?

Also, have you tried the development version of WP Super Cache as Doncha suggested above?

Just reporting what’s happening…I am no developer, so I can’t explain why… ??

I will say that WPSC is still working fine on 2 other sites, one w/ the new dev version & one on the older version of WPSC. No issues that I can tell. One of those sites runs Thesis, as does the one with the issues, & one uses another theme.

Keep in mind that I first noticed the errors just after I installed WPTouch & initially assumed that was somehow causing conflict w/ WPSC. But the problems persisted even after disabling WPT & I saw that many others were experiencing the same problems with WPSC that I was. Also, I figured that you would have said something if in fact WPT & WPSC had compatibility issues that could have caused these sort of issues. I know you have had direct contact w/ the team from WPT based on what I’ve read in various forums & it would seem that there are no compatibility issues. Thanks!

Hi Doncha,

Switching to legacy caching has nothing to do with the error on line 977.

Didn’t think so… I switched to Legacy because mod rewrite began casting a 977 error. “Couldn’t resolve host ‘www.mysite.com” was also a message received during this time. Only the PHP mode seems to be working correctly.

The error on line 977 is fixed in the dev version

Again, the dev version did not fix the problem for me & many others.

The memory problems are just a result of the plugins you use, including this one. Just increase the memory allocation.

I have plenty of memory. The only memory warning I ever received was when the problems w/ WPSC were occurring.

I appreciate your support & use of your terrific FREE plugin for many years, but many have been experiencing the same problems w/ WPSC in 2012 & the dev version is not helping. Seems that something has gone awry w/ WPSC & its functionality as of late. I know you say that the dev version has addressed the issues, but so many with the same problems say it doesn’t correct. Many also have experienced the problems with the cache not seemingly clearing properly. I hope the issues are corrected soon. I realize that you may not agree, & if I am wrong, I apologize, but me & many others are in the same boat. Thank you much for your efforts Doncha!I will check in for updates, but for now, I needed to uninstall the plugin on the site in question, as 2 of 3 modes weren’t functioning & clearing cache was acting up as well.

Uploaded the dev theme & mod rewrite still not working. Fetching fails with error “Couldn’t resolve host ‘www.mysite.com”. Went back to PHP caching for now.

Please advise as other users are experiencing the same issue. Again, is there a pro version that might prove more effective? Thanks Doncha.

Thanks!

The memory happened just after I switched to Legacy caching & hasn’t happened before or since. I switched to Legacy because mod rewrite caching began casting the “977” error. Others have also been experiencing that error as well, yet you don’t think that whatever is going on w/ WPSC might be the cause of the memory errors as well?

Thanks!

PS-If this dev version is the answer, should I uninstall the current version first, since I won’t be using auto update? Thanks!