Assorted Skin Bugs

[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.