DISQUS

JaredB · 2 years ago

Excellent.

I'd just suggest triggering or attaching the onload script from within your plugin, by including a script reference using the 'wp_head' WordPress action. Then you could remove installation step 5.

Brajeshwar · 2 years ago

Sounds cool. have to try this out.

Abhi · 2 years ago

Thank you for this plugin.

Looks really cool. I have it installed just like you said, but for me it just shows ...loading...

I checked out your source and mine and they look identical. What do you figure I am doing wrong?
Thank you.

Dan · 2 years ago

Fixed the body tag modification.

@Jared:
function OnLoad() {
...
}
GSearch.setOnLoadCallback(OnLoad);

Google actually suggests that method anyways.

Abhi · 2 years ago

Hello Dan
Wow. thats great. it loads. but yeah it looks ugly with the glossy blue theme.

thanks though.

Keith · 2 years ago

Well, it is not working for my blog here - http://keith.edu.ms Any idea?

Dan · 2 years ago

[quote comment="204053"]Well, it is not working for my blog here - http://keith.edu.ms Any idea?[/quote]
Make you download the newest release. It's already at .95.

Also make sure you go to the configuration page.

Abhi · 2 years ago

this is really great.

Keith · 2 years ago

Dan, thanks for reply. I have upgraded to the latest version .995, and also updated the information at the Option tab in WordPress. But, I still cannot get it to work. Is there some kind of special requirement?

Dan · 2 years ago

What version of wordpress do you have because it's not loading in your header. You might have another plugin interfering.

lars · 2 years ago

Hey Dan, this is a really great Plugin! *thumb up*

But you should consider to correct the Installation Guide, it seems you forgot to place an questionmark in the String:
It won't load without the missing questionmark.

best regards, lars

Dan · 2 years ago

Thanks for the heads up. Fixed/

Keith · 2 years ago

[quote comment="204596"]What version of wordpress do you have because it's not loading in your header. You might have another plugin interfering.[/quote]
I am running WordPress 2.1. Well, I aren't sure what plugin might be interfering with it. But, that might be possible.

oso · 2 years ago

The plugin is fantastic, but the "powered by Google" slogan is pretty hideous. Is there a way to exclude that? Thanks so much.

Dan · 2 years ago

I agree. The next release will have the option to take that out.

wolkanca · 2 years ago

excellent dan.

oso · 2 years ago

Fantastic - really looking forward to the next release. Thanks so much.

Dan · 2 years ago

For those subscribed to this post I've just released Version One. It's completely redone and has complete flexibility over style and search functions.

Hoboken411 · 2 years ago

I've been testing this out in my sandbox, and I've found that it doesn't keep the widths consistent, and LONG URLS that come in the search results cause the theme to break.

Any way to keep everything, including search results locked at say, 200 pixels? That's what's preventing me from installing it in a production environment.

But looks great otherwise!

Good work. Let me know if others have experienced the same issue.

martin · 2 years ago

Thank you for the plugin, works like a charm and looks great.

One question tho; for some reason the search results aren't correct. If I make a search for something it shows some posts, but not all. And sometimes it doesn't show any posts at all, even tho it should since the search query is correct.

Any ideas on what I'm doing wrong here?

Thnx in advance!!

Mary Robinette Kowal · 2 years ago

This is a lovely plug-in. I'm also having issue with the width of the search results breaking my theme in Firefox. It doesn't seem to happen in IE. If you just tell me where you define the width, I can adjust it myself.

Alex · 2 years ago

what am i doing wrong...i cant get this to work either!!!!!
i checked out the code on abhi's site, and mine is nothing like it.
All that happens when i search is it takes me to a google blog search page....
maybe its just too late at night to be trying to implement this stuff.
does the standard plugin give the same functionality as on your search box, cause that is what i was expecting...

Will · 2 years ago

/* Blog Results Width */
.gsc-results .gsc-blogResult * {
width: 180px;
}

Works in IE, but not 100% in FF...

Anonymous · 2 years ago

[quote post="1673"]what am i doing wrong…i cant get this to work either!!!!!
i checked out the code on abhi’s site, and mine is nothing like it.
All that happens when i search is it takes me to a google blog search page….
maybe its just too late at night to be trying to implement this stuff.
does the standard plugin give the same functionality as on your search box, cause that is what i was expecting…[/quote]

Darren · 2 years ago

I am having some unusual problems with the Google Search plug-in. It only seems to work with certain keywords. I can type CAR and get a result, but if I type TEXTPATTERN (a word I KNOW is in Blog) I get NOTHING :(. Any ideas??

Dan · 2 years ago

It must be something to do with Google since Google is responsible for the results. Confirm it by searching with Google and without the plugin.

Alex · 2 years ago

@will
when you say not 100% in ff, what do you mean? it stops the text extract flowing over on mine, but not the url, is this what you mean?

also, add this, and the width is regulated for page search, not just blog
/* Blog Results Width */
.gsc-results .gsc-blogResult * {
width: 180px;
}
.gsc-results .gsc-webResult * {
width: 180px;
}

is there a way to not show a title for this sidebar widget? my theme automatically puts a background up for h2 headings in the sidebar, but i dont want one here, and if i change the css for it, it changes the other h2 in the nav sidebar.

thanks

Dan · 2 years ago

Alex: Everything looks fine, the width is regulated in the options page now. Maybe that comment was before the last release.

To take the header title out, I would use sidebar modules instead of sidebar widgets. It has the option to not show the title of the widget.

Hope that helps.

Dan · 2 years ago

Now I see what you might be talking about. Your width is off because the divs in your theme are weird. Use SBM and it hide the div problem.

dougie · 2 years ago

Installed Google-AJAX-Search.php on a Wordpress blog and it works, but I have some questions...

1. Google is finding the RSS feed content in the "web" section of results, which we don't want.

2. Is there a way to control how many results display, currently it's only one.

3. I don't see the option for open vs. closed either. It's currently set to "closed", and I thought it would impact the drop down of the results, but the results drop down.


FYI, the only changes we made were to the user defined labels:
"webSearch.setUserDefinedLabel("Webpages");"
"blogSearch.setUserDefinedLabel("Articles");"

You can see the installed search at www.kidoinfo.com/ri/ But we need to either fix or remove it soon.

If we can't get the Google search to stop finding RSS content and also control the # of results, then I'll just use the search_everything3.php (which we already installed), at least it searches the pages, but the results aren't displayed nearly as well as the Google solution.


Bottom line, I appreciate all that you've done to develop these solutions, they are almost perfect for what we need and much more than we could have created ourselves.

Any feedback or customizations you can offer would be greatly appreciated.

surtin · 2 years ago

Hey seems like a great plug-in, and it seems like it setup fine and dandy. But when entering a search string, nothing is returned. So I guess I have maybe a couple of questions...

The difference between OPEN and CLOSED in the options is basically to tell the plug-in to just search your blog (CLOSESD) and the enter web (OPEN), right?

I think I had another question but I just forgot it...

Your help is appreciated. :)

Dan · 2 years ago

OPEN and CLOSED is for the results. It specifies if you want the results view to be open or closed.

Not sure why results aren't showing since it uses Google. Search Google directly with site:www.your_url andsee if you get any results.

surtin · 2 years ago

Ah I see, well I do get results when searching Google directly. Could it be that my blog address (WP settings > General) is different from the WP URL?

surtin · 2 years ago

Any ideas? Still can't seem to get this working...

Alex · 2 years ago

hey dan,
did you get my email?
where is the PHPSESSID being created?
a

Dan · 2 years ago

Yes.

I've noticed that a from the groups that Google AJAX search doesn't validate strict XHTML.
I'm sure theirs a thread in the groups about it, http://groups.google.com/group/Google-AJAX-Sear... since I remember seeing one a few weeks back.

I'm interested in your fixes if you want to send me another email.

Alex · 2 years ago

for everyone interested, to solve the problem of overflowing urls, add

overflow: hidden;

to the

.gs-result a.gs-visibleUrl,
.gs-result .gs-visibleUrl {

and

.gs-result a.gs-clusterUrl,
.gs-result .gs-clusterUrl {

sections of the plugin file.

dan, this is another fix that ive only just thought of, and is not in the file i emailed you.
did you get the mail?

Dan · 2 years ago

Yes, I did. I'm just trying to find the time.

Alex · 2 years ago

thats cool. ive still had no luck on the PHPSESSID

Alex · 2 years ago

dan, you'll be glad to know that the PHPSESSID problem was a plugin conflict with the skypebt plugin.
therefore the file i sent you is 100% XHTML valid.
Wahoo!

Searcher · 2 years ago

Link at the top here [Download One.One] still points to 1.003?
One.One appears to be available from http://google-ajax-search-wordpress-plugin.goog...

Thanks!

hAmid reZa · 2 years ago

Seems nice but I encountered problems using it. My wordpress installation directory is different from my blog root. This plugin sends my wordpress installation path to google not my blog root and this is not correct (eg. http://www.gozir.com/wordpress instead of http://www.gozir.com).

Anonymous · 2 years ago

How can I get the results to appear on a page as opposed to in the sidebar:
www.smears.co.uk

I'm using WordPress as CMS so no posts need searching by the way.

Carson Weber · 2 years ago

How do I remove the "Web" results and have it display only the "Blog Search" results?

todd johnson · 2 years ago

HEY !
this is totally sweet
i love you.
[quote post="1673"]Seems nice but I encountered problems using it. My wordpress installation directory is different from my blog root. This plugin sends my wordpress installation path to google not my blog root and this is not correct (eg. http://www.gozir.com/wordpress instead of http://www.gozir.com).[/quote]

Carson Weber · 2 years ago

I figured it out... went into the php and commented out some lines. Thanks for this wonderful widget!

z.king · 2 years ago

Thanks for the plugin.

There's no option to change the search result text color. There are options for the title and links, but not the text color.

I can't figure out how to make the change with style sheets, so it would be nice to have an option.

Thanks again.

Jared · 2 years ago

I noticed that some ads come up in some search results. I assume they are Google ads. How is this controlled?

Dan · 2 years ago

They aren't. It's part of the API Google gives. I might even stop using it because of this.

Jared · 2 years ago

I guess I should rephrase my question: Who gets paid when someone clicks on those links?

Dan · 2 years ago

let me rephrase, "I might even stop using it because" I don't get paid. :)

Jared · 2 years ago

So does anyone know who gets paid? If it is Dan the developer, I could see donating a percentage of ad revenue as in the AdSense Manager plugin. Dan, want to chime in?

Dan · 2 years ago

Sorry, I thought you were another Jared.

The money goes to Google of course. I would love for it to go to me but that's not how it works.

JaredB · 2 years ago

I was going to say something, but I figured you'd figure it out.

Jared · 2 years ago

Have you seen the Adsense Manager plugin? They figured out some way for it to work.

JaredB · 2 years ago

This isn't Adsense though. If I understand correctly, the ads you are referring to are Google's ads that get included with the search results returned when using their API, and (I believe) Google is the only one making money on those. It's just like the ads you see when you do a regular Google search on their page.

Adsense is a seperate issue entirely, and the WordPress plugin is for managing your Adsense ads on your own site.

In other words, the ads in the API search results have anything at all to do with your Adsense account.

JaredB · 2 years ago

"... don't have anything to do with ...", I should say.

Jared · 2 years ago

Got it. Thanks for clarifying that painfully obvious fact that was right in front of my face. Actually makes plenty of sense. Sometimes I wish I was born with an above average ability to perceive those things directly under my nose.

Hamid reZa · 2 years ago

What's your problems? It seems funny?! I reported I bug I think. Do you know what is a bug?

[quote comment="245455"]HEY !
this is totally sweet
i love you.
[quote post="1673"]Seems nice but I encountered problems using it. My wordpress installation directory is different from my blog root. This plugin sends my wordpress installation path to google not my blog root and this is not correct (eg. http://www.gozir.com/wordpress instead of http://www.gozir.com).[/quote][/quote]

Dan · 2 years ago

You need to configure wordpress correctly. The plugin uses your wordpress URI.

Hamid reZa · 2 years ago

Thanks for the response!
But I think this is not true. It must use "Blog URI" not "WordPress URI". "WordPress URI" is used to determine path to wordpress installation (path to administration url, theme, css, ...) while the blog address actually determines where the home page is.
I figured this out by changing my WordPress URI in general options: Everything got wrong, my control panel address became redirected to root address and ... . Only a db modification using phpMyAdmin helped me.

Dan · 2 years ago

Download 1.1 beta. It uses your home URI instead.

Jared · 2 years ago

Hi Dan, I am using 1.003 with WP 2.2. I am seeing a strange issue: whenever there is a long link, it doesn't break and wrap. Instead it spans across two columns. Can you take a look when you get a chance? Thanks!

Do a search on 'prefab' and do a search on 'test' to see the difference:
http://www.smallhousestyle.com/

Best,

Jared

Jared · 2 years ago

PS, I'm using FF on OSX and when I look at it with 'one result' it looks fine, but with 'more results' and 'all results' it breaks...

Dan · 2 years ago

Thanks for reminding me, I need to add that to the CSS. Look for a new release soon.

zets · 2 years ago

Hi Dan!

I think I have a problem with Your plugin. When I search for something only the "Second Search" works fine. "Web search" is always using http://www.adbundy.com as a sourse for its results and I'm not sure that "blog" search works fine either. Please help.

Thanks

wljinxin · 2 years ago

Very helpful CODE

wltuoye · 2 years ago

Oh, very good!

流水线 · 2 years ago

流水线
流水线

alternapop · 2 years ago

this works for me if i put the code in a sidebar but doesn't work if i create a dedicated 'page' with only this code.

what do i need to do differently?

thanks!

Dan · 2 years ago

It should work as is on that page. What does it look like?

Dan · 2 years ago

Now that I think about it. Are you adding the <php> code in the page template or the page content? You should make an extra template that has the code in the div that you want. It will not work in the content of the page unless you use another plugin to enable the ability to place code within a post/page.</php>

alternapop · 2 years ago

hi dan, thanks for responding...
nothing shows up at all. it's completely blank where the code is.
i'll play around with a second template and see if i can get that working.
thanks

Dan · 2 years ago

The second template should work. That's the only way to put php on pages without using another plugin.

Long · 2 years ago

Stupid question here:

Installed the plugin, configured it, but I don't use sidebar widgets. What's the code for placing it on my sidebar?

Dan · 2 years ago

< ?php gajaxsearch(); ?>

Andrew · 2 years ago

Hi, I have installed the plug in but the "search" button takes up most of the space where the search term should be entered. When the site is first opened the long search button sits underneath the search box but then it jumps up on top of it. Can you help! You can view it at my site: http://rspas.anu.edu.au/rmap/newmandala/

Dan · 2 years ago

It looks like you have some conflicting CSS for buttons and that why it both looks styled like that and is larger than normal.

Andrew · 2 years ago

Here is my layout.css Any idea where the problem is?

/* reset
--------------------------------------------------*/
body,h1,h2,h3,h4,h5,h6,p,form,fieldset {margin:0;padding:0;}
.low {display:none;}


/* body
--------------------------------------------------*/
body {


margin:0;
padding:15px 0;
font-family:Arial, Helvetica, sans-serif;
font-size:75%;
line-height:1.6em;
text-align:center;



}


body#commentspopup {padding:0;}


/* headings
--------------------------------------------------*/
h1 {font-size:30px;}

#content h2 {
margin:0 0 18px 0;
font-family:Georgia, serif;
font-size:1.6em;
font-weight:normal;
}

#content h3 {
margin:0 0 18px 0;
font-size:1em;
}

#content h4 {
margin:0;
font-size:1em;
}

#content.archive h2 {margin:0 0 26px 0;}

#content.archive h3 {
margin:0 0 10px 0;
font-family:Georgia, serif;
font-size:1.3em;
font-weight:normal;
}

#content.archive h4 {
margin:0 0 18px 0;
font-size:1em;
}

#content.archive h5 {
margin:0;
font-size:1em;
}


/* links
--------------------------------------------------*/
a {text-decoration:none;}

a img {border:none;}


/* paragraphs, lists, etc
--------------------------------------------------*/
p {
margin:0;
padding:0 0 18px 0;
}

ul {
margin:0 0 0 1.4em;
padding:0 0 18px 0;
}

ul ul {padding:0;}

blockquote {
margin:0;
padding:0 18px;
font-style:italic;
}

pre {
overflow:auto;
margin:0 0 18px 0;
padding:4px;
}

pre, code, kbr {font-family:Courier, Monaco, monospace;}

code, kbr {padding:0 2px;}

abbr, acronym {
font-size:0.9em;
letter-spacing:1px;
}


/* images
--------------------------------------------------*/
img.left {
float:left;
margin:0 12px 0 0;
}

img.right {
float:right;
margin:0 0 0 12px;
}

img.center {
display: block;
margin:0 auto;
}


/* container
--------------------------------------------------*/
#container {
width:690px;
margin:0 auto;
padding:30px 30px 0 30px;
text-align:left;

}

#commentspopup #container {
width:455px;
padding:0 15px;
}


/* header
--------------------------------------------------*/
#header {
height:115px;
padding:0 0 0 18px;
}

#header h1 {
/*display:none; This will hide the text in your header */
padding-top:50px;
}



/* navigation
--------------------------------------------------*/
#navigation {
height:2.7em;
line-height:2.7em;
}

#navigation ul {
margin:0;
padding:0;
}

#navigation li {
float:left;
margin:0;
padding:0;
list-style-type:none;
border-right:1px solid;
white-space:nowrap;
}

#navigation li a {
display:block;
padding:0 18px;
font-size:0.8em;
text-transform:uppercase;
letter-spacing:1px;
}

* html #navigation a {width:1%;} /* see http://www.positioniseverything.net/explorer/es... */

#navigation form {
float:right;
height:100%;
width:189px;
padding:0 15px;
border-left:1px solid;
line-height:0;
}

#navigation form fieldset {
/* centering the search form could've
been done way more elegant but IEWin
and Opera refused to follow the rules */
margin-top:7px;
border:0 solid; /* Opera */
}

* html #navigation form fieldset {margin-top:7px;}

#navigation #s {
height:1.5em;
width:140px;
margin:0 5px 0 0;
padding:0;
border:1px solid;
font-size:0.8em;
vertical-align:middle;
}

#navigation #searchbutton {
height:2em;
width:auto;
padding:0 1px;
border:1px solid;
font-size:9px;
letter-spacing:1px;
text-align:center;
vertical-align:middle;
}


/* content
--------------------------------------------------*/
#content {
float:left;
width:455px;
padding-top:32px;
}

.singlecol #content {
float:none;
width:550px;
margin:0 70px;
}

#commentspopup #content {
float:none;
padding-top:0;
}


/* entry
--------------------------------------------------*/
.entry {margin:0 0 40px 0;}

.entry .info {
position:relative;
margin-top:-3px;
padding:3px;
border-top:1px solid;
border-bottom:1px solid;
font-size:0.9em;
}

.entry.single {clear:both;}

.entry.single .info {margin:0 0 22px 0;}

.entry .info a {
margin-right:6px;
padding-right:9px;
border-right:1px solid;
}

.entry .info em {
padding-right:6px;
font-style:normal;
}

.entry .author,
.entry .editlink a {
margin:0;
padding:0 0 0 10px;
border-left:1px solid;
border-right:none
}

.entry #filedunder {
clear:both;
padding:3px 0 0 0;
font-size:0.9em;
border-top:1px solid;
}


/* mini-entry
--------------------------------------------------*/
.minientry {
position:relative;
margin:0px 0 35px 0;
padding:10px 0;
border-top:1px dotted;
border-bottom:1px dotted;
}

.minientry p {padding:0;}

.minientry .commentlink {
margin-left:3px;
padding-right:7px;
border-right:1px solid;
font-size:0.9em;
}

.minientry .permalink {
margin-left:3px;
font-size:0.9em;
font-style:normal;
}

.minientry .author,
.minientry .editlink a {
margin-left:6px;
padding:0 8px 0 10px;
border-left:1px solid;
font-size:0.9em;
font-style:normal;
}

.minientry .editlink a {margin:0;}


/* comments
--------------------------------------------------*/
#comments h2 {margin-bottom:24px;}

#comments h2 a {
margin-left:2px;
padding-left:6px;
border-left:1px solid;
font-family:Arial,Helvetica,sans-serif;
font-size:0.55em;
}

#comments ul {margin:0 0 0 20px;}

#comments li {
position:relative;
margin-bottom:18px;
}


#comments li p {padding:0 0 10px 0;}

#comments .header {
position:relative;
min-height:19px; /* 19 + 3 +3 = 25px = height of gravatar */
margin:0 0 10px 0;
padding:3px 6px;
}

* html #comments .header {height:19px;} /* IEWin */

#comments .header strong {font-family:Georgia,sans-serif;}

#comments .header .gravatar {
position:absolute;
top:1px;
right:1px;
}


/* form
--------------------------------------------------*/
form {padding:6px 0;}

#commentform, #contactform {margin-bottom:18px;}

form fieldset {border:0 solid;} /* Opera */

form p {
padding:6px 0;
border-bottom:1px solid;
}

form label {
display:block;
float:left;
width:60px;
}

#commentform label {margin:0 15px 0 15px;}
#contactform label {margin:0 15px 0 0;}

form em {
margin-left:5px;
font-size:0.9em;
font-style:normal;
}

form input, form textarea {
padding:3px;
width:200px;
border:1px solid;
font-family:Arial,Helvetica,sans-serif;
font-size:0.9em;
}

form textarea {overflow:auto;}

#commentform input {width:200px;}
#commentform textarea {width:325px;}
#contactform textarea, #contactform #bx_subject {width:465px;}

* html #commentform textarea {width:320px;} /* IE WIN; but why? */
* html #contactform textarea,
* html #contactform #bx_subject {width:445px;} /* IE WIN; but why? */

form .button {
width:90px !important;
border-bottom:1px solid;
font-weight:bold;
}

#commentform .button {margin-left:90px;}
#contactform .button {margin-left:75px;}

form .hiddenfield {display:none;}

form .info {padding-left:90px;}


/* archives
--------------------------------------------------*/
.archive .postspermonth {
margin:0;
list-style:none;
}


/* content misc
--------------------------------------------------*/
.next a {float:right;}
.previous a {float:left;}


#entrynavigation {
overflow: auto;
height:1%;
margin-bottom:13px;
padding-bottom:13px;
border-bottom:1px solid;
font-size:0.9em;
}


/* subcontent
--------------------------------------------------*/
#subcontent {
float:right;
width:205px;
padding:15px 0 0 15px;
font-size:0.9em;
line-height:1.5em;
}

* html #subcontent {padding-top:32px;} /* dirty fix for IEWIN; temporary! */

#subcontent ul, #subcontent p {margin:0 10px;}


/* subcontent headings
--------------------------------------------------*/
#subcontent h2 {
margin:18px 0 10px 0;
font-family:Georgia,serif;
font-size:1em;
line-height:1em;
}

#subcontent h2 em {
display:block;
padding:5px 10px;
font-style:normal;
}


/* subcontent list
--------------------------------------------------*/
#subcontent ul li {
margin:2px 0 2px 18px;
padding-bottom:2px;
border-bottom:1px solid;
}

#subcontent li a {
padding:1px 0;
height:1%; /* IE WIN */
}

#subcontent ul.categories li ul {margin:0;}

#subcontent ul.categories li li {
margin:0;
padding:0 0 3px 0;
border-bottom:none;
}

#subcontent ul.categories li ul ul {margin:0 0 0 16px;}


/* calendar
--------------------------------------------------*/
#wp-calendar {
display:inline-table;
border-collapse:collapse;
width:185px;
margin:0px 10px 0 10px;
text-align:center;
}

#subcontent table caption {
margin:-5px 10px 0 10px;
padding-bottom:5px;
border-bottom:1px solid;
letter-spacing:0.1em;
}

#subcontent table thead tr {border-bottom:1px solid;}

#subcontent table th {border-bottom:1px solid;}

#subcontent table td {
width:200px; /* maximaize width; honestly, I don't know much about tables... */
padding:1px;
font-size:0.9em;
}

#subcontent table td#today {
padding:0;
border:1px solid;
font-size:1em;
font-weight:bold;
}

#subcontent table td a {
display:block;
border-bottom:1px solid;
font-weight:bold;
font-size:1.15em;
}

#subcontent table tfoot {border-top:1px solid;}

#subcontent table tfoot a {
border:none;
font-weight:bold;
}

#subcontent table tfoot #prev a {text-align:left;}
#subcontent table tfoot #next a {text-align:right;}


/* footer
--------------------------------------------------*/
#footer {
clear:both;
padding:40px 0 15px 0;
font-size:0.9em;
}

.singlecol #footer {
padding:25px 0 15px 0;
}

#footer p {
padding:12px 0 18px 0;
border-top:1px solid;
}

#footer strong {font-weight:normal;}

.singlecol #footer p {
padding:12px 70px 18px 70px;
}

Andrew · 2 years ago

Sorry about the long posts! And here is my spring_flavour.css Do I need to make changes in both?

Edited:

form .button {
width:90px !important;
border-bottom:1px solid;
font-weight:bold;
}

Dan · 2 years ago

I edited your comment with the CSS that is causing the problem. Just take that out.

Andrew · 2 years ago

Thanks for your help but still not working. I took that section out of the layout.css but the problem is still the same. AW

Dan · 2 years ago

Well it's definitely because of button styling. You'll notice that your comment submit button is the same style and size. just look through your CSS for an input style with either .btn or .button.

Gerben · 2 years ago

Not working over here also....

It looks like your search doesn't work either?

Gerben

Mr.Mark · 2 years ago

First of all i wanna say thank you for making the search option so much more attractive. i bet a lot of people now just wanna search for everything instead of reading it just like the normal way.

but the only thing that's not really good with my version of the plugin is the layout it comes with.
i have installed the plugin and tried to begin styling it with my own custom CSS but before i got to the styling part i already noticed a slight glitch in the layout itself.
i tried editing the layout in the plugin file itself but even there i had no luck. so maybe someone can help me out here and get me back on the search of Google ajax again.

a screenshot of my layout at the moment: http://tinyurl.com/2t2s2n

Dan · 2 years ago

That's strange. It looks like it's not being added to your sidebar list. Are you using widgets? If so try placing it at the top and see if it's still pushed over the edge. If not make sure it's in a li tag like the other items in your sidebar.

Mr.Mark · 2 years ago

apparently it's not inside a tag

here's a sample of the code that should be my AJAX search widget:
Lost something?








Mr.Mark · 2 years ago

like this then: http://tinyurl.com/ytdvvd