Author: humma
Description:
phpinfo show eAccelerator but mediawiki installer can't found it.
Version: 1.17.x
Severity: normal
OS: Linux
Author: humma
Description:
phpinfo show eAccelerator but mediawiki installer can't found it.
Version: 1.17.x
Severity: normal
OS: Linux
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Invalid | None | T35693 Fix outdated interface text in installer | |||
Resolved | None | T31747 Not found installed eAccelerator |
humma wrote:
mediawiki 1.17.0-1
lighttpd 1.4.28-6
php-fpm 5.3.6-4
eaccelerator 0.9.6.1-1
It seems, from a quick google, there is some funky things about eaccelerator_get, and them being disabled
http://adminuser.wordpress.com/2008/01/15/fatal-error-unknown-function-eaccelerator_get-in-somefile/
humma wrote:
yes, i changed script to check eaccelerator_info instead of eaccelerator_get. Is it good way?
Seemingly not
Unless I'm mistaken, if there isn't the get/put functions, this caching isn't going to be usable, is it? :/
Possibly the installer should detect that eaccelerator is present but the caching functions are disabled, and offer a link to info about that option.
Honestly though I'm very leery of any of the opcode-cache-plus caching options like this; they're already *totally unsafe* to use if you use any command-line scripts or have multiple web servers, and that can easily be something that a user isn't even aware of if they're on shared hosting. I tend to advocate removing support for eAccelerator-based caching entirely.
I have the same problem with eAccelerator 0.9.6.1 (which I am forced to use)
"Removed eAccelerator shared memory caching entirely"
What does that mean? eAccelerator is not supported anymore?
(In reply to comment #9)
What does that mean? eAccelerator is not supported anymore?
Yes, that's exactly what it means.