Flush Cache

[kolenoblata]

Hello,

Just installed 2.0.1 lite version for 3.8 forum . Everything is ok except Flush Cache. When I click on it I don't get anything, just blank field. Also, when I go to system test, flush cache just going and going

Edit:
Another problem. When I try to edit eny template I am geting blank page and edits are not done.
Uninstall mod until you solve this problem.

 

[Deceptor]

Are you running eAccelerator or XCache?

 

[kolenoblata]

I am running XCache

 

[Deceptor]

Chances are your XCache requires authentification. I recommend reading the FAQ provided in the vbulletin.org thread which covers this: http://www.vbulletin.org/forum/showthread.php?t=237325

If you have any questions regarding the FAQ let me know

 

[kolenoblata]

Nope, I did that and problem is still there:

I can see on VB.org that lot of people have same problem.

 

[Deceptor]

Nope, I did that and problem is still there:

I can see on VB.org that lot of people have same problem.

The people on vB.org have the same setup, they need to configure the username/password. I presume you've done that in vboptimise/config.php and turned on XCache Authentification in the settings?

 

[kolenoblata]

I have download vboptimise/config.php , open it, add username and password for Xcache from php.ini, save it and upload to server again on same spot. After that I went to vboptimise setings in ACP and check XCache Authentification to "yes", I don't know what to do else.

 

[Deceptor]

The password you entered, it cannot be the exact same thing you see in php.ini - that password is the md5 version, you need to enter the "plain-text" password into the config.php file (so if your password is "hello", enter that)

 

[kolenoblata]

Actualy, password was blank ( xcache.admin.pass = "" ), I added only username

 

[Deceptor]

That'll be why, if your XCache has admin authentification on, it needs a password too. Keep in mind the password in php.ini needs to be md5'd.

 

[kolenoblata]

Than what should I do? I added what I saw in php.ini.

 

[Deceptor]

You need to assign a password to XCache in your php.ini (in md5 format), and assign that password to the config.php (in plain-text format). Or you can turn off admin authentification in php.ini (it's only required really if you have the xcache statistics script live).

 

[kolenoblata]

So turning it off will not impact to security?

 

[Deceptor]

No, unless you have some web-accessible script that can control XCache.

 

[kolenoblata]

Ah, it is done, thank you for support

 

[Deceptor]

Not a problem Enjoy!

 

[hydn79]

yup xcache auth for flush issue! Is xcache still the best option for non-windows installs? So glad there wincache. If your on windows then switch xcache out with wincache its faster.

 

[Deceptor]

XCache is the better option for single-server installations, otherwise Memcache prevails. It's a close-call between the two but if you're anal about it you'll notice XCache uses a little bit less run-time memory than Memcache because it won't be communication with a socket server, but really the difference is near 0 in most circumstances.

 

[SSSlippy]

Recommendation as I found this the best way to work around this issue. Remove xcache default password protection and instead use apache ability to password protect a directory. This means that the admin panel for xcache still has a password/username but the flush cache from vb admin cp will still work. This is of course you are using the web based admin panel for xcache.

I personally have mine behind https and a user/password login.

 

[Deceptor]

Recommendation as I found this the best way to work around this issue. Remove xcache default password protection and instead use apache ability to password protect a directory. This means that the admin panel for xcache still has a password/username but the flush cache from vb admin cp will still work. This is of course you are using the web based admin panel for xcache.

I personally have mine behind https and a user/password login.

Requires configuration on the user end still unfortunately, but I agree . The next update I'm working on provides an alternate routing for the Flush mechanism so it can bypass -any- protection the extension is configured with.