I am using exactly what the VB updated the index file error reporting to:
(E_ALL & ~E_NOTICE & ~8192)
However, I'm still getting the below on the "home" part, there was no VB update to that index file. Should I use the same exact index file for both locations or ??
Doing a rundown of the errors now listed in the init.php file...... most are of this and some type of variant of it involving vbulletin:
That's the cause of the warning; the ampersand after the equals sign, before the keyword "new" is saying to assign the object to the $db variable by reference.
I have no idea, off the top of my head, if removing that "&" will fix the issue. It would remove this particular error, but might possibly cause others. If you try that, you should keep very careful track of exactly what you changed, so you can put it back like it was.
The best idea would be to upgrade the photopost plugin, I think. (Is it indeed a plugin? I don't have a "photopost" in any of my vB installations).
/!!\ mysql_ is deprecated --- don't use it! Tell your hosting company you will switch if they don't upgrade!/!!!\ ereg() is deprecated --- don't use it!
dalecosp "God doesn't play dice." --- Einstein "Perl is hardly a paragon of beautiful syntax." --- Weedpacket
Is it really cleaned up? motosouth.com/photopost/index.php is still broken from here.
/!!\ mysql_ is deprecated --- don't use it! Tell your hosting company you will switch if they don't upgrade!/!!!\ ereg() is deprecated --- don't use it!
dalecosp "God doesn't play dice." --- Einstein "Perl is hardly a paragon of beautiful syntax." --- Weedpacket
Oops... not the photopost page... it is a plug-in.
Main and forums page is set.
Don't know why photopost is still showing errors. I changed, well I had to add into the photopost's index.php file as there wasn't any error reporting?:
I guess I need to know where I'm supposed to add the error_reporting to photopost files.
Probably near the top; at the very least, put it before any of your out-of-date, deprecated code gets executed.
If there is some sort of central config file or something similar that all of the 'photopost' scripts include/require, you could potentially get away with only modifying that.
However, rather than all of these modifications... why not just modify your php.ini file to: 1) exclude E_DEPRECATED from error_reporting, 2) turn off display_errors, and 3) turn on log_errors?
Probably near the top; at the very least, put it before any of your out-of-date, deprecated code gets executed.
If there is some sort of central config file or something similar that all of the 'photopost' scripts include/require, you could potentially get away with only modifying that.
However, rather than all of these modifications... why not just modify your php.ini file to: 1) exclude E_DEPRECATED from error_reporting, 2) turn off display_errors, and 3) turn on log_errors?
I could do that. I just don't know how to write the code.
I added the below to the photopost index file with nothing before the error reporting:
Is there a way just to fix all these errors? I'm going to start removing that & in those lines above and see how that goes. I guess I'll still get that class_core error as I don't know what to do with that one.
I just got the photopost login info and will see if I can get an update for php5 to see if that fixes things too.
Thanks for having patience with me as this is all new for me.
Try to obtain an updated version of photopost? If whoever wrote it still cares about enough it to pay attention there should be one by now: PHP 5.3 has been around for three years - and will be reaching the end of its development lifecycle in March, with development concentrating on 5.4 and 5.5.
Originally Posted by php.net
[20 Dec 2012]
Please note that the PHP 5.3 series will enter an end of life cycle and receive only critical fixes as of March 2013. All users of PHP are encouraged to upgrade to PHP 5.4.
If photopost is a dead project, and you're not willing/able to update and maintain the plugin yourself, then two options are to hire someone to do the updating and maintenance of it, or to replace it with an alternative plugin that is still active.
Last edited by Weedpacket; 01-03-2013 at 10:14 PM.
It's not just photopost that gave these errors. It was also the vbadvanced page, which I just used the error_reporting code above so users wouldn't see it.
Vbulletin doesn't give any error and works fine with php 5.3.19
Reply With Quote
Originally Posted by jbomx363
Bookmarks