Search results

ahhh .htaccess support. ok that makes perfect sense. Thanks for the quick follow up!

We run a standard Enterprise Litespeed with multiple cpu license for our Wordpress installation using WP Super Cache. We have not configured anything special specific to Wordpress or WP Super Cache, however. I saw the announcement of the template for a WP Super Cache installation and was...

Disabling APC did not work for us, it was necessary to disable Zend. APC is working without issue for us.

@eva2000: to clarify, if I am already serving static files via WP super cache that adding LiteSpeed cache provides no additional value?

Thanks for the tip. Did not know it was that easy. Are you running LS Cache with a Wordpress installation? I'm trying to figure out the right rewrite rules that I should be using to get it to play nicely with WP SuperCache and LS Cache. Thanks in advance.

I am running LiteSpeed Enterprise Edition 4.1.4 and trying to get LiteSpeed Cache setup to work with my Wordpress 3.2.1 and WP Super Cache 0.9.9.9 configuration. My goal would be that WP Super Cache produces the static files and they are served using LS Cache as suggested by NiteWave in this...

Thanks. Can you provide any specific guidance on how the exclude works? For example, is this what I would need to exclude all wpadmin requests from being cached? 
# excluding certain URLs RewriteCond %{REQUEST_URI} !/(wpadmin) \.php$


@webizen: Any chance of getting a general guide for Wordpress setup using LiteSpeed Cache. Specifically in dealing with wp-admin and logged in user requests.

After a bit of research (and much effort by Mike) we may have this sorted out. Even after using 3.019 of APC we were still seeing issues, turns out a conflict with ZEND was the culprit in this case. Once the ZEND extension was disabled everything has been running pretty smooth. I'll...

@webizen: In reading through the forums here I tested updating the php.ini with: apc.enabled = 1 apc.shm_size = 48 apc.include_once_override = 1 apc.mmap_file_mask = /tmp/apc.XXXXXX This made things a little better in that it is not consistently throwing 503 , but still seeing them...