Forum Replies Created
-
Posts
-
I didn’t get the .htaccess file, but If the .htaccess is ok, then it’s either a plugin redirecting the request, or the Apache vconf files are causing it.
The url http://quiquealien.com/wp-admin/admin-ajax.php should return a “0” if you open it in the browser, but it does not, it’s redirected to a 404 error page.
Check for example wordpress.org ajax url: https://wordpress.org/wp-admin/admin-ajax.php
or the ajax url of this site: https://wp-dreams.com/wp-admin/admin-ajax.phpYou can try deactivating a few plugins (mainly cache plugins) to see if any of them is causing this. The 404 problem is unfortunately not related to Ajax Search Pro, so I honestly don’t know what might exactly cause it.
I see a different error now, which might bring us closer to the solution:
http://quiquealien.com/wp-admin/admin-ajax.php is missing, error 404
That is not good at all, that’s an internal wordpress file. Please check if that file exists on your server in that directory, it’s responsible for all WordPress ajax requests on the front-end and back-end.
If the file is not missing, then there must be a malfunctioning .htaccess rule in your .htaccess file, which redirects all requests to the admin-ajax.php file to the default 404 error page.
Hi!
Uninstalling or deactivating does not execute or does anything, so it’s not related to that. What I’m thinking, that this might be some kind of cache issue. If the cache is not cleared properly, the front-end might still try to load the ajax search pro scripts, but they do not exist anymore, which might cause such problems.
There must be something else related to this, perhaps another plugin is requesting something from Ajax Search Pro, or maybe a custom code.
The only error I can see on the log is this:
http://www.beautypediya.com/wp-content/plugins/woocommerce-multistep-checkout/script.js?ver=4.3 Failed to load resource: the server responded with a status of 404 (Not Found)
It means that one of the requested script files from the WooCommerce multistep checkout plugin is missing, but it’s not related to Ajax Search Pro, but this also might not be the cause.
Can you point me to a page which break if the plugin is deactivated, so I can try it? I don’t want to change anything on your site, since I don’t understand the language 🙂
I will try to de-activate and check for errors and do debugging if I can.Hi!
Just checked the site, the server gives a very weird response with dozens of different cookies, that should not be there, also there is a repetitive no-cache pragma printed all over the response header.
I don’t think it’s related to the search plugin, as it does not manipulate the response headers in any way. It migth not be a plugin related issue at all. I’m thinking of a lower level server-side cache like varnish or something similar, I honestly don’t know, it’s impossible to tell based on the response only.
What you can try, is to turn off the custom ajax handler, and use the WordPress default on the Compatibility Options submenu: http://i.imgur.com/0PWzHSc.png
I have seen similar issues with some security and cache plugins, which sometimes block ajax requests as false positives, causing no response. If that’s the case, then the suggestion above should help.
Hi!
It’s a new issue with the latest FF version. Luckily there is an easy fix:
Open up to the Compatibility Options submenu under the Ajax Search Pro menu, where you will find an option called Javascript Source. Try to change that option to “Non Minified”: https://i.imgur.com/E5JEMiR.png
I will upload a bugfix version later today to codecanyon, that fixes this automatically.
Hi!
Unfortunately this is not yet possible with an option on the back-end.
I’ve added this as a request for the upcoming version, I see what I can do to make it work.
Hi!
I tried to upload a .docx file, and the following mime type is in the database:
application/vnd.openxmlformats-officedocument.wordprocessingml.document
Looks weird, but it might work 🙂
Hi!
Thank you for the kind words 🙂
I found the problem, you did nothing wrong. I’m not sure what’s the exact cause, but I have a feeling it’s related to the latest firefox update, as the issue came up on an unchanged piece of code, and someone else just reported this as well.
Anyways, I logged in to your site back-end, and changed Javascript Compatibility option on the Compatibility Options submenu under the Ajax Search Pro menu. Luckily, that solved it immediately.
I will investigate this issue further on my test environment 🙂
Indeed.
I see some kind of weird minification error, but I have no idea what’s causing it. Anyways, there is something you can try. Open up to the Compatibility Options submenu under the Ajax Search Pro menu, where you will find an option called Javascript Source. Try to change that option to “Non Minified”: http://i.imgur.com/E5JEMiR.png
You might have to clear your site, browser and CDN cache if you have them enabled in order to see a change.
If the “Non Minified” option does not work, try the remaining two as well.
Hi!
I’m not sure if you were able to solve the problem, but I’m getting results when I’m typing. Let me know if the problem still exists.
Hi!
I believe ACF runs a function through that array to display it, or uses some kind of code to parse through the array. It means that not the checkbox HTML is stored in the custom field, but some kind of array values, that are transformed into checkboxes.
You can ask the ACF author how the checkbox array is transformed into actual HTML checkboxes, then I might be able to suggest a customization or filter function to append the transformed code to the result list. It’s probably going to be some kind of function or a small snippet from the ACF plugin code.
Hi again!
I think I might have found something, that’s related to the new version as well.
Please wait with the update for 12 hours till it’s approved on codecanyon, I’m uploading a bugfix right now regarding category exclusions and stuff.
Hi!
Sorry for the late answer, I’ve been a bit busy releasing the new version.
I’m not sure, this should definitely work, the configuration looks all right to me.
I suggest downloading and upating the latest version, just to make sure it’s not something in plugin version 4.0. How to update.
Let me know if that changes anything.
