See if [url=http://manual.b2evolution.net/FAQ_:_After_Installation#When_I_do_xyz_I_just_get_a_blank_page_or_only_a_half_page]this document helps[/url]

Looked up that file... thanks...

now I get a 500 error... guess I did something wrong... will have to contact my hosting provider...

:-(

After contacting my hosting provider, put in a php.ini file on the site... that did the trick... extended the memory usage and the error message went away... thanks for the help...

Regards

Hi I'm new to all this... I installed my blog on Monday, and posted away. All was going super well. Then suddenly yesterday (after 2 days), I got a really weird error when I tried to view my blog. On reading up, I found that php.ini needed some editing... but couldn't find it in my blog folders, and realized this is a file that the webhosts probably have on the root of their server. So I emailed them. THey sent me a friendly email back to say they'd been having problems with php on their server, please be patient. This evening I went in, and my blog was back, but only the last posting was visible, and I got the same error as posted by Thomas810.
So now, I'm wondering about the last post here... you say, Thomas810, that you "put in a php.ini file on the site"... does that mean you got a php.ini on the /blog folder of your site?
Should I contact my provider and ask for a "copy" of this, or what?

don't worry, I came right... I think... emailed my host and was told their admin has to do it on the server... so I wait in anticipation!

PHP can be set up in various ways. One popular method is using a standard php.ini file for PHP and allowing users to create their own. This second php.ini file goes in the root of the user folder and overrides the standard settings. It's even possible to set PHP up to have a different php.ini file in every folder ;)
One of the things that can be managed in php.ini is the amount of memory a process can take. If that's limited to 8Mb there will be a problem with B2evolution. See the FAQ for details.

Good luck

I had this problem this morning after upgrading last night to the "Monument Valley" version. Followed the above link and commented out the ini_set line in blogs/conf/_advanced.php. Interesting to note that it's now been upped to a 32MB limit.

All running smoothly again :)

Oh - just noticed this is under the 1.XX version area, so no wonder the limit has increased over the years. Ahem.

lxsparks wrote:

Oh - just noticed this is under the 1.XX version area, so no wonder the limit has increased over the years. Ahem.

*unloads gun* :D

¥