The issue is that we want the default user profile to match the customer site, not the vBulletin default install. That means we have to map the stylevars to the new profile variables. We need a total of two sets of text/background colors that will have enough contrast to be visible, and four sets of text/link/background colors. There aren't that many combinations that have guaranteed contrast.
If the site style keeps the current lightish colors lightish, and the darkish colors darkish, then all will be fine. If the colors are all reversed,so the current lightish colors become darkish and the current darkish colors become lightish, all will be well. But if some of the darkish colors become lightish, and some of the lightish colors stay lightish then there could be a problem.
The long-term solution is that as we add the "theme" capability we will add the ability to customize the default theme. In 408 we put in the back-end code to process that default style but not the front-end code that allows the admin to set the default. The ability to set this will be in v409.
So this problem can be fixed with an SQL query. You can do it either in admincp > maintenance > execute sql query, in phpmyadmin, or any other sql query tool you have. This has not been through QA, so this is unsupported and must be done carefully.
Again, in 409 this won't be necessary.
If the site style keeps the current lightish colors lightish, and the darkish colors darkish, then all will be fine. If the colors are all reversed,so the current lightish colors become darkish and the current darkish colors become lightish, all will be well. But if some of the darkish colors become lightish, and some of the lightish colors stay lightish then there could be a problem.
The long-term solution is that as we add the "theme" capability we will add the ability to customize the default theme. In 408 we put in the back-end code to process that default style but not the front-end code that allows the admin to set the default. The ability to set this will be in v409.
So this problem can be fixed with an SQL query. You can do it either in admincp > maintenance > execute sql query, in phpmyadmin, or any other sql query tool you have. This has not been through QA, so this is unsupported and must be done carefully.
- Go to your own profile and customize it to look like the default.
- Get your userid. It very likely is one but isn't guaranteed.
- Execute the query
UPDATE <TABLE_PREFIX>customprofile SET userid = -1 WHERE userid = <this userid>;
So for example if on your member profile page the url is something like member.php?12-fred, and your table prefix is vbf_, your query would be
UPDATE vbf_customprofile SET userid = -1 WHERE userid = 12;
and any users who haven't customized their profile will get the new default. - If you don't like the results, you can remove the profile by executing
DELETE FROM <TABLE_PREFIX>customprofile WHERE userid = -1 - If you execute step 3 and want to change again, please execute the query in step 4 to delete the saved default profile before you save a new one.
Again, in 409 this won't be necessary.
Comment