Albert Peschar

Hi @dooh,

Thanks for your report.

This is intended functionality. We use this to serve remote scripts with a longer cache duration. It will only serve certain whitelisted domains (such as https://connect.facebook.net) but not any URL.

I do realize there is a potential XSS vulnerability if a whitelisted domain serves HTML and the browser sniffs the content type of the response. I will fix that.

–Albert

Hi @panmaster,

Thanks for using PhastPress and for your kind words!

1. How and when does PhastPress clean the cache?

PhastPress uses filesize and modification time information to detect file changes, so clearing the cache is generally not needed. When you change a script or CSS file, the change should be visible immediately after reloading. If you do want to clear the cache, you can delete all the data inside wp-content/cache/phastpress or wp-content/plugins/phastpress/cache.

I’ve added the answer to this question to the FAQ. (Thanks!)

2. You say it lazy load iframes therefore videos. Would you consider lazy load also images?

We don’t lazy load images, because it doesn’t really help performance. The browser is able to render the page before images are loaded anyway, so there’s no need to do lazy loading.

You suggests WP Super Cache, I would suggest you to take a look at Simple Cache. In my case they scream together.

I recommend WP Super Cache because it is extremely widely used and supported by Automattic, the creators of WordPress. Other simple caching plugins such as the one you suggest, and Comet Cache, also work well. ??

If you enjoy using PhastPress, I’d really appreciate it if you left a review.

Thanks again for your message and have a nice day!

–Albert

Hi @imatei1985,

Sorry, yesterday I forgot to actually upload 1.26. Now there is 1.27 and it should be available to update right now. ??

–Albert

Hi,

@4csmedia: The ABSPATH variable is usually defined in wp-config.php, but I didn’t know it isn’t always there. In PhastPress 1.27 this is now no longer required, as PhastPress uses wp-load.php instead, which always defines ABSPATH. Thank you for your bug report and detailed information about the fix.

@imatei1985:

There is a problem on your server causing output from PHP to be compressed twice. For example, this causes problems on wp-emoji-release.min.js. I don’t know whether this is due to another plugin or your web server configuration. Do you have a .htaccess file? And if so, could you share it with me via gist.github.com pastebin?

Additionally, I see you are using some other plugin to minify scripts. It moves them to /min/abcd.js and breaks PhastPress. Could you please disable any other optimization plugins? There is a conflict with PhastPress, and generally, when you use PhastPress, no other optimization plugins are needed.

–Albert

Hi @imatei1985, @mukeshkumar1995,

I’ve diagnosed and fixed the issue with Thrive Architect. The latest version, PhastPress 1.26, should no longer cause this issue when editing your site using Thrive.

@imatei1985: You will have to revert your latest changes to restore the original CSS. After that, it should work fine.

–Albert

Hi @imatei1985,

Are you using the latest version, PhastPress 1.25?

Could you share the URL of your site with me, so that I can have a look? Please enable the “Minify scripts and improve caching” temporarily, so that I can see what the problem is.

If you’d rather not publish the URL on the internet, please create a new topic and enter the URL into the “the page I need help with field”, so only logged-in users can see it.

–Albert

Hi,

Please share the site on which you have installed and enable PhastPress, and I’ll have a look to see if everything is working as it should.

–Albert

For those that are affected by this issue, comment out this line in squirrly-seo/controllers/Frontend.php:

add_filter('rocket_buffer', array($this->model, 'getBuffer'), PHP_INT_MAX);

This should be on or around line 70.

I recommend not using lazy loading plug-ins with PhastPress. They will not make your site load faster, and images will not be shown until scripts are executed.

–Albert

Hi Yeknafar,

Sorry for not replying earlier. It seems the notifications for new support topic aren’t arriving anymore.

Could you share the URL of your site with me, so that I can have a look?

Hi Robert,

Thanks for trying out PhastPress! Sorry for my late reply, it seems I didn’t get the notification I usually get for new support questions.

If you’re getting 500 errors, there should be errors in your server error log, or in wp-content/debug.log, after enabling WP_DEBUG and WP_DEBUG_LOG.

Could you update to the latest version again, check the logs after reloading the page a few times, and send me the errors that occur?

Hi fabi,

Thanks for trying out PhastPress!

I’ve just released PhastPress 1.23 which fixes the compatibility issue with YellowPencil Visual CSS Editor. Would you like to try it out, and update your review if the issue is fixed?

Looking forward to hearing from you. ??

–Albert

Hey spacemonkey,

I found the time to have a look at this, and just released version 1.22. This new version uses only a short code for each resource, instead of the full URL. Could you try it out, and see if it works for you and fixes this issue? Thanks a lot!

–Albert

Looks like the whitelisting worked out. Great!

I started work on mitigating this in the plug-in as well, but it’s not done for all functionality yet. As it’s working for you now, I’ll mark this as resolved.

If you’re happy with the results on your site, I’d much appreciate it if you left a review here. ??

Hey spacemonkey,

Thanks for trying out PhastPress and for leaving a review!

Unfortunately, that large request URL is caused by us combining all filenames into one. For now, we don’t have a fix for that, although it might be added to a future version of the plug-in.

–Albert