Forum Replies Created
-
Posts
-
Hi!
The search is looking for results in the wp_posts (or {dbprefix}_posts) table. There isn’t a separate table built for this, mainly beacause it would take up database space for no reason.
In order to have the data on the first website from the second website, you would need to copy it to the wp_posts table, but I highly doubt that this is a good idea.
In my opinion the best option would be to ethier make modifications to the plugin to connect to a remote database (docs.cloudfoundry.org) and parse the data from there, or to copy the data to a new table in the first database and create a parser for that.Both solutions will require some very serious knowledge in PHP, WordPress databases and of course deeop examination of the search plugin.
To answer your question I’m not sure which way is the best to solve this. You might need to do further research on this topic, maybe there is a better way of doing this.
Thank you, that worked!
The search shold work now as intended. The problem was, that the server was not permitting to use a custom ajax handler, so I restored the original that points to admin-ajax.php. Perhaps this was a security issue.
Anyways, you should see the results now. I have never seen so fast server as your in my life.
Hi!
I can’t seem to find the directory you suggested. Perhaps the login does not have access to it? Here is a screenshot of what directories I see: http://i.imgur.com/87Uhqa3.png
The results page is coming from the theme, not the plugin. The plugin does not affect the default results page…
It’s because you need MyIsam SQL tables to work with fulltext, and you most likely have InnoDB. But unless you have like 20000 posts you won’t need fulltext indexing – there is no noticable difference. Please don’t change the database engine unless you are experienced with relational databases.
The slow is most likely caused by a conflict or an unknown error, without ftp access I’m not able to tell.
Hi!
Indeed it’s slow, something is most likely blocking the ajax request. Can you provide temporary ftp access as well? (you can edit the 1st post for that) I can’t tell what is causing the search to be this slow. It should react in 1-2 seconds based on your site speed.
I might only answer tomorrow, it’s 1AM here, and I’m leaving the office.
As your second question, you can’t make them clickable, it’s a bit complicated, but I will consider adding this feature to the future releases.
Hi!
You will not loose your custom settings after update, no worries. Currently there is only the documentation and the faqs available, but those are a bit outdated. The new version comes with a fresh documentation and I’m working on a knwoledgebase as well. It should be up in 10 days.
Hi!
Copy the wp-content/plugins/ajax-search-pro folder over to the main site’s plugin folder, and it should work.
Hi again!
The second issue was indeed a bug in the search code. The problem was, that the search filters the results by category after the actual database query. After retrieving 15 results the plugin filtered all of them, because they did not belong to the proper category, so no results were left. I fixed this by increasing the results count to 30 on the general opions panel, so you should see the proper results now.
The new search version (3.0) is coming out very soon (3-5 days), you will have access to it as well on codecanyon – this issue is completely fixed in 3.0 in a different way. (so after upgrading you don’t need to worry about this anymore)
Thank you for noticing me about this, and I hope you like the plugin despite this small issue.
Hi!
In order to use fulltext search, you need to change the wp_posts table from InnoDB engine to MyIsam. But if you have less then 20 000 posts I would not recommend doing that, as you won’t see any difference in search speed or results. Fulltext search is more for advanced developers, I hihgly recommend not changing anything in the databse unless you are experienced with MySQL.
You can read a quick guide about innodb to myIsam conversion here: https://rtcamp.com/tutorials/mysql/innodb-to-myisam/
But once again, unless you are experienced with mySQL, I don’t recommend changin the engine.As for the second isse, I will do a debugging soon to see why is that happening. The search might not work sometimes because of that.
Thank you for the detailed description and the proper login details, it makes my work a lot faster.
Hi!
I believe I have found the issue. The drag-drop list was too big and the browser could not handle it. I limited the terms count except for product categories. It should work now properly.
You can also leave temporary administrator and ftp access by editing the first post in this thread. I will then take a look at the backend, and see if I can find anything.
Of course it can be resolved, once we find what is causing the issue.
Please try to deactivate all the plugins, except the Ajax Search Pro and see if it works then. If it works with all the other plugins deactivated, then it’s something else conflicting.
You can also try to switch the theme temporary to the default, and see if it’s working then.
Once we find the plugin conflict I will able to reproduce it on my test environment and help with the solution.
