vb.org Archive - PHP error

Page 2 of 3

Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)

- - PHP error (https://vborg.vbsupport.ru/showthread.php?t=316329)

ozzy47

12-31-2014 08:30 AM

Quote:

Originally Posted by Snowhog (Post 2529703)

We were also getting php errors concerning preg_replace() /e being depricated and to use preg_replace_callback() instead. For each reported occurrence, I made the change in the affected .php file. Would I not have had to do that with this fix??

Probably a error with a mod, see if you can find out which one.

Snowhog

01-01-2015 09:11 PM

ozzy47 -

We are now running 4.2.3 Beta 3. Should I undo the fixes identified and made in this thread?

ozzy47

01-01-2015 09:13 PM

You can try, I am not sure if they are needed or not, as I have not upgraded any of my sites to 4.2.3 just yet.

Snowhog

01-01-2015 09:24 PM

I guess my real question should have been, is it necessary to undo the changes? So far, everything is working as expected. Rule of thumb is, "If it ain't broke, don't fix it." As nothing is presenting as broke, I wont 'fix' the 'fixes' I fixed. :eek: :D

ozzy47

01-01-2015 09:27 PM

Well the change I told you to do in post #2 would have been overwritten when you loaded the new files to the server. As well as any other changes you made to the core files. :)

Paul M

01-01-2015 09:55 PM

Quote:

Originally Posted by ozzy47 (Post 2529695)

In includes/class_core.php locate lines 5683-5685 which should be this.

Code:

 case E_NOTICE:    

        // Just ignore these completely //    

    break;

And change it to this.

Code:

case E_NOTICE: 

   case E_STRICT;     

   case E_DEPRECATED;        

    // Just ignore these completely //  

break;

This is/was completely unnecessary.

To turn off the extra warning/error reporting in 4.2.2 use SKIP_DS_ERRORS - see this post.

Its already fixed in 4.2.3.

Snowhog

01-01-2015 09:56 PM

Ah, true. I like that even better, as that means that all is working as it should. No bandaids. Cool.

ozzy47

01-01-2015 09:56 PM

While it may be unnecessary, I prefer not doing the hiding of all the warnings if at all possible. :)

Paul M

01-01-2015 09:59 PM

Um, you do realise thats exactly what your change did, just by an unnecessary edit to a core file rather than by the designed method. ;)

ozzy47

01-01-2015 10:00 PM

Yes, but that was for one error only, or did that disable all of them as well?

All times are GMT. The time now is 04:03 PM.

Page 2 of 3

Show 40 post(s) from this thread on one page

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01079 seconds Memory Usage 1,730KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (2)bbcode_code_printable (2)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)pagenav (1)pagenav_curpage (2)pagenav_pagelink (1)post_thanks_navbar_search (1)printthread (10)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start pagenav_page pagenav_complete bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: