[Ernest Marcinko]

Hi!

It seems like it’s only a minor issue with the css setup. I tried to access your site, however it’s giving me a 504 getaway timeout error for the backend and it loads the pages only sometimes. Do you experience the same, or it’s just me?

[Ernest Marcinko]

Hi!

A quick question, can you tell me what type of iPad are you using with which ios version?

I only have an iphone 5 and it works fine for me, but it seems like I need to buy an iPad as well.

[Ernest Marcinko]

Hi!

Could you please grant me temporary admin/ftp access to the beta site you are working on? I’m not sure what is the problem, probably a missing file or a function redeclaration.

Thank you!

[Ernest Marcinko]

Thank you very much! I was just about to answer your questions, but I thought I wait a bit to see if you can figure it out. Thank you for the feedback and the kind words, I’m trying my best. I hope I can release the final version very soon!

[Ernest Marcinko]

Changing the font settings on the typography panel should do the trick. Attached a screenshot of it.

[Ernest Marcinko]

No problem at all!

Let me know if you find anything strange, this version is under heavy testing and not finished yet 🙂

[Ernest Marcinko]

I think it’s only because it’s cached from the first bad version I sent you.
If you have cloudflare or something similar cdn, try to clear all caches. Hitting ctrl+shift+R solved it to me on firefox, but I think the cache content is still there. Let me know if it helped!

[Ernest Marcinko]

Oh I know why. I downloaded from test site with filezilla and it placed an extra blank line there. Here you go, this should work now.

[Ernest Marcinko]

Here is the 2.0 version alpha.

Please delete the old search from the plugins before installing, along with the searches you have already configured (it’s unfortunately not compatible backwards)

You should see tons of new features on the administrator area. It’s a bit harder to configure, but it should work better.

[Ernest Marcinko]

Ok, I think I found the source of the problem. There is a css property on the style1.css line 514 “content:…” and it’s somehow bugged, thus the rest of the styling is not loading after that line. As far as I recall I fixed this in the 2.0 version alpha, I will send you copy to try it out in a few minutes.

• This reply was modified 12 years, 5 months ago by Ernest Marcinko.

[Ernest Marcinko]

Hi!

I just checked the website you give in ie9 and 10 and it looked fine to me. Can you perhaps add screenshots of the issue? Which ie version are you using?

[Ernest Marcinko]

Hi!

In this case, you can use the @media query css selectors. These will help you to determine the screen width aka. separate the mobile phone width from desktop. In this case you can change the width of the search + add any other rules you want. I guess the text by the search and the search is in a floating div element, which instead of making new lines, they are placed next to each other. To sum up everything, you can use something like this:

/* Regular pc & others */
#ajaxsearchprowidget-4 {
  width: 486px !important;
}

/* Smartphones (landscape) ----------- */
@media only screen 
and (min-device-width : 350px) 
and (max-device-width : 600px) {
  #ajaxsearchprowidget-4 {
    width: 265px !important;  /* Was originally 486px */
    float: none;
    margin: 0 auto;
  }
}

The “float: none;” property should place the search in a new line and the “margin: 0 auto;” should place it to the middle. With this code you can have different search width depending on the screen size. Please note, that I can’t test these codes, I’m just hoping it helps.

[Ernest Marcinko]

Hi!

In this version your can’t change the width of the plugin, it’s adjusting automatically to the container element. The best way to change the width is to add the search shortcode inside a div element and change the div’s width, like:

<div style='width:300px'>
  <?php echo do_shortoce(...); ?>
</div>

let me know if it helps!

[Ernest Marcinko]

Hi!

I couldn’t find the cause of the issue, but I found a way to fix it. The container element of the search widget shrinks by 8 pixels when the search query is made. The initial size of this container is 486 pixels. Anyways, all you need to do is add the following lines of css into any css file that is loaded on your website (I would recommend a css file from the template):

#ajaxsearchprowidget-4 {
  width: 486px !important;
}

I didn’t want to change anything on the backend, let me know if you need any more assistance!

[Ernest Marcinko]

Oh I see what is the problem now, sorry I was thinking of another distance.

You can set this by editing the ” One result item height” on the general options tab in the search settings. Let me know if it helps.

[Author]

Posts