Upgrading problem from 4 to 5

[habboubih83]

Hello,

I have just upgraded my vbulletin from 4 to 5. But after installation, the forum doesn't look right.

Please see here:
https://community.hma-labs.com/

How do I fix this?

[Dave]

It seems that some of the stylesheets aren't loaded properly.

I haven't used vBulletin 5 in a very long time but can you try creating a new default style and see if that works? Or maybe in the vBulletin settings move the stylesheets from the database to the filesystem.

[habboubih83]

This didn't resolve the problem.

It seems there is a problem with the style order numbers. They all have the order of 1. When I try to change it, or try to rebuild styles from General Tools, I get a database error.

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

Okay, I got it.

So here is where I need to set the option to yes:

Store CSS Stylesheets as Files?
If you would like to store the CSS stylesheet for each style as a file, you must ensure that you have a directory called 'vbulletin_css' inside the 'clientscript' folder, and that the web server has permission to write and delete files within that directory.

However, what seems to be the problem with this option? Why doesn't it work when I set this option to no?

[Dave]

I have no idea (maybe someone else can explain), but by storing CSS stylesheets as files it will lower your database load as well so this is the better option to have turned on.

[Rafa-el]

Originally Posted by habboubih83

This didn't resolve the problem.

It seems there is a problem with the style order numbers. They all have the order of 1. When I try to change it, or try to rebuild styles from General Tools, I get a database error.

--------------- Added 28 Jul 2017 at 14:29 ---------------

Okay, I got it.

So here is where I need to set the option to yes:



However, what seems to be the problem with this option? Why doesn't it work when I set this option to no?

Is the directory writable? Also what does the DB error says?

[noypiscripter]

The problem seems to be related to htaccess. But it looks like the issue has been fixed?

[habboubih83]

Thank you guys for your comments. I've had it fixed. I had to rerun the installation/upgrade.