Support

January 30, 2015 at 5:32 am

Actually this finally kicked in and started causing me problems.

One option would be to have the whitelist and also make sure that the option “Clear all cache files when a post or page is published or updated.” is set.

January 31, 2015 at 10:20 am

Speaking of plugins, do you have any recommendations for a plugin to make my site more mobile-friendly, one that you know works well with EE4?

That’s not really a job for a plugin (although some may try) its based on your sites theme. If you theme is responsive, then so is EE4.

Are you saying that it’s not necessary to add “/register/” and the rest of that list? (Is that the whitelist you’re referring to?) Is Event Espresso somehow set to never get cached, with or without adding any strings?

You will always need to set Event Espresso from caching. We are taking some steps to try and ensure that Event Espresso never caches, but it will always be best to manually set all Event Espresso core pages from caching.

Do you know of a better cache plugin to use with EE4?

They all work in basically the same way so its personal preference really. The way caching works is by building pages that users view and saving them for future visitors.

So lets say you have a page of text (and maybe images), each time a user visits that page, your webserver hits the DB for the relevant data (which can happen multiple times depending on the data) builds the html output and sends it to the browser.

Then the next visitor visits the same page, the same happens all over again, and again, and again.

Caching basically saves the page the first time a visitor views it and sets ‘expiration’ on that page. So then visitors view the page and the server simply says ‘I have this page saved, here you go!’ which is find for static content, that rarely changes.

The problem with this is how do you select tickets from a page that doesn’t actually check with the DB if tickets are available? When you input your attendee info and that is sent to the server, the returning page, the server says ‘Hey I have this already’ and gives you a page, that appears totally irrelevant to your attendee. Each page EE also uses ‘nonce’ values, which is why a ‘security error’ will pop up if the pages are cached (once the nonce has expired)

So caching Event Espresso (or any other e-commerce type plugin) pages isn’t really an option. You can cache the static pages around them, but not the dynamic pages EE needs.

Its also worth noting that some of those options will update your .htaccess file with some rules. Those rules will not be removed from that file when you uninstall the plugin, so it could be these causing your problems.

If EE pages are all still set to exclude from caching, I would start by looking at your .htaccess file.

January 31, 2015 at 11:32 am

WPSC may have added rules to your .htaccess file when you enabled a setting. Those rule will still be in place now even though you have removed the plugin.

So say there’s a rule that looks within a specific directory that is created on install of WPSC, but removed when you remove WPSC. That means that the rule becomes active just by installing the plugin.

There may not be, but its where I would start looking.

So, the logical thing is to not use it. Right? Except, of course, for the fact that my website is operating way too slowly. Thus, I want caching. It’s a Catch 22, isn’t it?
Do you have a suggestion for a different cache plugin that might not have the same problem that WPSC does in caching dynamic pages?

Installing another caching plugin to work around an issue with a caching plugin is just asking for trouble in my opinion.

You want to find the issue with the current setup and fix that.

Do you have a development copy of the site, possibly on the same server? If not I suggest creating one (a subdomain for example) and working there, to find the right settings for your site/server. Working live is not recommended and prevents a panic when settings are incorrect and users can not register.

January 31, 2015 at 12:39 pm

No, it will not remove the .htaccess rules, alot of plugins prefer not to remove them as .htaccess is often edited by the user, if they place rules within the block added by WPSC then un-install WPSC and it removes what it thinks (and should) be its own rules, the site breaks and the user (wrongly) blames WPSC.

You can see here:

https://wordpress.org/plugins/wp-super-cache/other_notes/

That .htaccess rules are not removed.

Whilst I can point you towards the right direction, we can’t really support other plugins and/or server config so you may need to post up on the WPSC forums for further help.

You will need FTP access to your site using an FTP client such as FileZilla or CyberDuck, within the root directory where WordPress is installed you.

You should see something like this – http://take.ms/oBcCI

This is a default WP .htaccess file – http://take.ms/U246N

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Be sure to keep a backup of the current file, but open that file with an editor such as SubLime Text (do not use MS Word or another Word Processor, they add formatting to files)

You may find your .htaccess has a block of rules for WPSC, separate from the code in the image above, try removing them and replace that file on your server.

January 31, 2015 at 2:40 pm

Hmm, which ftp client are you using to view the files?

February 2, 2015 at 9:51 am

No.

You set the exclusions manually.

So when re-installing just check those strings are still within do not cache list and WPSC should continue not to cache them.

February 2, 2015 at 10:20 am

Just check the wp-config.php file within the root of your site (same place the .htaccess was) and check that this line:

define( ‘WP_CACHE’, true );

has been added above this line:

require_once(ABSPATH.’wp-settings.php’);

It may be worth opening a ticket with bluehost to have them configure this correctly for you.

February 2, 2015 at 10:43 am

As long as:

define( ‘WP_CACHE’, true );

is above that line somewhere, it’s fine.