Feedback - green color need fix

[TTayfun]

hello staff members, at green color left side 1px more according to the right side. i think it must fix. i added in attachments.

if you let, i can fix with remake back jpeg file with ps.

.

[Mark.B]

Unlikely any work will be done on styling now, to be honest.

[TTayfun]

Unlikely any work will be done on styling now, to be honest.

i did fix broken jpeg file, i would like to send via private message fixed jpeg file to you, i am thinking really vb.org family and members and its design. :up:

[Mark.B]

I don't have any ability to change anything I'm afraid.

[TTayfun]

I don't have any ability to change anything I'm afraid.

hmm i see than, if any vb.org staff message me, i can send. :up:

[In Omnibus]

Unlikely any work will be done on styling now, to be honest.

It's painfully obvious vBulletin stopped caring about vBulletin.org when third party developers stopped caring about vBulletin 5.

Painfully obvious.

[Mark.B]

The styles here have been in place for at least a decade now. It's not within the official process to just make a quick change to something that must have been the same for most if not all of that time.

Resources are finite and everything has to be prioritised. It isn't even the default style. I would respectfully say it'd be very low on the list of things to commit resource and testing to. Yes it would need to be tested. There are processes for these things.

[Max Taxable]

It's painfully obvious vBulletin stopped caring about vBulletin.org when third party developers stopped caring about vBulletin 5.

Painfully obvious.Which, the reverse might be that vB stopped caring about the developers when it released a major new version of the product that didn't utilize hooks. THEN the developers stopped caring about vBulletin, THEN vB stopped caring about vBorg.

[In Omnibus]

Which, the reverse might be that vB stopped caring about the developers when it released a major new version of the product that didn't utilize hooks. THEN the developers stopped caring about vBulletin, THEN vB stopped caring about vBorg.

True but if vBulletin had any sense of direction they would have developed vB4 to do all of the things this heavily modified vB3.x site does, because, at the time it was highly in-demand and frequently asked: "How can I make my site look like vBulletin.org?" That "You can't without a ton of custom coding!" was off-putting to a lot of customers. The there was the manner in which v B4.x was released. vBulletin learned nothing from that and made the same mistake on steroids with vBulletin 5. Obviously, this is all hindsight at this point but it is all symptomatic of a larger issue, which is that Internet Brands either has no concept of what is in demand and how to meet that demand or Internet Brands has no interest in proactively creating in-demand forum software. vBulletin 5 is the most reactively created software I've ever seen. Here's a basic shell. Now tell us what you want it to do or be in a JIRA and we'll get to it sooner or later. It really doesn't take much forethought to know that virtually every modification and add on is based upon the ability to utilize PHP hooks and that third party developers are not going to be champing at the bit to completely rewrite every modification they've ever released to be compatible with API-based software. Not even vBulletin's own staff have done that with their modifications. It was a poor concept, poorly planned and poorly implemented. When Lawrence Cole was with IB at least you could communicate with him, with some assurance that customer ideas would be relayed to the higher ups, whether or not those ideas were implemented. IB got away from that when Cole left and it's been impossible to even contact IB directly since.

[Mark.B]

Wayne is capable of feeding stuff up the tree but that doesn't mean it will get implemented.

Also it's worth noting that one customer saying "I really need this, put it into the software" does not translate to it being something a lot of customers want. Every request is critical to somebody, but obviously not every request can be added. There is also the issue of whether particular requests fit the vision for the software. A good example of this is people asking for a Shoutbox, which is unlikely ever to be adde because it doesn't fit what the company want the software to be.

Another point worth noting is that even at this site's peak, modified sites accounted for only a tiny percentage of overall customers. The overwhelming majority of customers wanted a default site, and the most they did was put up a custom logo. That's still the case today. People don't want the hassle. Most don't even play with many of the options, it's all left as default. Create a few forums, slap a logo on (these days, pick one of the themes as well) and go.

Spending a fortune on a modification platform these days is unlikely to provide a good return on investment, unless you introduced some form of fee, but with modifications everyone wants everything for nothing.

[In Omnibus]

Wayne is capable of feeding stuff up the tree but that doesn't mean it will get implemented.

Also it's worth noting that one customer saying "I really need this, put it into the software" does not translate to it being something a lot of customers want. Every request is critical to somebody, but obviously not every request can be added. There is also the issue of whether particular requests fit the vision for the software. A good example of this is people asking for a Shoutbox, which is unlikely ever to be added because it doesn't fit what the company want the software to be.

Another point worth noting is that even at this site's peak, modified sites accounted for only a tiny percentage of overall customers. The overwhelming majority of customers wanted a default site, and the most they did was put up a custom logo. That's still the case today. People don't want the hassle. Most don't even play with many of the options, it's all left as default. Create a few forums, slap a logo on (these days, pick one of the themes as well) and go.

Spending a fortune on a modification platform these days is unlikely to provide a good return on investment, unless you introduced some form of fee, but with modifications everyone wants everything for nothing.

Wayne has a full plate of responsibilities as it is. He's also been used as a human shield against direct criticism of anyone higher up, which is entirely ridiculous on face because he is one of the few remaining positives about this product. I wouldn't burden him with the additional task of asking him to fight customer battles for functions and features that should have been added to the core vBulletin 5 product.

It's entirely understandable that every customer has different needs but some of the functionality missing in vB5 should have been optional. Most customers use a default version of the software because that is what is readily available. They don't have the option of enabling a shoutbox, for example, from the admincp to see if it's something for which their site has any use. Most customers are afraid of breaking something and so they won't even attempt to install third party add ons or modifications. The handful of techno geeks who insist on modding and template editing the bejeezus out of the software are a small minority.

We agree and have always agreed that if modifications are necessary to a forum the core content is the problem. That is not the issue. The issue is summarily dismissing your existing customer base by creating a product that doesn't even allow for a smooth transition. Customers who could not move up moved out. That is why this product is in the state in which it currently resides. That is why a competing product was even capable of gaining a foothold in a market once dominated by this product line.

[TheLastSuperman]

What the bloody HELLO there gents! I see there's an issue with the green style no clue where all this other jargon came from such is communication I suppose. I'll mention this issue to the appropriate staff but as already noted this is on the low end of the totem pole I'm afraid so your best option in the meantime is to simply overlook it or use a different style choice ;).

Closing this as we know there is an issue, see the fix provided, will implement when/if possible :cool:.