Forum Replies Created
-
Posts
-
Hi!
The latest plugin version (4.5.3) deals with apostrophes a bit better then the older ones. Still, it is a bit more complicated problem, as apostrophes usually raise security concerns. The older plugin versions simply ignored apostrophes, the new one uses a better escaping method which should work in most cases. There also was a changed in wordpress core code lately regarding safely storing these “special” characters.
If you are using an older version, I suggest updating to 4.5.3, it should make a difference. Safe update guide.
Hi!
I managed to find the cause of the problem, it wasn’t easy 🙂
The queries work perfectly fast, even though there are over 1 million keywords, luckily this was not an issue. There were 3 problems:
1. On the search settings page the product custom post type was not selected, because woocommerce was disabled. After enabling the I was able to add the product custom post type, but there was still no response.
I enabled the debug mode in your wp-config.php file and temporary increased the memory limit to 1GB to see what error message is shown.
There was still no error, but after a step-by step debugging I found the cause, which is the second issue:2. The search tried to get the authors of the post, but most likely because of the database size, the wordpress internal function “get_users()” failed. It took over 60 seconds to get 10 users by IDs. I’m not sure if this is some kind of bug within wordpress Core, but it looks like it.
Anyways, to solve the problem, I simply disabled this part of the code, so the author is no longer shown in the results list.3. A minor issue was that the index table was build 25 post at a time (as default option) and at some point it failed. But since your server is extremely powerful, I increased this number 2000, so it build the index without issues in 2 minutes.
Now the search works without problems. Make sure you test ever single page before production, because the “get_users()” function is used widely by plugin developers – so it’s a potential source of failure in other plugins as well.
Plus one more suggestion: I recommend not using the frontend search settings at all with a database size like yours. The category filtering especially. It requires a table join operation, which is fine on smaller databases, but on yours it may cause performance spikes.
Let me know if you need any more help.
Hi!
Can you please provide temporary back-end and FTP details to take a look at your configuration and debug through the search code?
If the configuration is correct, it might be a yet unknown issue.
To safely provide FTP and back-end access edit your first post in this thread, or upload a .txt file with the details. Both methods are safe and visible only to me an you.For the in-stock status I can only think of a custom code solution. I’ve quickly put together a small code snippet for you, that might work. Try putting this code somewhere into your themes functions.php file in your theme directory:
[php]
add_filter( ‘asp_pagepost_results’, ‘asp_stock_status_titles’, 1, 1 );function asp_stock_status_titles( $pageposts ) {
foreach ($pageposts as $k=>$v) {// Get the stock status
$stock_status = get_post_meta( $v->id, ‘_stock_status’, true);if ( $stock_status == "" ) continue;
// Add stock status string
if ( $stock_status == "instock" )
$pageposts[$k]->title .= " – In Stock";
else
$pageposts[$k]->title .= " – Out of Stock";}
return $pageposts;
}
[/php]Hi!
The settings should remain untouched if you deactiavate, delete, download and install the new version.
If you want to make sure everything is 100% fine, you can go through this safe update guide: https://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/update_notes.html
Sure 🙂
Try modifying the code above to something like:
[code].asp_main_container {
margin: 0 auto 26px auto !important
}[/code]..where the 26px is the bottom margin, you can change that to anything you want.
Also, if I may suggest another thing. I noticed that the theme is adding a bit of a box shadow inside the input field when focusing it. If you want to get rid of that light grey shadow, you can use this code:
[code].probox .proinput input:focus {
box-shadow: none !important;
}[/code]I mean it might be a search setting related to that, but I’m not sure.
Can you please try the following:
– disable the W3TC plugin temporary, and check if the search works then?There are no error messages in the console, it is just not returning any results. If you want, you can provide temporary admin and FTP access and I will debug through the search code to see if there is anything wrong. You can edit your first post in this thread or upload a .txt file with the details – both methods are safe and only visible to me and you.
Hi!
Unfortunately there is no option for that, because it depends on the container element alignment as well.
I suggest trying the following custom CSS code, it works most of the time:
[code].asp_main_container {
margin: 0 auto !important;
}[/code]Okay, I thought it’s not working at all, this is different.
If you disable the W3TC, then it starts working? It does not look like to me that there is a conflict. No error messages in the ajax response. It looks more like there is something wrong with the configuration.
Hi!
Sure! It looks to me that a fixed width of 330 pixels is the closest for your suggestion. I changed the desktop width to 330px on the theme options panel: http://i.imgur.com/OS15BBB.png
The search bar will still adjust to the optimal width on mobile devices.
It might take some time till the cache clears and the new width applies.
Hi!
Can you link me to a page where the search is active?
I think it might be a minification issue. The ajax search pro javascript is already minified and it does not need minification from the W3TC plugin. I believe you can add it as an exception or turn off minification as well.
I don’t think anyone has ever attempted to do this. You also need to make the content available in the database as a post type, or create a new search class file to directly go through the XML file, then after getting the results pass them through the SOAP API in the preferred format.
I’m not sure if there is a pre-made tool for this, but if there is, I would rather recommend using that. I would be a huge time saver for this task.
Hi!
Unfortunately this is way beyond the plugins capabilities. It’s definitely possible, but with lots of custom coding.
Can you please link me to a page where this is different? I browsed around the site, but I couldn’t find any.
If it’s used as a widget then I can see two possible causes:
– The widget position does not exist on those pages, it’s not likely, but possible.
– Or more likely the pages are cached and displaying the initial content yetIt does not sound like something with the search plugin, but I want to be sure.
