joe_bopper

Hi,

Sorry for not getting back to you sooner; my email didn’t seem to alert me to your message.

I couldn’t find the issue described on your site (I assume you’ve resolved it in some way already). However, from your description, I get the strong impression that this is a conflict between SEOpress and another plugin/theme (probably the theme).

The reason for this is because this plugin doesn’t change how the search function occurs, i.e., no change to the URL it goes to or the database query made – therefore, no change to the search results. This plugin only puts a bit of html in your menu (and, of course, allows you to place where via the admin area).

Hope this is of any help.

Cheers,
Joe

Thanks very much.

Hi Conny,

Sorry for my late reply.

This plugin only adds in the default WordPress search box to menus. I would have thought that to get it to behave like the Yith plugin would likely require a little tinkering. However, as you’re saying that it is working on desktop, perhaps Yith automatically modifies it.

This plugin doesn’t use any javascript, css, nor inline styles on the frontend, and therefore has no capacity (nor intention) in itself to behave differently from mobile to desktop. Therefore, I think the difference will be coming from Yith and I’d advise asking for support from them.

The only way I can think of doing a potential quick fix would be to add:

add_filter( 'get_nav_search_box_form', function( $current_form, $item, $depth, $args ){
  ob_start();
  do_shortcode( /* INSERT YITH SEARCH FORM SHORTCODE AS STRING HERE */ );
  $new_form = ob_get_clean();
  return $new_form;
}, 10, 4 );

to your theme’s functions.php

Hope this is of help.

Cheers,
Joe

Hi Judy,

It looks very much like your theme doesn’t support html5 and the placeholder attribute isn’t available in prior versions of html. Therefore, unless you can make it so your theme supports html5, a placeholder is unavailable. Here’s how you can do it: https://developer.www.ads-software.com/reference/functions/add_theme_support/#html5

BTW, the “Search” you’re seeing in the current html is for screen readers (i.e., for the blind) and so is hidden from usual view.

Cheers,
Joe

Hi,

I’m afraid this plugin doesn’t have a css file (and even if it did, it is not recommended to alter plugin files as they get overwritten on updates).

I don’t think the Additional CSS section has any kind of restrictions over style rules. I think it’s much more likely that you’re experiencing one of the following: your selectors aren’t specific enough, !important is being used in another stylesheet, or you have a syntax error.

Sorry for taking a while to respond.

Cheers,
Joe

Hi shiftsrl,

Don’t you just want to put your search box as one of your first menu items in Appearance > Customize > Menus?

Cheers,
Joe

Hi Judy,

I’m pretty sure the problem you’re having is because Appearance > Customize still isn’t up to scratch and WordPress has an obsession with not showing you most of the options available. The customizer doesn’t allow change of Screen Options, so instead you must go to /wp-admin/nav-menus.php. In there open the tab in the top right corner and Title Attribute should be a tickbox there. This will allow you to edit the placeholder in the menus page and in the customizer.

Hope this helps.

Cheers,
Joe

Hi agamirzadeh,

I’ve tried to avoid any styles and scripts as much as possible in this plugin to keep it lightweight (in both the front and back).

Thankfully, WordPress core provides the functionality to add custom css without the need to edit your theme. You can do this in Appearance > Customize > Additional CSS in the admin area.

Hope this helps.

Cheers,
Joe

Hi candyg333,

You will need some custom css. It appears your theme is adding a lot of padding on to input tags. I suggest cutting it down with:

.bop-nav-search input.search-field{
  padding: 2px;
}

for example.

Hope this helps and you work out how to sort it fully – should just need a bit of trial and error on css properties.

Cheers,
Joe

P.S., styling is down to a theme and/or the end web developer and not a matter in the responsibility of this plugin. Therefore, I am marking this issue as resolved.

Hi,

I’m afraid that’s something you’re going to have to play around with to work out. I don’t have any apple products and therefore can’t test safari (also styling changes are beyond the remit of this plugin and are naturally going to be custom from theme to theme and site to site).

Cheers,
Joe

P.S., It’s also perfectly understandable to leave safari with aesthetic issues as it has low market share and is truly the worst browser around by a massive margin.

Hi,

It’s css. It’s meant to go in style.css at the bottom.

Cheers,
Joe

Hi,

I’m not sure I understand your issue and I am highly suspicious of the use of a url obfuscator. For these reasons, I suspect this message is spam and am simply marking it as “not a support question.” If this is in error, please reopen the thread (preferably with a rewording of the issue at hand) and I’ll see how I can help.

Cheers,
Joe

Hi mahwash,

Please refer to your previous support thread.

Cheers,
Joe

li.bop-nav-search {
    padding: 20px 0;
}

Hi mahwash,

I’m sorry to say that themeing issues are outside the remit of this plugin. Moreover, such as it is with css, there are a multitude of factors that could be at play. That said, I’ll offer some tips that’ll hopefully be helpful:

* Use your browser’s dev tools (f12) to see the css properties applied and the selectors that choose them. Also, use this for trial and error to work out which properties you need.

* Ensure your custom styles are coming in at the right place in the cascade. This means where it comes in from top to bottom of the page, the selector used, whether !important is coming after your properties or ones employed by your theme, and inline styles (i.e., the style attribute on the html element).

* The css properties position and display are ridiculously important.

* Appearance > Customize > Additional CSS is a good place to add little extras and changes.

Hope this helps.

Cheers,
Joe

P.S. I’m marking this support request as resolved as it is outside the responsibilities of this plugin. That said, if you need any further assistance, feel free to respond and I’ll see what I can do.