Assorted Skin Bugs

[Chippiewill]

I'll go through these from top to bottom, some apply to just SS2010:
http://i.imgur.com/qhbIt.png

1) The top box is overflowing from it's container, you can fix this by removing "width:100%" from ".wgo_block h2" (I believe this is only used on SS2010)

2) The collapse button is misaligned on all the skins (I only checked two) in this specific place, due to the offset used for the collapse button on forum listings.

3) This applies to all skin, but most visible on SS2010, just needs "padding-right:20px;" in ".wgo_block .section div, .wgo_block .section ol"

4) ".blocksubhead" needs "margin-bottom:5px;" applies to all skins I think, and to all the blocksubheads, it's most visible here however.

5) Massive amount of deadspace on SS2010 setting ".wgo_block" to "margin-bottom:-15px;" looked closer to similar areas of spacing on the skin.

Done by Intricat.

[Recursion]

Noted.

[Chippiewill]

Before:
http://i.imgur.com/7l3n7.png

After:
http://i.imgur.com/fbteg.png

SS2010
For ".below_threadlist .threadpagenav":
"margin-top: -2em;"
Remove "width:100%
margin-bottom: 14px;"

For ".below_threadlist .threadpagenav .pagination"
Remove "margin-top:14px;"

Fixes stupid spacing bug for the pagination on the "forumdisplay.php" mode. On the show thread mode
For ".below_postlist .pagination_bottom .pagination"
Remove "margin-bottom:1em;"

For ".below_postlist"
Remove "margin-top:45px;"
Remove "margin-bottom:1em;"

For ".below_postlist .pagination_bottom .pagination"
Remove "margin-bottom:1em;"

For ".below_postlist .pagination_bottom"
Add: "margin-top:-2.5em;"


Noted.
I want another site coder to note it, when you note things - nothing happens.

Edit: Remove the 20px margin from the bbcode container, it creates a massive amount of space underneath quotes.

Done by Intricat.

[iAdam]

Tom's recognition is as good as anyone elses.

In reality, we won't fix these for a while as there's other projects we're working on.

[Chippiewill]

At the bottom of the view forum page:

Before:
http://i.imgur.com/cxZM8.png
After:
http://i.imgur.com/HvU8j.png

SS2010 Again:
To prevent the header overflowing:
".forum_info h4.forumoptiontitle" and ".forum_info .options_block_container h4"
Remove: "width:100%"

To remove a misalignment bug between the header and the content portion of the boxes (Couldn't figure a fix for Forum Options and Information):
".forum_info_block, .forum_info_form"
Remove: "width:100%"

To create some sensible spacing:
".forum_info .options_block_container, .thread_info .options_block_container"
Add: "margin-top:1em;"
".forum_info h4.forumoptiontitle"
Add: "margin-top:1.5em;"

To make the optionboxes take up the full width:
".forum_info .options_block, .thread_info .options_block, .forum_info .options_block2, .thread_info .options_block2"
Remove: "padding-right: 0.5%;"
".forum_info .options_block2"
Add: "float:right;"

To solve the "posting permissions" cluster****:
"#forumrules ul.youcandoblock"
Remove: "width:55%"
"#forumrules .rules_link" and ".rules_link"
Remove: "width:<value>;"

---------- Post added 08-06-2012 at 12:36 AM ----------


Tom's recognition is as good as anyone elses.

In reality, we won't fix these for a while as there's other projects we're working on.
In reality it's a ten second job that makes the forum look prettier and makes everything more readable yet you guys think that your not so secret project getting launched those few minutes earlier is that important?

Done by Recursion.

[iAdam]

In reality it's a ten second job that makes the forum look prettier and makes everything more readable yet you guys think that your not so secret project getting launched those few minutes earlier is that important?

I don't do any of the graphics fixes, but yeah. It's more important that we work on something major than on a silly spacing error etc.

[Kasabian]

yet you guys think that your not so secret project getting launched those few minutes earlier is that important?
yes.

:¬:

[Chippiewill]

I don't do any of the graphics fixes, but yeah. It's more important that we work on something major than on a silly spacing error etc.
I could understand that if the length of time it would take to achieve either task were comparable, but this is a really short job that I have given LINE FOR LINE instructions practically on how to fix so it'd be quick to do.

[xxMATTGxx]

You need to do something better in your life than reporting minor bugs that no one else would actually notice. I would also rather have my staff working on more important tasks than these fantastic minor bugs you are reporting.

[iAdam]

I could understand that if the length of time it would take to achieve either task were comparable, but this is a really short job that I have given LINE FOR LINE instructions practically on how to fix so it'd be quick to do.

You're thinking in terms of time not people. While it might not take long, that's still another person out of the other project and bearing in mind it's currently in the graphics phase, reducing the team from 2 to 1 for any length of time isn't good. Plus, matt just explained.

[Chippiewill]

You need to do something better in your life than reporting minor bugs that no one else would actually notice. I would also rather have my staff working on more important tasks than these fantastic minor bugs you are reporting.
Some of these aren't even minor. You may as well not bother fixing skins after you update vbulletin if minor bugs aren't a problem, heck, just add "body {display:none;}" and then you won't even see ANY bugs.

[Tom]

TO THE CLASSIC SKIN!

-BATMAN DOO DOO NOISE-

[Recursion]

The real question is, why does it bother you so much and why are you spending so much time reporting them?!

[Kieran]

I'll get round to it at some point when I feel the issues become a visual impairment to myself or other viewers of the site ;)

[xxMATTGxx]

Some of these aren't even minor. You may as well not bother fixing skins after you update vbulletin if minor bugs aren't a problem, heck, just add "body {display:none;}" and then you won't even see ANY bugs.

You never did this when it was just HotelUser to be honest. I don't know why you have only just started...

[Chippiewill]

The real question is, why does it bother you so much and why are you spending so much time reporting them?!

Because they really agitate me and it's little to no effort on your part.

[Recursion]

Because they really agitate me and it's little to no effort on your part.

I hope your Wiki is 100% bug free tomorrow morning ;)

[Kasabian]

TO THE CLASSIC SKIN!

-BATMAN DOO DOO NOISE-

I've been on it since 2006 whats your point?

[xxMATTGxx]

I think p { margin .4em } of the wiki should be .45em as it would add to the visual impact of the main page. Also can you fix this pixel error: http://habboxwiki.com/wiki/images/1/18/Maintenance.gif

[Chippiewill]

I hope your Wiki is 100% bug free tomorrow morning ;)
Give me simple and complete instructions on how to fix each bug and it will be.

[Kasabian]

i think we should scrap the whole ******* wiki

[Kieran]

Also,

http://habboxwiki.com/HabboxWiki:Community_portal

The H2 header boxers of each colour seem to be differing widths and have differing margins to each side.

[David]

Give me simple and complete instructions on how to fix each bug and it will be.


open this (http://habboxwiki.com/wiki/images/1/18/Maintenance.gif) in photoshop
take your eraser and remove the stray pixel
do a cart wheel
save as .png
???????????
profit

[Kasabian]

We are currently in the April 2012 cycle. Last month's winner was (not applicable). (Read More... (http://habboxwiki.com/HabboxWiki:Top_Contributor))

its june and whos not applicable? he doesn't post much :¬:

[Chippiewill]

open this (http://habboxwiki.com/wiki/images/1/18/Maintenance.gif) in photoshop
take your eraser and remove the stray pixel
do a cart wheel
save as .png
???????????
profit

That's a mediawiki error, related to the fact that the server doesn't have ImageMagick installed which creates problems with images for no good reason. Archived versions of an identical image do not have the same problem:
http://habboxwiki.com/File:Maintenance.gif



We are currently in the April 2012 cycle. Last month's winner was (not applicable). (Read More... (http://habboxwiki.com/HabboxWiki:Top_Contributor))

its june and whos not applicable? he doesn't post much :¬:
Thanks for the reminder.



Also,

http://habboxwiki.com/HabboxWiki:Community_portal

The H2 header boxers of each colour seem to be differing widths and have differing margins to each side.
Thanks for the helpful bug report. I trust this is fixed now?

[Kieran]

That's a mediawiki error, related to the fact that the server doesn't have ImageMagick installed which creates problems with images for no good reason. Archived versions of an identical image do not have the same problem:
http://habboxwiki.com/File:Maintenance.gif


Thanks for the reminder.



Thanks for the helpful bug report. I trust this is fixed now?

No. The purple one seems to have about a -1 pixel difference to the green. ;)

[Chippiewill]

I think p { margin .4em } of the wiki should be 4.5em as it would add to the visual impact of the main page. Also can you fix this pixel error: http://habboxwiki.com/wiki/images/1/18/Maintenance.gif
I disagree but you're the boss :)

[xxMATTGxx]

I disagree but you're the boss :)

I've corrected, do .45. Also while you are at it, fix everything else.

[Chippiewill]

I've corrected, do .45. Also while you are at it, fix everything else.
You're right, that's much better.

[Kieran]

You're right, that's much better.

I reckon .5 would be even better ;) :P

[Chippiewill]

I reckon .5 would be even better ;) :P
Why aren't you working on your top secret project. Matt said he wants his staff doing that rather than helping fix/improve graphical stuff that's already in place.

[Kieran]

Why aren't you working on your top secret project. Matt said he wants his staff doing that rather than helping fix/improve graphical stuff that's already in place.

I can multi-task... it was in my job description.

[Chippiewill]

I can multi-task... it was in my job description.
Then why aren't you fixing the bugs I just reported?

[Kieran]

Then why aren't you fixing the bugs I just reported?

I've told you I will get around to it.

[xxMATTGxx]

Then why aren't you fixing the bugs I just reported?

Because it's half 1 in the morning and some people have better things to do or even go to bed because of their work later on today. The bugs are not major and they will be fixed when people have time.

[iAdam]

That's a mediawiki error, related to the fact that the server doesn't have ImageMagick installed which creates problems with images for no good reason. Archived versions of an identical image do not have the same problem:
http://habboxwiki.com/File:Maintenance.gif



That's no excuse. Work around it and force it to appear as it should. Vbulletin broke the skins when it updated but we're getting around to fixing it.

[Chippiewill]

That's no excuse. Work around it and force it to appear as it should. Vbulletin broke the skins when it updated but we're getting around to fixing it.Well if you get Recursion to install imagemagick it'll be fixed.

[iAdam]

Well if you get Recursion to install imagemagick it'll be fixed.

I'm not involved in HabboxWiki or server issues. It's your job to request changes like that.

[Chippiewill]

I'm not involved in HabboxWiki or server issues. It's your job to request changes like that.
It seems resolved now anyway. Some bug related to the cache.

[Chippiewill]

Whilst I appreciate Recursion completely disabling forum features so there are less bugs to fix I would like to note that as of this point a maximum of 15 minutes (maybe) has been spent fixing these bugs. That equates to a whopping 0.0452898551% of time since being reported. Actually, I guess since there's 3 site coders it's more like 0.0150966184%.

Let's be honest here, it's no longer about priorities, you guys are adamantly refusing to fix serious issues, considering Recursion seems to have a problem with sorting out 2 cron-jobs (He worded it as "just needs the cron fixing" which does make me wonder why he's putting of doing it) so that the entire forum search isn't broken/indexing it's a bit out of hand here.

[xxMATTGxx]

Whilst I appreciate Recursion completely disabling forum features so there are less bugs to fix I would like to note that as of this point a maximum of 15 minutes (maybe) has been spent fixing these bugs. That equates to a whopping 0.0452898551% of time since being reported. Actually, I guess since there's 3 site coders it's more like 0.0150966184%.

Let's be honest here, it's no longer about priorities, you guys are adamantly refusing to fix serious issues, considering Recursion seems to have a problem with sorting out 2 cron-jobs (He worded it as "just fixing a cron" which does make me wonder why he's putting of doing it) so that the entire forum search isn't broken it's a bit out of hand here.

Let me correct you on a matter here. The cron job problem has been sent to Jin because Tom can't figure out why it won't run automatically but runs perfectly fine if it is ran manually. It's not that he is refusing to work, it's a matter of him not knowing how to fix the issue fully.

[Recursion]

Whilst I appreciate Recursion completely disabling forum features so there are less bugs to fix I would like to note that as of this point a maximum of 15 minutes (maybe) has been spent fixing these bugs. That equates to a whopping 0.0452898551% of time since being reported. Actually, I guess since there's 3 site coders it's more like 0.0150966184%.

Let's be honest here, it's no longer about priorities, you guys are adamantly refusing to fix serious issues, considering Recursion seems to have a problem with sorting out 2 cron-jobs (He worded it as "just fixing a cron" which does make me wonder why he's putting of doing it) so that the entire forum search isn't broken it's a bit out of hand here.

*REMOVED* We have lives, we have day jobs, the cron job is a real issue (neither me nor Jin can work out why it's happening) and the forum bugs are stupid little bugs that you're only reporting because they're on the SS 2010 which you're reporting bugs on to benefit yourself. We're not here to fix 2px margin errors.

Edited by SyrupyMonkey (Assistant General Manager): Please do not be rude to other members

[Chippiewill]

It's not that he is refusing to work, it's a matter of him not knowing how to fix the issue fully.
It's that he's not willing to spend time looking at the problem, not that he can't. At the very least he could run the jobs manually in the mean time.


they're on the SS 2010
Most of them are on every skin as I have already told you.

[Recursion]

It's that he's not willing to spend time looking at the problem, not that he can't.

Again, I'm not going to fix your 2px margin errors. If you want us to fix them within a matter of minutes of you reporting them, find the name of the associated vBulletin template, provide the old code and then provide new code to fix it.
Chippiewill; I'm not sitting here running commands on a server the entire day, I suggest you accept the fact some of us have jobs and a life.

[xxMATTGxx]

It's that he's not willing to spend time looking at the problem, not that he can't. At the very least he could run the jobs manually in the mean time.


Most of them are on every skin as I have already told you.

Tom runs the cron job every so often each day to be honest. But if you expect him to run it each hour than think again.

[Chippiewill]

find the name of the associated vBulletin template, provide the old code and then provide new code to fix it.
Gimme a list of template names and I will.

[xxMATTGxx]

Gimme a list of template names and I will.

How do you plan on doing that with the list of names?

[Chippiewill]

How do you plan on doing that with the list of names?
Use common sense, something which Tom lacks, clearly.

[Recursion]

Use common sense, something which Tom lacks, clearly.

OK, scrap the templates, provide a link to where the issue exists, describe where on the page, provide the old code and the new code.

You're treading on dodgy grounds.

[Chippiewill]

OK, scrap the templates, provide a link to where the issue exists, describe where on the page, provide the old code and the new code.

You're treading on dodgy grounds.
I already have included screenshots (You should be able to acertain location from that) and exactly what needs to be changed within each CSS id/class.

[Recursion]

I already have included screenshots (You should be able to acertain location from that) and exactly what needs to be changed within each CSS id/class.

You provided no screenshots on 90% of the ones you gave to me (i.e. the ones David deleted).

[Chippiewill]

You provided no screenshots on 90% of the ones you gave to me (i.e. the ones David deleted).

I described where they were.

[Recursion]

I described where they were.

Well, if you have them noted down anywhere, feel free to post them as you know full well I didn't delete them.

[Chippiewill]

Well, if you have them noted down anywhere, feel free to post them as you know full well I didn't delete them.
I'd rather you fix the ones at the start of this thread first, then I might well reveal the others.

In the meantime Matt should probably look into a way of preventing AGMs from making Habbox violate their part of the TOS aka actually deleting ****, for good, just before they resign.

[Recursion]

I'd rather you fix the ones at the start of this thread first, then I might well reveal the others.

In the meantime Matt should probably look into a way of preventing AGMs from making Habbox violate their part of the TOS aka actually deleting ****, for good, just before they resign.

We have daily/weekly/monthly backups, but for something like this, I'm not going to go trawling through them and messing around with databases to pull it back.

Search crons should be fixed now I hope.

Thread closed.

[xxMATTGxx]

I'd rather you fix the ones at the start of this thread first, then I might well reveal the others.

In the meantime Matt should probably look into a way of preventing AGMs from making Habbox violate their part of the TOS aka actually deleting ****, for good, just before they resign.

David wasn't an AGM then, he left that role a while back and stayed as a Occasional Techie role before fully leaving. So to prevent anyone doing that than the permission to delete posts would have to be removed from Admins, General Management etc.