beat wrote:
This smells like a hidden php error (e.g. memory limit reached).
I uninstalled all CB Plugins and finally CB 1.1. I reinstalled CB 1.1 and then each module & plugin one by one, testing both Back and Front end ability to edit CB User Profiles. I had issues with the CB Gallery, CB Captcha and CB ProfileBook and tested these today in light of Beat's suggestion above. Thanks.
I also had an issue with CB Auto Welcome due to another (probably similar) error but it was the middle of the night, I was tired, I did not document. So it was unpublished during the following tests and I will handle it as a separate problem.
CB Gallery 1.0 RC2 caused an unspecified 'Server error' (Blank Page displayed with 'Server Error, contact your hosting provider' - or words to that effect. So I uninstalled it and used version 1.0 RC2 SR1 for tests.
***************************
Testing results:
Software Version
Joomla!: 1.0.13 Stable (Sunfire) 21 July 2007
CB: 1.1
CB Gallery: 1.0 RC2 SR1 July 2007 (Note: 1.0 RC2 resulted in unspecified 'Server errors' on CB 1.1 so was upgraded)
CB Captcha: 1.0 14.Feb.2007
CB Profile Book:
Note: default_language.php edited to add '?>' on last line to terminate it, but same effect occured as described below (debug off) both post and prior to updating.
***************************
Back End Tests (via Community Builder -> User Manager):
Plugin: Published?
CB Gallery Yes
CB Captcha Yes
CB ProfileBook Yes
caused error (blank page displayed, debug off) when editing profile.
caused this error when editing profile (debug on):
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 3840 bytes) in /hsphere/local/home/xxxxx/kiwicaching.com/includes/domit/xml_domit_lite_parser.php on line 1098
Plugin: Published?
CB Gallery Yes
CB Captcha Yes
CB ProfileBook No
caused error (blank page displayed, debug off) when editing profile.
Plugin: Published?
CB Gallery Yes
CB Captcha No
CB ProfileBook No
caused error (blank page displayed, debug off) when editing profile.
Plugin: Published?
CB Gallery No
CB Captcha No
CB ProfileBook No
caused no error when editing profile
Plugin: Published?
CB Gallery No
CB Captcha Yes
CB ProfileBook No
caused error (blank page displayed, debug off) when editing profile.
Plugin: Published?
CB Gallery No
CB Captcha Yes
CB ProfileBook Yes
caused error (blank page displayed, debug off) when editing profile.
Plugin: Published?
CB Gallery No
CB Captcha No
CB ProfileBook Yes
caused error (blank page displayed, debug off) when editing profile.
***************************
Front End (via Edit, Update Your Profile):
Plugin: Published?
CB Gallery Yes
CB Captcha Yes
CB ProfileBook Yes
caused this error when editing profile (debug on):
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 184320 bytes) in /hsphere/local/home/xxxxxx/kiwicaching.com/modules/mod_cblogin.php on line 267
Plugin: Published?
CB Gallery Yes
CB Captcha Yes
CB ProfileBook No
caused no error when editing profile
Plugin: Published?
CB Gallery Yes
CB Captcha Yes
CB ProfileBook No
caused no error when editing profile
Plugin: Published?
CB Gallery No
CB Captcha No
CB ProfileBook No
caused no error when editing profile
Plugin: Published?
CB Gallery No
CB Captcha Yes
CB ProfileBook No
caused no error when editing profile
Plugin: Published?
CB Gallery No
CB Captcha Yes
CB ProfileBook Yes
caused no error when editing profile
Plugin: Published?
CB Gallery No
CB Captcha No
CB ProfileBook Yes
caused no error when editing profile
***************************
Test Summary:
1. When any of the three plugins are published, memory error occurs on Back End (Community Builder -> User Management) when attempting to edit profile.
2. When all of the three plugins are published, memory error occurs on Front End (Edit, Update Your Profile) when attempting to edit profile.
***************************
I hope the tests will assist others. But it looks like CB 1.1 plus a combination of plugins causes issues with the default memory allocation as defined in the php.ini file.
My next task is to resolve that - Thanks Beat for pointing me in the right direction and also to Nant for his blog re the memory error. Googling it now
Post edited by: GenCuster, at: 2007/08/17 05:55