What's New ? 404 Error!
 

All right, so my server is now updated to PHP 5.3.6.

vBulletin is at 4.1.3.

But now whenever I click the What's New tab, or the New Posts button, I get a 404 error.

So what's up here?

I don't seem to have any plugins/products that cover this particular function.

Any guidance?

Peace,
Gene

Did you make any modification?

Not before installing PHP 5.3.6.

I removed a few products that might impact search.

But search in general is broken. Rebuilt it, but no result.

Peace,
Gene

Check your error_logs (if you don't know where they are, ask your host)

This help?

[04-May-2011 10:07:58] PHP Warning: set_error_handler() expects the argument (vb_error_handler) to be a valid callback in /home/theparac/public_html/forum/includes/init.php on line 52
[04-May-2011 10:07:58] PHP Fatal error: Class 'vB_Registry' not found in /home/theparac/public_html/forum/includes/init.php on line 55
[04-May-2011 10:08:00] PHP Fatal error: Class 'vB_Bootstrap_Forum' not found in /home/theparac/public_html/forum/global.php on line 19
[04-May-2011 10:08:05] PHP Fatal error: Call to undefined function fetch_relevant_notice_ids() in /home/theparac/public_html/forum/includes/class_bootstrap.php on line 953

Peace,
Gene

It sounds like you are missing a file. Reupload all your default files.

OK, I backed down to PHP 5.2.17 and it seems to work. But isn't vBulletin 4.1.3 supposedly PHP 5.3.x compatible? I need some guidance here.

Peace,
Gene

I run PHP 5.3.6 just fine with vb 4.1.3. I would contact the host. And disable your plugins to be sure no product is causing that.

I asked my admin; he was stumped.

I reinstalled vBulletin, no change.

Do those error messages signify something?

Peace,
Gene

Did you disable your plugins to see if a mod COULD be conflicting with things since you upgraded? Whether you think a mod should or shouldn't mess things up won't be certain until you try that.

What about the error message? Any clues there? I disabled anything and everything that had impact on a search function.

Peace,
Gene

It doesn't have to be a mod that deals with search directly. Disable ALL of them and add them back one at a time until you find the culprit.

make sure its not any plugins or anything causing this, its very easy to test this.

Go into your config.php file, directly under

add:
To enable again just remove the line or add // infront of it.


Hope this helps.

~C

Been there, done that. Didn't work.

Here's the history.

1. I was running PHP 5.3.x and it worked fine.

2. I downgraded to PHP 5.2.x because we installed a Mambo site on my server, and it wouldn't work otherwise.

3. After finding the fix for PHP 5.3.x and Mambo, I upgraded to PHP 5.3.6.

4. No plugins/products were changed over this period of several months after the original PHP changeover.

5. Disabling all products didn't change anything.

So where do we go from here?

Peace,
Gene

Nowhere. Talk you your host is all you can do now or download to PHP 5.2.

I'll try 'em.

Peace,
Gene

--------------- Added [DATE]1304553442[/DATE] at [TIME]1304553442[/TIME] ---------------

Here's the solution.

Zend Optimizer is evidently not compatible with PHP 5.3.

But cPanel's EasyApache installs it anyway.

When I removed that module and rebuilt Apache and PHP, search in vBulletin worked fine.

The host didn't have time to help.

Maybe you can put this in your memory bank in case anyone else complains.

Peace,
Gene

EasyApache will only install that if you have it checked and it was installed before. I use EasyApache and have not had that issue at all.

In theory, when you change PHP versions, it should uncheck things that aren't compatible and not allow them to be installed.

Peace,
Gene

Well, how would it know it isn't compatible with vbulletin, when it is compatible with other things?

If you read my first message you'd see what happened. It's cause and effect. When Zend Optimizer was disabled, the search functionality was restored. Why do I have to explain this?

Peace,
Gene

I was commenting in this asinine theory:
But, no biggie. You won't hear from me the next time you do something ignorant.

You provided no help. Nobody did. I worked it out. I'll report the EasyApache bug to cPanel.

The only ignorance I see he is the reflection of your nasty attitude. Take a sedative, or just don't respond unless you have something useful to contribute.

Gene

Go ahead and report a non-existent bug and see what they tell you.

I've reported bugs to cPanel previously that have been accepted and fixed. It does appear you're just trolling for trouble; if you pulled this nonsense on my forums, you be banned by now. Have a nice day. I'm done with you, and I hope the moderators will agree.

Gene

But it is not a bug. You're not understanding. There is no way that EasyApache can know that Zend Optimizer doesn't work with certain things when it will work fine with other things. That was the only point I was making.

But, I digress. You have the mindset that it is a bug, so until they straighten you out that it is not a bug, nothing else can be said. Good luck with that.