Wedge

Public area => Bug reports => The Pub => Archived fixes => Topic started by: Bunstonious on June 30th, 2014, 01:11 AM

Title: Caching Purge
Post by: Bunstonious on June 30th, 2014, 01:11 AM

Just a few issues I get since updating recently (I haven't updated much in the last few months):

1) Whenever I try to purge the cache I get a blank screen.
2) Sometimes when I try and save the cache settings I get the same thing.

I am using XCache on the same UBuntu machine I usually use.

Edit: I haven't had time to test extensively, will do soon. I have also tried with and without action pretty URLs and same thing, just a reminder though I use HTTPS.

Title: Re: Caching Purge
Post by: Bunstonious on June 30th, 2014, 01:36 AM

I get a 500 error in IE9.

Title: Re: Caching Purge
Post by: Bunstonious on June 30th, 2014, 02:04 AM

I also get it when I "do" any action, eg creating a board.

Title: Re: Caching Purge
Post by: Bunstonious on June 30th, 2014, 05:28 AM

So it works with a brand new site, will need to do additional testing when not at work.

Title: Re: Caching Purge
Post by: Pandos on June 30th, 2014, 08:25 AM

The caching feature is working rock solid.

The only thing I could imagine is that it's due to https.
Does your logs say something?

Title: Re: Caching Purge
Post by: Bunstonious on June 30th, 2014, 11:19 AM

Nah i still need to investigate.

A fresh install works fine over HTTPS, and the logs say nothing :(

Title: Re: Caching Purge
Post by: Bunstonious on June 30th, 2014, 03:49 PM

Its weird...

I get loads of this error when I try.

[Mon Jun 30 23:45:47.001009 2014] [:error] [pid 9542] [client 10.1.1.18:57119] PHP Fatal error:  xcache_count(): xcache.admin.user and/or xcache.admin.pass settings is not configured. Make sure you've modified the correct php ini file for your php used in webserver. in *EDITEDPATH*/forum/core/app/Subs-Cache.php on line 1753, referer: https://forum.bunston.net/

Title: Re: Caching Purge
Post by: Bunstonious on June 30th, 2014, 04:26 PM

After researching the documentation it was an inaccurately setup "admin auth" for xcache... :^^;:

Carry on Gents!