Re: [TYPO3-english] E-Accelerator bug when configuring extension

2012-09-02 Thread Tomasz Krawczyk
W dniu 2012-07-19 10:29, Oliver Klee pisze: Hi, Am 19.07.2012 08:01, schrieb Tomasz Krawczyk: Is eAccelerator still maintained? Its last version is from 2010. I can't create an account on its trac. The forum on the Google is dead. I may be wrong but it looks a father has abandoned baby.

Re: [TYPO3-english] E-Accelerator bug when configuring extension

2012-07-19 Thread Tomasz Krawczyk
W dniu 2012-07-18 23:02, Oliver Klee pisze: Hi, Am 18.07.2012 21:47, schrieb Loek Hilgersom: We recently had stubborn segmentation fault errors with APC on a project running TYPO3 4.6. Now switched to Xcache with no problems since - for what it's worth, YMMV. I had exactly the same

Re: [TYPO3-english] E-Accelerator bug when configuring extension

2012-07-19 Thread Oliver Klee
Hi, Am 19.07.2012 08:01, schrieb Tomasz Krawczyk: Is eAccelerator still maintained? Its last version is from 2010. I can't create an account on its trac. The forum on the Google is dead. I may be wrong but it looks a father has abandoned baby. That's my impression, too. Oli -- Certified

[TYPO3-english] E-Accelerator bug when configuring extension

2012-07-18 Thread Éric Thibault
Hello to all! We've just installed E-Accelerator in our developpement system with comments and now when we try to configure our extensions in the extension manager, we get this error: Cannot use object of type stdClass as array in

Re: [TYPO3-english] E-Accelerator bug when configuring extension

2012-07-18 Thread Loek Hilgersom
Hi, We recently had stubborn segmentation fault errors with APC on a project running TYPO3 4.6. Now switched to Xcache with no problems since - for what it's worth, YMMV. Loek On 18-07-12 16:29, Laurent Cherpit wrote: Hello, Use APC -

Re: [TYPO3-english] E-Accelerator bug when configuring extension

2012-07-18 Thread Oliver Klee
Hi, Am 18.07.2012 21:47, schrieb Loek Hilgersom: We recently had stubborn segmentation fault errors with APC on a project running TYPO3 4.6. Now switched to Xcache with no problems since - for what it's worth, YMMV. I had exactly the same experience (and the same solution ...). :-) Oli --