Member
I've been told to install the nightly build to get the MaxSpace stuff to work correctly, but I'm getting an mbstring warning on loading. I think it's actually causing some problems for me, else I would just ignore it.
If I do a clean install, everything's fine. As soon as I upgrade to the nightly build, my mbstring changes from UTF-8 to ISO-8859-1.
My config.php file says UTF-8 and the php.ini file in my root directory says UTF-8, and my other (older) installs of stable ZP say UTF-8. Any idea how to change my nightly build version to UTF-8?
Thanks!
If I do a clean install, everything's fine. As soon as I upgrade to the nightly build, my mbstring changes from UTF-8 to ISO-8859-1.
My config.php file says UTF-8 and the php.ini file in my root directory says UTF-8, and my other (older) installs of stable ZP say UTF-8. Any idea how to change my nightly build version to UTF-8?
Thanks!
Member
The place to change this is in your PHP.ini file. This setting controls the internal encoding of characters in PHP. So, if you are using standard American you will have no problem. It is just if you have accented characters or are using a locale different from en_US that you might have problems.
The diagnostic in new to the nightly builds, so that is why you did not see anything when you installed straight 1.2.1. It is very unlikely that anything has in your configuration, so If things worked before they still should work.
At least for my ISP, I have to edit the PHP.ini file on the server site, putting one in the root folder does no good.
The diagnostic in new to the nightly builds, so that is why you did not see anything when you installed straight 1.2.1. It is very unlikely that anything has in your configuration, so If things worked before they still should work.
At least for my ISP, I have to edit the PHP.ini file on the server site, putting one in the root folder does no good.
Member
hmm... okay, thanks. i've edited the php.ini file on the server site, so I'll check with my ISP to see if i need to put it somewhere else.
I was wondering if it had anything to do with this:
When I swapped out printCustomSizedImageMaxSpace and tried to use printCustomSizedImageThumbMaxSpace, I got this 500 server error:
http://www.stanats.com/gal02/index.php?album=testalbumâ„‘=03.jpg
I thought that weird character might be a mbstring problem.
But I've looked at the printCustomSizedImageThumbMaxSpace function in the nightly build, and I think somebody goofed. It is written this way:
function printCustomSizedImageThumbMaxSpace($alt='',$width,$height,$class=NULL,$id=NULL) {
printCustomSizedImageThumbMaxSpace($alt,$width,$height,$class,$id, true);
}
Shouldn't that second occurence be "printCustomSizedImageMaxSpace" instead of "printCustomSizedImageThumbMaxSpace"? The function is currently calling itself.
I was wondering if it had anything to do with this:
When I swapped out printCustomSizedImageMaxSpace and tried to use printCustomSizedImageThumbMaxSpace, I got this 500 server error:
http://www.stanats.com/gal02/index.php?album=testalbumâ„‘=03.jpg
I thought that weird character might be a mbstring problem.
But I've looked at the printCustomSizedImageThumbMaxSpace function in the nightly build, and I think somebody goofed. It is written this way:
function printCustomSizedImageThumbMaxSpace($alt='',$width,$height,$class=NULL,$id=NULL) {
printCustomSizedImageThumbMaxSpace($alt,$width,$height,$class,$id, true);
}
Shouldn't that second occurence be "printCustomSizedImageMaxSpace" instead of "printCustomSizedImageThumbMaxSpace"? The function is currently calling itself.