Hi,

This is a common issue. Hosting company will put you on a wheel, giant wheel when we ask more especially php.ini and httpd config change.

To you question php.ini file you should look at ./usr/local/lib/php.ini,

My experience suggesting me that 90% of blog software will give you same type of troubles. I work on wordpress/wordpress mu, nucleous and be2 (consulting work).

I found b2e is more stable and near to my nature. Good support forum. So stick to one and get more from your hosting company.

Good luck.
zb

zblogwala wrote:

To you question php.ini file you should look at ./usr/local/lib/php.ini,

I don't think that I have that set up on my directory, at least what I can see; does that mean that the provider must put the file on?

They said:
Tech support wrote:

You would need the php.ini file in the directory where you need those settings applied as the custom php settings do not propagate down to lower folders.

Which does not seem to fit with your lib folder??

Thanks,
Perry

You put the php.ini file in the folder where you have the blog software, or in the root of your server.
You should be able to check with phpinfo() if the changes did take place. What zblogwala is referring to is a host that doesn't allow you to change some settings and particular the memory settings.

Good luck

Afwas wrote:

You put the php.ini file in the folder where you have the blog software, or in the root of your server.

OK, thats /blogs/ as unpacked from the distribution, right?

Well, that's where I put it, and it made no difference (I was using the System page in b2Evolution to check), which is why I wondered if it should go into a different folder??

Afwas wrote:

You should be able to check with phpinfo() if the changes did take place. What zblogwala is referring to is a host that doesn't allow you to change some settings and particular the memory settings.

Maybe that is the case, as I'm having trouble getting the settings accepted.

Thanks,
Perry

scribbly wrote:

Afwas wrote:

You put the php.ini file in the folder where you have the blog software, or in the root of your server.

OK, thats /blogs/ as unpacked from the distribution, right?

Thanks,
Perry

Yeas, and you can also try the directory where the 'blogs' folder is located. That will be the root, I guess.

Good luck

Afwas wrote:

Yeas, and you can also try the directory where the 'blogs' folder is located. That will be the root, I guess.

Actually, the techs at LunarPages have just suggested:
LunarPages wrote:

As far as I can tel the only solution would be to place copy of the php.ini file within every b2Evolution directory.

Hmmm: that's quite a few directories, eh? :-/

Can you upgrade to php5? If so, try it.

OK, this has been solved with the extremely friendly and helpful actions from LunarPages HelpDesk...

Issue 1: On Windows IIS PHP must not be run as an ISAPI extension
Issue 2: php.ini must be located in the root directory of the website
Issue 3: cgi.force_redirect = Off had to be the first instruction

php.ini files in other sub-directories will not be processed, i.e. there is only one per site (although they did offer a few suggestions on how to get around this, but I didn't think that was necessary).

Hooray :p :p :p :p :p

Well done and thanks for reporting back to this topic.

Happy blogging

Afwas wrote:

Well done and thanks for reporting back to this topic.

Thanks. But I have to say that the only thing I'd accept a "Well done" for was the persistence. I just kept asking the questions until they were picked up by someone who knew what he was doing (inside out and back to front!)

For anyone else struggling with a HelpDesk: Persistance is sometimes the only card you've got to play!!

And anyone else on IIS (I gather not many ;) ), I'd hoped the information may be of some use.

Afwas wrote:

Happy blogging

Thanks: I love b2Evo!!