5 replies to this topic

[Olivier Turbis]

We are glad to announce that all of our current vBulletin 4 skins have been updated and improved. We fixed a lot of bugs, replaced images that didn't necessarily fit and much more. Here are some of the main features this update provides in the Brave, Underground, Blood and Warrior skins.

No more tables
We removed all the added tables from the Underground, Brave and Warrior skins so you have less tables in your vBulletin skin. Of course, some tables are left since the default vBulletin 4 skin does have tables.


New custom made forum icons
All dark skins now have their own custom forum icons, replacing the default vBulletin skin's forum icons. Here's a little preview of these icons:




Share This Thread
We are introducing a new feature, Share This Thread which is included in all of our current vBulletin 4 skins. This feature lets you submit a thread to both Twitter or/and Facebook.




New thread button in topics
We have also included a "Post New Thread" button in the threads of all of our vBulletin skins. The default vBulletin skin doesn't have this button, and we thought it was primordial.




A new Bigthing in Underground
Underground now has a "new" Bigthing (the guest welcome message). It now indeed has the user login form right in the bigthing.



Grab the new copy of your skin now from your download box or purchase one!

[d3vlabs]

congratulations! however is it possible to update skins without losing current hacks, like a patch or something?

[Olivier Turbis]

No, unfortunately.

[d3vlabs]

Olivier Turbis, on 22 May 2010 - 12:48 PM, said:

No, unfortunately.

gotta be a way. what about merging skins, could that work?

ceilo alone had like 3 upgrades

[Olivier Turbis]

I'm not sure if you can "merge" skins, no. There is no "automatic" ways to do that unfortunately.

[d3vlabs]

I was reffering to this : , but seems like the only advantage of Merging is keeping the name of the skin the same.

what about a descriptive changelog, it says some sort of changelog will be implemnted in SB 2.0, what about having a changelog that actually has the code that was changed. would that be too much work?

one of the reasons im asking is that i feel im going to be a skinbox customer for a long long time.