Error upgrading to 4.02

[Mopar1973Man]

Is anyone going to respond to this problem? Is any of the Dev's going to write a patch for us? I'd like to move forward...

[Rik Brown]

When I was upgrading styles I got:

Updating style information for each style...

vB4 Default Style ... (Templates) (Stylevars) (Replacement Variables) (CSS) (Controls)
Warning: Invalid argument supplied for foreach() in includes/adminfunctions_template.php on line 913

Warning: Invalid argument supplied for foreach() in includes/adminfunctions_template.php on line 913
Done.

for every style I had. Should I be worried?

Getting the same error here but it doesn't appear to effect operations. Everything still works fine afterward.

FYI, there's at least one bug report on this: http://www.vbulletin.com/forum/proje...?issueid=36279. -- Rik

[Mopar1973Man]

Ok... I'd made the update...

One of the Dev's had posted on the bug report that to return your CSS file to database storage and then run the install. so far the install went just as planned and the software is working fine. As for returning back to file storage CSS files he recommends that you leave it in Database mode till version 4.0.3 comes out which will have the fix...

[vivamexico55]

This error keeps popping up everytime you change something in the stylevar editor, apparently

[Mopar1973Man]

Change your CSS storage to database to correct this...

[motowebmaster]

On my test forum, I made sure that the vbulletin_css directory had the proper ownership and finished the upgrade. Then I deleted all of the auto-generated files in that directory (except for index.html). Then rebuilt the style.

I had removed all of the v4.01 files and directories before uploading v4.02, with the exception of my configuration file. All that needed to happen was a normal upgrade, don't understand why they couldn't get this to come out during testing before releasing this version.

[ez4arab]

rebuilt the style then run upgrade code

[Yves R.]

A temp fix is available on the bug link previously given here. Go to the bottom of the page on 'Attachments' part and click 'View Highlighted Patch' to see the edit you need to do to fix. This is fixed on 4.0.3.

It happens only when you disable products on the Suite or on Forums itself (if you don't use the Suite).