[Bug / Issue] Styling issue bug on Search in several styles live on this site?

[1kether1]

I am working on skinning my vB5.5.5 and liked one of the styles that comes with the software. I downloaded it have uploaded a copy that I have been editing. I noticed an issue with the styling around the search box drop-down arrow and figured it was something I had done, but when I visit this live (vbulletin.com) site and choose several of the different skins, the error appears to be part of the style(s). Can someone help me remove that little hanging down divider? Or, shorten it? Here is an image to show what I mean.







Thanks,
K

[Mark.B]

Hmmm. It's definitely there, though I can only make it out with a zoom.

Seems to be controlled by this:

.search-box .vertical-divider-left {

The height for that is set to 100%. I find that reducing it to about 93% gets rid of it however I'm absolutely certain that's not a 'proper' fix.

Probably needs a bug report going in.

[1kether1]

Hmmm. It's definitely there, though I can only make it out with a zoom.

Seems to be controlled by this:

.search-box .vertical-divider-left {

The height for that is set to 100%. I find that reducing it to about 93% gets rid of it however I'm absolutely certain that's not a 'proper' fix.

Probably needs a bug report going in.

Okay, I have a question about this. I looked and finally found the code in the:

vbulletin-style.xml file inside the install directory.

That directory has been deleted from my server after the install was completed. I have the xml file and can upload it in the style manager, but I wondered if it would write over the default style and the other 'default' styles in the style manager. Also, would that update my custom style that I am building. Sorry, if this is a dumb question. I just want to know how to update it correctly. I'm fairly certain I don't upload that directory and run the upgrade script again, do I? Thanks, Mark.

Also, I'm not certain how to report a bug. Usually someone else finds them way before me and I come here and find the solutions. If you could tell me how to actually update the file and also provide a link or directions to how to report the bug, I will get it done. Thank you, again.

K

[Wayne Luke]

Templates are stored in the database during installation. Any changes to the vbulletin-style.xml file will be overwritten and lost in the next software upgrade. You can view templates in the Style Manager which is under Styles in the AdminCP. Within the Style Manager you can click on the <<>> button to the right of the style name. Templates will be listed in alphabetical order. When there are multiple templates with the same prefix, they will be grouped such as CSS Templates. Double-clicking on a template group name or a template name will open it. When opening templates, they will be editable. Your changes will be saved as a new copy of the template that won't be overwritten on upgrade. I don't know what to change the code to offhand. Not even sure we can account for zoom 100% of the time due to the way CSS actually works in the browser.


You can report the bug by clicking the "Tracker" link in the header navigation of every page on these forums. Once the tracker loads, click the blue "Report Issue" on those pages in the header. Choose bug as the type of issue. Give it a title and description in the form that opens. Set the version in the drop down to the one that you're using. Click the save button.

[1kether1]

Wayne Luke Thank you. I have reported the bug here: https://tracker.vbulletin.com/vbulle...sues/VBV-19867

I finally found the code in the css_global.css: template. Thank you for your help. I sincerely appreciate it.

.search-box .vertical-divider-left {
    border: 0;
    border-{vb:stylevar right}: 1px solid #BDBDBD;
    display: block;
    height: 93%;

K

[Mark.B]

It is actually visibile without zoom, you just need a very keen eye to spot it.

I would also stress...my 'fix' is probably not a proper fix. Consider it a workaround. It seems wrong to have to set a vertical bar height to 93% when you do in fact want it to persist all the way down.
I suspect the container it's in is too large.