Important 11 posts on thread then blank page

Matias,

The page url is: www.fastingconnection.com/forum/40-Day-W...st-thread-fixed.html

and

www.fastingconnection.com/forum/40-Day-W...lled-water-fast.html

You can see the thread when not logged into the site. But when you sign in you can no longer view the page.



Gratefully
David

Very odd please try second url when signed in.

www.fastingconnection.com/forum/40-Day-W...lled-water-fast.html

Gratefully
David

Yes, I can see the issue.

What is your memory limit in PHP? It looks like there's nothing special in that page, so you may be running out of memory..? Kunena needs more than 32MB of PHP memory when running with CB integration - 64MB is recommended.

I had trouble locating any php.ini file on my cpanel file public_html/ file directory.
So I added this code to the .htaccess file

########## Added by David for increasing joomla memory to 64mb
#
php_value memory_limit 64M

However this did not work

I checked joomla/admin/systeminfo/phpinformation/phpcore/memory_limit is set to 128M but not sure if this is the memory you are referring to. Sorry I should be more acquainted with how to increase joomla memory size.

Thanks
David

daviddmf wrote

Sorry I should be more acquainted with how to increase joomla memory size.

G'day, David

I've spent the past two hours looking into this fascinating subject, partly for your benefit and also for mine.

Although a little off-topic - I'm not experiencing the 11-posts-on-thread-then-blank-page problem - I was inspired to do my research because of what Matias wrote.

Matias wrote

Kunena needs more than 32MB of PHP memory when running with CB integration - 64MB is recommended.

The point I want to make is that I am using CB 1.2.3 with K 1.6 on J! 1.5.20 with "only" 32M memory without any apparent difficulty as far as I can tell.

But, in investigating your implied question "How to increase PHP memory allocation for Joomla?", I came across this interesting thread: forum.joomla.org/viewtopic.php?f=47&t=275276 (read the thread, if only to have a chuckle at one of the stories entitled "The Twenty Steps").

I assume that the information one needs needs to know about "What is the PHP memory_limit for Joomla?" is obtained from your Administrator site: Help » System Info » PHP Information. This screen shows two values for memory_limit: the first column is the "local" value, the second column is the "master" value. I assume that the value in the first column is the value Joomla is attempting to allocate (rather than the actual amount being used). I also assume the the second column is some absolute limit applied by the global PHP configuration (php.ini). If my assumptions are incorrect, I hope that someone else can inform us what they really mean.

The advice given in the abovementioned topic was:

Add the following line of code (make it the second line in the file, immediately after "<?php") in each of the following files:

• index.php and the index2.php file in the main Joomla root folder; and
• index.php, index2.php, and index3.php (if you have a 2 and 3) files under the Administrator folder

I've done that and now, when I look at Help » System Info » PHP Information, I see

memory_limit 64M (local) 32M (master)

So, I'm still left wondering whether I really have the 64M that I want? :dry:

I posted a request to my webhosting provider (I'm still waiting for their reply) about whether I can increase the memory limit for PHP or not and, if it's possible, where is the php.ini file that I can change? In summary, it may not always be entirely possible for you to change the PHP memory_limit because your webhosting provider may not allow it. I'll let you know what is my experience from my w/host provider.

Sozzled chuffed that you would spend 2 hours of your precious time partly but not totally for my benefit. Looks like I have unwittingly opened up a can of worms here. Did read the Twenty Steps well worth the read (LOL) well perhaps Matias can shed more light on this mystery.

I wont upgrade to 1.6 just yet as I would like to find out if the memory is causing this issue.

Gratefully

David