Page 1 of 1
Categories Plug in.
Posted: Wed May 23, 2007 4:10 am
by rj
In the categories plugin, the GO box for the category picker is way too long.
I don't see this plugin in the plugin area so I dont know where I would change the width of the GO box at?
RJ
Re: Categories Plug in.
Posted: Wed May 23, 2007 11:48 am
by garvinhicking
Hi!
The length of it depends on your CSS for the 'input' type field element, which you can adjust using the 'width' CSS modifier within your style.css file, like:
Code: Select all
.serendipity_categories_plugin input {
width: 5px;
}
Regards,
Garvin
Posted: Wed May 23, 2007 3:33 pm
by rj
My problem seems to be that the Category plugin, though presented in ADMIN and on the Blog, is no where to be found on the server or in the plugin directory, or in CSS. I think it was added with the original install and is some sort of hybrid confuse ME!
Posted: Wed May 23, 2007 3:36 pm
by garvinhicking
Hi!
You add the CSS into your main style.css file of your template, no need to edit/find any plugin related files!
Best regards,
Garvin
Posted: Wed May 23, 2007 5:11 pm
by rj
I still do not understand.
I put that in in the css file and nothing happens.
I keep thinking it is because that plugin does not exist in the plugin directory.
But what do I know!
.serendipity_categories_plugin input {
width: 100px;
}
There is no existing .serendipity_categories_plugin line in the CSS file. Does it matter where I put it. I put in the rest of the plugin area at the bottom of the CSS file.
Default for that GO! box is about 150px and my sidebar is 125px, thats the problem. How wide does a GO! have to be anyway?
Posted: Thu May 24, 2007 1:25 pm
by garvinhicking
Hi!
It simple might be because you have other CSS rules that override the thing you enter. One thing is to add this as the last thing to style.css, not at the top.
A second thing would be to use this:
Code: Select all
.serendipity_categories_plugin input {
width: 100px !important;
}
And a last thing is to use the proper prefixing. Search your .css file for "input" and see which rules it precedesses. CSS is "Cascading", so a clearer indiciation of a rule always takes precedence for an unclearer indication. The more complete you add the "path" of a CSS element to your CSS file, the higher precedence it has and cannot be overriden by other statements.
Regards,
Garvin
Posted: Thu May 24, 2007 2:49 pm
by rj
I tried it up top and important down bottom and it just doesnt take.
http://rackjite.com
if you go there you can see GO! so obviously sticking out too far!
BTW, traffic is doubling every week.
Broke 500 a day yesterday and havent even entered the blogosphere yet.
Posted: Thu May 24, 2007 3:01 pm
by garvinhicking
You can find the solution if you read my full previous answer, the instructions are there.
Regards,
Garvin
Posted: Thu May 24, 2007 4:58 pm
by rj
hehehe.... GOT IT! Thanx...
What was screwing me up was not seeing that plugin in the plugins.
I was dwelling on something that did not matter!
RJ