[RESOLVED] Weird problem after upgrade.

[RichieBoy67]

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 ---------------

Originally Posted by Eq4bits

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.

[ForceHSS]

Originally Posted by RichieBoy67

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 20:11 ---------------




So the only change you made was upgrading to Vbulletin 4.2.2?

you had ; after
case E_STRICT;
case E_DEPRECATED;

should be
case E_STRICT:
case E_DEPRECATED:

[RichieBoy67]

Originally Posted by ForceHSS

you had ; after
case E_STRICT;
case E_DEPRECATED;

should be
case E_STRICT:
case E_DEPRECATED:

Ahh, I see now. Thanks, I thought I was losing my mind. I just may have been right too. lol

[ForceHSS]

Originally Posted by RichieBoy67

Ahh, I see now. Thanks, I thought I was losing my mind. I just may have been right too. lol

I have always done it that way seems to fix the problem. Maybe a good coder could answer that

[RichieBoy67]

yeah, actually I am looking at the post where i got that from and it appears it is the way I was using it. This is the way I have been doing it on at least 7 or 8 sites and it has resolved the warnings. I have done the social group file edits as well at times. That is probably the better way to fix it as it is stopping the issue causing the warnings where the clas_core is just ignoring them. I am not sure if it matters though in any noticeable way.

http://www.vbulletin.com/forum/forum...81#post4000681

[ForceHSS]

Originally Posted by RichieBoy67

yeah, actually I am looking at the post where i got that from and it appears it is the way I was using it.

http://www.vbulletin.com/forum/forum...81#post4000681

seen that, have no idea where i got my one from but it does work

[RichieBoy67]

Originally Posted by ForceHSS

seen that, have no idea where i got my one from but it does work

All is well that ends well . Apparently they both work. Now we need an expert coder to come in and explain why.

[Eq4bits]

Originally Posted by RichieBoy67

What are you using for a host? A shared hosting account? is this a new server you are on or something?

You are using vb3 plug ins on a vb4.2.2 site?

Don't use Yahoo yui. Use Google or nothing in that setting.

As for the rest they are not going to really impact this issue much that happens when rebuilding a database table.

Did you try rebuilding thread/post cache using a smaller amount of posts at a time?

Shared server, been with host for 10 years............ on save server for last 5 or more, host recently did all kinds of upgrades too.
no I am NOT using vB3 plugins on my vB4.2.2 site - that is what tech support pointed me to - certain optimization tools that I can't use
I have it set to Google, it WAS the Yahell but I changed it earlier today.

[RichieBoy67]

Did you run the repair/optimization using phpmyadmin?

[Eq4bits]

Originally Posted by RichieBoy67

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.

Yup and Yup to your first questions
And yes, I've been optimizing via vB admincp AND phpMyAdmin.
there are some very large posts, I may have to go in and split them into several if this is the case. Just never had a problem until this upgrade. =S