noisegate95

Thank you for the thorough response…

1. All 4 or my websites on two totally different hosts, did not get hacked.

2. The code was edited to make it “look” like the version was up to date, therefore wordpress was NOT alerting me to update this plugin, and a supposed hacker who clicked update all, would not of had that option.

3. My ISP did not do it, because they would have at least backed it up. There is nothing.

All your ideas seem to be legitimate, but we are talking about 4 different sites.

@acp73
Looking at your source, you are using disk “enhanced” for page cache. Change that to Disk “basic”. Also disable database and object cache.

As for Cloudfront: I was always under the impression that Cloudfront needed to pull from somewhere. Not needing S3 with Cloudfront doesn’t sound right to me, but I could be wrong.

You basically setup an S3 bucket, Setup your CNAME’s, (cdn.yoursite.com, cdn1.yoursite.com), then setup Cloudfront and W3. Depending on your W3 config, you can either push (manual) or pull (auto) your content.

A user will go to your site, W3 will direct them to Cloudfront – Cloudfront will pull the content from S3 and serve it to the user.

There are many sites that will assist you in getting W3 working with CLoudfront.

As I am waiting this one out, as I know I spent a lot of time tweaking and configuring W3 for optimal performance.

I DID however install fresh on two test sites that did NOT have the older version and it went without an issue.

For those users who are removing W3 and re-installing, I am assuming you are having to re-configure the plug-in from scratch or are you just restoring a W3 backup file?

@110101100, I had to sign in just to comment on your post. Do “you” even bother to test out plugins on a test site, prior to jumping right in on day one? For someone who runs a commercial site, I would think this would be an important first step.

Let’s all remember something. This is a FREE product. Work through the problems, but there is no need to get downright nasty!!!

Not everyone has the same WordPress host, the same plugins, the same this, the same that… So there is no way in he11 the author can create something with a “Standard” config.

Just saying!

Remove all caching plugins and try again. It seems this theme does not play nice with minifying.

Not a problem on the forum assistance. I’m no guru, but I pitch in when I can.

I’d be more than happy to to do some beta testing on any new revisions you may have. I would really like to stick with this plugin, even though my extension list is not limited to mp3, I can still limit the size.

You can contact me via https://blog.noisegate95.com/contact-us/ and we will go from there.

Thanks.

I just came here to see if anyone got this plugin working as I noticed it is not functioning for non-logged in users. I saw your post – and I had the same issue when I changed my permalink structure, thought I would share.

Try editing your .htaccess file to do the redirects.

This site will create htaccess redirects that you can place in your htaccess file, and immediately the redirects will begin, and you will not lose all your SEO. Just scroll down and hit the generate redirects button. This only works if you are changing to /%postname%/

Just a thought.

Will do. BTW, I wish all plug-in authors had the same “reply” methods as you. Keep it up! Thanks.

According to the change log:

0.6

Refactored the way file storage happens. Uploaded files are now obscured and downloads are routed through the plugin so as to help prevent unwanted execution of uploaded files
Elaborated installation instructions

Email client? Do other links of that extension work?

Via FTP, go to /home/yourhomedirectory/.spamassassin/ and edit user_prefs. Add a whitelist entry:

whitelist_from *@host-ed.me

OR

Lower your required score. Add this line (or change existing, most likely it is 5)

required_score 2.5

Camu, thanks for the update. Miraculously, the error is no longer. I am getting stats, but I guess they will be skewed due to this caching issue.

With W3TC it is possible to set certain php functions not to be cached, well at least so I’m told. Would setting the /plugins/wp-slimstat.*php directory to do just this solve the problem?

Chris

I did it the hard way.
1. Disable W3TC.
2. Rename the folder in the /plugins directory to wp-total-cacheOLD.
3. Open the “new” plugin in 7Zip.
4. Remove the version “0.9.2.5” from the folder name. Save
5. Remove the version “0.9.2.5” from zip file name. Save
6. Install the newly renamed plugin using the “upload” feature in WP.
7. Verify W3TC settings and functionality. (New Prime button)
8. Delete the wp-total-cacheOLD folder in /plugins.

I received that same minify re-write error. I think just clearing your cache, and verifying your three htaccess files, you should be good to go.

If you are using a CDN such as Amazon, you should upload all your files once again, to get the new caching config working. Also try the new “Prime” button in the Page Cache setup. Click “Prime Cache”.

More testing of all 4 of my websites after installing this new version, the initial first response of each site has dropped from about 8-10 seconds, to about .3 – .5 seconds. Amazing.

The fix mentioned above totally fixed my response time issues. I swore it was Cloudflare. Give it a shot.