PDA


View Full Version : RC1 Error

Blaminator
08-01-2005, 10:45 AM
Hi there, CMPS seemed to work fine on vb 3.5 beta 4, but this morning I upgraded to vb 3.5 rc1, now after making the global.php file edit, i get this error in cmps_index.php:


Warning: Division by zero in /includes/functions.php(4174) : eval()'d code on line 48



Help please :/
ConqSoft
08-01-2005, 10:47 AM
Hmm. Been working fine with me in RC1. Does the error go away if you replace global.php with the "stock" one? If so, I'd try making your edits again.
Blaminator
08-01-2005, 11:03 AM
When I replace global.php with the original one, i get this error:



Fatal error: Call to undefined function: print_portal_output() in /home/blamina/public_html/index.php on line 35
ConqSoft
08-01-2005, 11:08 AM
Right, but does your Forum now work? Or, were you only getting the first error on the CMPS page?
Blaminator
08-01-2005, 11:14 AM
I Was only getting the first error in the cmps page
ConqSoft
08-01-2005, 11:16 AM
Sorry, dunno.... I've never seen that error.
Blaminator
08-01-2005, 11:17 AM
Eek, well, let's just hope somebody knows what to do
Brian
08-01-2005, 12:31 PM
Try turning off any plugins you've added to vB and see if you still get the error.
FleaBag
08-04-2005, 07:24 PM
Right I just upgraded to vBulletin RC2... And now I get the exact error mentioned above. I don't see what turning my plugins off is going to do for me since it worked fine with RC1?

Cheers. :)
FleaBag
08-04-2005, 07:34 PM
OK so I started fresh with a new global.php and got the standard no edits to global.php error that you'd expect. Did the first edit and refreshed index.php - same error, second edit and refreshed - same error. Thirs edit and refreshed - that's where the error below comes in. So does this mean it's something to do with the code in the third edit?

Warning: Division by zero in /includes/functions.php(4191) : eval()'d code on line 10

Obviously now noticed that my error is slightly different, with a different reference in the functions.php file, and in the line the error is occuring on.
ConqSoft
08-04-2005, 07:35 PM
Did you disable all your plugins, just to see?

It has worked fine with RC1 and RC2 for me, so I'm not sure what the problem could be with yours.
FleaBag
08-04-2005, 07:37 PM
OK I'll go for that option now, can't hurt hehe. :D

Should I disable the products too?
FleaBag
08-04-2005, 07:41 PM
OK I disabled all of the plugins [sorry, I should have done that as directed to start - and hell did it take a long time, wish there was a check/uncheck all option!] and I now get blank white page - about to do a template re-install to see what it does.

On an off note for a moment, why are the template re-installs required after every vB upgrade - isn't there a way around that?
FleaBag
08-04-2005, 07:43 PM
After a new template installation it works. Baffling... I wouldn't have thought it possible for the plugin to cause the problem? But what do I know eh!?
ConqSoft
08-04-2005, 07:43 PM
about to do a template re-install to see what it does.

On an off note for a moment, why are the template re-installs required after every vB upgrade - isn't there a way around that?

That should fix it.

Yep, for now you have to do that. I think Brian said that with 3.5 there's a way to do it so that won't be required, so maybe CMPS 2 RC3 (or Gold) will do that.
FleaBag
08-04-2005, 07:56 PM
Ah right I see... I was sure I used to have some hacks installed who's templates survived the upgrade, a fair few in fact?

And I've now re-enabled all plugins, and the CMPS is still working?
xxskullxx
08-05-2005, 12:15 AM
I had the same exact error right after upgrading. All I had to do was re-install the templates. No big deal. Didn't need to disable anything.
roscoe36
08-05-2005, 12:31 AM
It really helps to read the upgrade notes in the forum. I did, and after upgrades from Beta 3 -> Beta 4 -> RC1 everything works like a dream.

GO VBADVANCED!
Brian
08-05-2005, 12:20 PM
Ah right I see... I was sure I used to have some hacks installed who's templates survived the upgrade, a fair few in fact?
That would be because the templates were not added to your global set. Not adding them to the global set though means that you will not have an option to revert them if needed, plus if you add any new styles then you would have to add those templates to the new style as well. As CS said though, there is some new stuff in 3.5 now that will allow the templates to remain after a vB upgrade and this feature will be taken advantage of in the next CMPS update.