Forum Replies Created
-
Posts
-
Hi David!
Could you please check the response body if debug mode is enabled in wp-config.php? These are only the javascript error messages due to the server response.
Error 500 means, that at some operation the server stops the ajax process with an error 500. If debug mode is enabled, it might send the error message as well with the ajax response. You can check that on your browsers Network panel:
– before typing in anything: http://i.imgur.com/KBJnv4Z.png
– after typing in a phrase, you check the failed response: Step 1, Step 2Hopefully there will be some kind of error message.
Indeed! I digged a bit more and I found a yet unknown issue. It wasn’t a space character, but actually a dash ‘-‘. When designing I set a delimiter to a dash character, so taxonomy names with a dash in cause this problem. It should display correctly now.
I’m including the fix to the upcoming version of course.
Hi!
I’ve found the problem. One of the taxonomy slugs had a blank space ” ” character in the middle and the drag-and-drop could not handle it. I’ve made a correction on the javascript code, hopefully it will work now.
I’ve moved some terms back and forth for testing, so you might need to re-configure that field again.
Great! I’ll make sure to integrate it to the upcoming version so this problem won’t happen again.
Thank you for the 5 star rating, I just noticed 🙂
Hi!
I’ve checked the code and it looks like I forgot to include this feature from the term results, that’s why it’s not working.
The only way around this is to make modifications to one of the files.
You will have to open up the following file on your server: wp-content/plugins/ajax-search-pro/includes/search/search_terms.class.php and replace it’s contents with this: http://pastebin.com/raw.php?i=Zq8AWuui
That should solve the problem.
Once again, try to put it into the Ajax Search Pro custom css field on the Theme Options -> Custom CSS panel: http://i.imgur.com/4IkwDzQ.png
I guess, maybe.
Try to change the file contents to only the php search shortcode:
[code]<?php echo do_shortcode(‘[wpdreams_ajaxsearchpro id=1]‘); ?>[/code]
Hi!
I can’t see the rule on the page, maybe it’s still cached. Try to put it into the search plugin custom css: Theme Options -> Custom CSS panel
Hi!
It looks like something is forcing the form inside the search bar to 0 height.
Try this custom CSS rule to fix the issue:[code]
.proinput form {
height: 100% !important;
}
[/code]Hi!
I’ve found the cause. There is a javascript error caused by on of the the Blog Manager Light plugin scripts, that blocks further page processing. When I disabled it temporary, the search back-end worked again.
Since you gave me FTP access as well, I’ve made a tiny modification to that javascript file to prevent this error.
The file is: public_html\ledigehjerter\wp-content\plugins\blog-manager-light\assets\js\otw-admin-bm-functions.js
and I have added an extra line, number 5.
The search back-end works now, but it’s not a long term solution, since upgrading this plugin will overwrite this change.I will notify the plugin developer to not load it’s plugin javascript files on other plugin pages as it is causing problems. It’s a common mistake by developers.
If the issue appears again, just disable the Blog Manager Light until you configure the search, that’s probably the best way to deal with the problem 🙂
Hi!
Try the following steps, one of them might help:
- Check if the plugin is indeed activated in the plugin manager
- Try to delete and install the plugin again
- Make sure you don’t have any custom back-end themes enabled (custom admin themes might not support some plugins)
Sometimes the plugin manager fails to upload the file correctly and it might cause missing or incorrect files. In that case the above mentioned solutions should work.
If the problem is something else, then I need more information as well to see where the problem might be:
- Can you see the Ajax Search Pro menu on the back-end?
- Did it show any error message upon activation?
- Can you create a new search instance?
- Can you change other plugin settings?
Could you also provide temporary back-end and ftp access? It’s extremely hard to solve a problem without seeing it. You can provide temporary access by editing your first post or uploading a .txt file with the details. Both methods are safe and only visible for you and me.
Hi!
I would love to provide you a way to make this happen, but unfortunately this is not possible without coding.
Links are deprecated from wordpress version 3.5, and it’s not included in the latest versions (only with a plugin), but that’s not the main issue.
The problem is that links are not stored as custom post types, but as a completely different structure in a different table – thus they are not reachable for the search plugin.
The only way to make them work is to create a completely new wrapper, implement it to the plugin and design a new settings page for it – thus lots of lots of coding.
Hi!
I’ve done a good amount of security tests, so far no problems. The query fails every time due to the multiple escape calls.
The problem occures because the plain $_GET[s] value is echoed into the search text field before escaping. I’ve found a quick and effective fix using one internal wordpress call.
If you open up the plugins/ajax-search-pro/includes/views/asp.shortcode.probox.php file and go to line 44, you should see the input field output, and at the end of the line there is something like:
[code]… value='<?php echo isset($_GET[‘s’])?$_GET[‘s’]:”; ?>’ autocomplete="off">[/code]
change it to:
[code]… value='<?php echo get_search_query(); ?>’ autocomplete="off">[/code]
The problem will disappear right away. I’m including this fix in the upcoming version of course.
