Forum Replies Created
-
Posts
-
Hi!
Your configuration looks correct, so this is most likely an unknown bug yet. Could you please also provide temporary ftp access so I can run diagnostics? I don’t want to edit files via the plugin editor, it’s unsafe.
Hi!
If you are referring to W3C CSS validations, than it’s probably right. Unfortunately the W3C validity does not allow many many properties like SVG fill, rgba backgrounds, background gradients and hundreds of other things. On the other hand every single major browser (including mobile) support these CSS features.
If the search CSS complied the W3C CSS validity, then the plugin most likely would loose all the sales.If you check any wordpress theme, plugin or anything that has CSS files, you will probably find hundreds of errors with the W3C validator. As an example, check out the AVADA theme (300+ errors) or you can check out facebook as well (40 errors on the login page).
There are many many lines of CSS in the plugin only for the proper compatibilty. Since this is a stock product, it has to work with millions of themes and plugins out there as well as with every major browser.
Okays. That might explain it. Grouping is for now only possible by Category or Post type but not by taxonomy. The search is trying to retrieve a category name for a taxonomy which probably results in a fatal error.
The category and taxonomy search is a fairly new feature so I’m working on some additional things regarding them. I’m going to add your request to the TODO list right now. I’m almost done with the next major update (which contains mostly compatibility updates), but I guess I can work out something, since grouping needs an update anyways. I can’t promise it’s going to be exactly how you imagined, but I will add as much flexibility as possible 😉
Will contact you in a few days with an update on this.
Hi!
After logging in I can only see an empty folder. (tried both with FTPS explicit and simple FTP as well, both empty folders). Could you please check the credentials?
Hi again!
I’m attaching a beta version with the CSS changes. Before installing please make a copy of your wp-content/plugins/ajax-search-pro/ folder so you can restore it if you need.
1. After making the backup copy, deactivate and delete the ajax search pro plugin in the plugin manager.
2. Install the attached version.
3. Open the “Compatibility Options” submenu.
4. There is a new option there called “CSS compatibility level”. Change that to “Maximum” and save the settings: https://i.imgur.com/ppYQ7B0.png
5. After clearing your site cache and refreshing your site you should see some (or all) of the CSS issues disappear.Let me know how it goes.
Hi!
By turning off the keyword suggestions. See this part of the documentation: http://wp-dreams.com/demo/wp-ajax-search-pro3/docs/#general_options_keyword_suggestions
You can edit your first post and add the admin and ftp details there, or you can attach a .txt file to your next post with the details. Both methods are safe.
Hi!
Try to open up the plugin settings and save them without changing anything. It should clear the plugin cache. If you have any caching plugins active, you should try to clear that cache as well.
If that doesn’t help, then I might need temporary admin/ftp access as well to run a quick debugging to find out what’s the problem.
Hi!
Thanks for contacting me here. The test version is not ready yet, it might take a few hours. I will send you a test version today if I can finish it. If not, then tomorrow for sure. Thank you for your patience!
Hi!
I’m suspecting a 3rd party javascript (probably from another plugin or theme) which automatically submits the form when pressing the enter key. The search tries to automatically prevent this behaviour, but depending on the method it might fail.
The best you can try is the following javascript code:
[html]
jQuery(document).ready(function($){
var scope = $;
if (typeof aspjQuery != "undefined")
scope = aspjQuery;
scope(".proinput input.orig").keydown( function(e) {
if (e.which === 13) {
e.preventDefault();
e.stopPropagation();
if (typeof(e.stopImmediatePropagation) != "undefined")
e.stopImmediatePropagation();
}
});
scope("input.orig").parent().submit( function(e) {
if (e.which === 13) {
e.preventDefault();
e.stopPropagation();
if (typeof(e.stopImmediatePropagation) != "undefined")
e.stopImmediatePropagation();
}
});
});
[/html]Try to add it to the page footer or header. It might work, but if another javascript file is interfeering with the event listeners this might not work.
Also, try to clear your page as well. If you are using any kind of CDN, then their cache as well. The cache can prevent such settings from application.
Sure. It was the \wp-content\plugins\ajax-search-pro\backend\search.php line 23. It was simply commented out. It’s going to be changed to something else in the upcoming update.
Hi!
This sounds like the image field does not actually contains the image url, but something else. The MIME type error indicates that the browser interpeted it as text, which usually means, that the image url is incorrect.
Moreover the url “http://www.afsdp.org.pe/leguia-la-historia-oculta/610/” is definitely not an image url, it just points to one of your pages.
After diggin up some old tickets I found a similar issue solved for someone. The ACF actually does not store the image url, but the image ID. Thus you need some post-processing function in order to make it work.
This is what solved the issue for him. Put the following code into your themes functions.php file:
[php]
add_filter( "asp_result_image_after_prostproc", "asp_cf_image", 1, 1 );function asp_cf_image( $image ) {
if ($image != "" && strlen($image) < 10) {
$atts = wp_get_attachment_image_src( $image );
if (isset($atts[0]))
return $atts[0];
return null;
}
return $image;
}
[/php]Hi!
It looks like something is caching the stylesheet file. I checked the source and it’s changing, so it’s writeable. Maybe it’s just extended browser caching. Anyways I turned on the Inline styles option on the plugins “Cache Settins” submenu. This way the styles are applied to the header directly and should be visible immediately.
