My error was caused by the colour legend hack, a friend found the source of the error, edited the code and it went away. He commented that it is something to do with the 4.2.2 release that is the real cause of the problem. As it seems to affect a whole lot of different hacks, I tend to agree with him about it being really a problem with the 4.2.2 release. Shouldn't have so may issues with all different hacks due to one upgrade, especially when it was something to do with forerunner xss exploit. Just my opinion. Peter
upgrade to 4.2.2 problem
Collapse
X
-
yeah that's the way, nobody uses that feature anyhow1 PhotoComment
-
I had to back out 4.2.2. Displaying errors is a huge security issue and should not of even been allowed to get through. I don't care if the plugins have depreciated code or not. Those errors do not display prior to 4.2.2 and should not display in 4.2.2. Poor quality control and customer services IMHO.
None of the suggested changes worked for me, so I went back to previous version.Comment
-
I had to back out 4.2.2. Displaying errors is a huge security issue and should not of even been allowed to get through. I don't care if the plugins have depreciated code or not. Those errors do not display prior to 4.2.2 and should not display in 4.2.2. Poor quality control and customer services IMHO.
None of the suggested changes worked for me, so I went back to previous version.Comment
-
same error in version 4.2.2
Warning: Function split() is deprecated in ..../forum.php(791) : eval()'d code on line 4Comment
-
-
-
Comment
-
Some further information on error displays in 4.2.2 ;
As part of the php compliance changes, error reporting in 4.2.2 was fixed to take account of the new strict & deprecated errors added in php 5.x
A side effect of this is that old (existing) errors that were not showing up may also now get displayed.
All of the errors we encounted during testing were corrected, but there may be more.
If you encounter such an error, then please log it in the vB4 Jira project, so we are aware of it.
If you need to disable error displays you can do the following ;
Add the following line to your config.php ; PHP Code:
define('SKIP_DS_ERRORS', true);
This will bypass the additional reporting added in 4.2.2 (i.e work as previous versions have done).
If necessary, you can also add the following to your config.php ; PHP Code:
define('SKIP_ALL_ERRORS', true);
This will bypass all (non fatal) error reporting.
Note that in vB 4.2.3, the additional reporting is not enabled by default, so the above options are not required (and wont do anything).---
To Be Smart ، Play With Smarter
Mahmoud ElklmawyComment
Related Topics
Collapse
-
by enCydeHi,
I have a problem here and I have tested everything but my site still loads slow at the start but not when I'm logged in. First I thought it was the twitter feed and facebook module but...-
Channel: Support Issues & Questions
Thu 1 Aug '13, 10:06pm -
Comment