Forum Replies Created
-
Posts
-
It was my pleasure helping you, and I wish you a happy new year too! 🙂
If you like the plugin, feel free to leave a rating on it on your codecanyon downloads page, it’s greatly appreciated.
Hi!
I’ve googled a bit about this issue, and most likely there might have been a change on your hosting – either IPv6 address or something similar. This code has been around before the update, you just probably didn’t get notices before that.
Can you please try to replace the code with this modified version of this function?
[php] function wd_current_page_url() {
$pageURL = ‘http’;$port = !empty($_SERVER["SERVER_PORT"]) ? $_SERVER["SERVER_PORT"] : 80;
$server_name = !empty($_SERVER["SERVER_NAME"]) ? $_SERVER["SERVER_NAME"] : "";
$server_name = empty($server_name) && !empty($_SERVER[‘HTTP_HOST’]) ? $_SERVER[‘HTTP_HOST’] : $server_name;if( isset($_SERVER["HTTPS"]) ) {
if ($_SERVER["HTTPS"] == "on") {$pageURL .= "s";}
}
$pageURL .= "://";
if ($port != "80") {
$pageURL .= $server_name.":".$port.$_SERVER["REQUEST_URI"];
} else {
$pageURL .= $server_name.$_SERVER["REQUEST_URI"];
}
return $pageURL;
}[/php]let me know if you see any notices with the change.
Hi!
It looks like the redirection to the WooCommerce search page has changed. I’ve chaged the Redirect to url? option on the General Options -> Behavior panel to: ?s={phrase}&post_type=product
It appears to be searching the excerpts now correctly. I have tried “Golden” then “Golden ginger” and the redirections seemed all right now.
Hi Mike!
I’m not sure if that is how you want it, but I’ve quickly changed the input background color from white to transparent on the Theme Options -> Input field layout panel (Search input field background gradient option). It should appear as a transparent magnifier on the front page now.
Also, I’ve turned off the settings icon on the Frontend Search settings -> General panel: http://i.imgur.com/B9iLDSM.png
You are welcome Mark!
The current market of viable search plugins is pretty much limited to a few good ones, all others miss something vital.
To limit the search to a specific subset of pages, you should start with the General Options -> Sources panel. There you can turn off the search in posts first, as you don’t need those for page search – I see you have the diseases on separate pages by starting character.
Then here comes the hard part: Since pages can’t have any categories nor any taxonomies, the only way to exclude the rest of them is one-by-one by their ID’s – On the Advanced Options -> Content panel, with the “Exclude Posts/Pages/CPT by ID’s (comma separated post ID-s)” option.
That might be time consuming, but there is no other way for pages – since you cannot catgorize them by default in WordPress.I’m from Europe, Slovakia to be exact 🙂
No option for that, but there is a CSS trick to convert it to upper case.
I added the following custom CSS rule to convert the title to upper case:
[html]a.asp_res_url {
text-transform: uppercase !important;
}[/html]Yep, I only found that issue.
It’s indeed changing back, but it’s only a visual bug – the classic green options remain loaded anyways. I’m going to fix that in the upcoming version.
Hi!
1. Yes, it is a known issue with horizontal and polaroid results with the current release. It’s getting fixed in the next release very soon.
2. Yes it is possible, you can change that on the advanced options panel: http://i.imgur.com/0cUx50e.png
Hi!
Sorry for the late response, I was on a family vacation.
I see you managed to put the search shortcode to the header.php file. It was almost correct, I had to remove the surrounding form element, it was causing problems.
Also after fixing that, I’ve added the following custom CSS to reduce the width a fix the floating and margins for the home page search:
[html]/* Front page ajax search pro fixes */
#main-menu-wrapper .asp_main_container {
width: 200px !important;
height: auto !important;
margin-top: 12px !important;
}[/html]That reduces the width for the search to a correct 200px to fit into that space, but only for the header search instance.
I still see the old shortcode if I open the Home page editor: http://i.imgur.com/pX9nl9I.png
This shortcode is used:
[html][wpdreams_ajaxsearchpro id=1][/html]
and it should be this one:
[html][wpdreams_ajaxsearchpro id=3][/html]
I have found the problem 🙂
You are using the wrong shortcode on the front page. I see the shortcode of the sidebar search instead of the frontpage one. Simply just replace it, and it will work 🙂
Hi Mark!
Thank you for your kind words!
I tried to log-in with the provided details, but the site tells me to check my phone for a log-in code. Can you please disable the phone authentication on that account temporarly? I will check again then.
I’m guessing a cache issue based on your description, but I will check the configuration and do some tests to confirm.Hi!
Sorry, I was on a family Christmas vacation, I’m answering tickets today as fast as I can.
I have messaged my ISP if they can allow port forwarding for me so I can connect, but they refuse to do so. I have tried several mobile internet providers as well, but all of them are of course behind a NAT firewall so active connection is not possible. I also tried different computers, but no luck.
The only possible solution for me to connect is for you to allow passive connections to your FTP server. You might have to message your host to do so. Passive mode is widely used because of issues like this, so they will most likely allow it. Can you please ask your hosting provider to turn on passive mode? I’m out of options here and I would really like to help you.
Hi!
Are you sure that those are custom fields indeed? If so, they should appear on the settings page.
Do you know the names of those fields? They might be set to private and have an underscore “_” character before their names.There is also a limit for listing custom fields on the search options page, but it’s set to 500. I counted the items there with javascript, there are 242 fields there currently, so it’s not that.
If you tell me the names of the custom fields, I might be able to investigate why it’s not there.
