RichieBoy67 |
02-12-2014 07:10 PM |
Quote:
it needs to be like this
case E_NOTICE:
case E_STRICT:
case E_DEPRECATED:
// Just ignore these completely //
break;
|
I think that is what I posted? lol i was scratching my head to see what I messed up.
I think the single class_core should fix it but it will not fix his memory error. only the depreciation warning he is seeing in the maintenance page.
--------------- Added 12 Feb 2014 at 15:11 ---------------
Quote:
Originally Posted by Eq4bits
(Post 2480679)
Yes, sir ;)
I'm submitting ticket to host. Same host I've used the past 10 years with only 1 issue as problematic as this one seems to be, so don't suggest changing hosts - these guys have excellent customer service and response times avg. 15 minutes.
--------------- Added 12 Feb 2014 at 15:10 ---------------
Are you still up? I can send the files but where do I send them? Can do so quickly once I know where to send
|
So the only change you made was upgrading to Vbulletin 4.2.2? Are you sure you uploaded all the files correctly and have permissions set?
You can also optimize the database using phpmyadmin and then try to run the counter. The memory issue is not being caused by the depreciation warnings. The issue is that some of your posts are very, very large and this is causing you to go over your memory allocation.
|