Forum Replies Created
-
Posts
-
Wait a minute, I just opened the zip file you attached. That’s corrupted, directories and files are missing from it, that’s why you get the error message!
Please try to download the file again from codecanyon. The file should be over 1MB, definitely not 300k.
Okay, let’s try something.
Open up the wp-content/plugins/ajax-search-pro/ajax-search-pro.php file and go to line 13, where you should see this:
[php]
define("ASP_PATH", plugin_dir_path(__FILE__));
[/php]change that line to:
[php]
define("ASP_PATH", untrailingslashit(plugin_dir_path(__FILE__)) );
[/php]Now try to activate the plugin again, if it throws the same error message, then it’s something else. Copy/pase the error message you get after this change.
Hi!
May I ask what kind of server are you using? I’m guessing it some kind of windows server based on the paths. It looks like there is some kind of directory/path issue. My first guess would be that the plugin_dir_path(__FILE__) function might return an extra backslash, but I’m not sure if that’s the cause at all.
I just chekced on your backend, and the custom field does not contain the url, but a number. Here you can see it: https://i.imgur.com/PyfSLgm.png
And that’s what is visible on the frontend as well. Normally I can’t offer 3rd party plugin support, but in this case I can probably help you to get around this.
It looks like that the number is actually the ID of the image, that has been uploaded. There is a filtering function available for the image manipulation for ajax search pro. Try to copy this code into your theme’s 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]I’m not sure if it will help, but it’s worth a try.
This ticket is a duplicate of: https://wp-dreams.com/forums/topic/search-logic/
I’m closing this thread, you will get a response to your first thread soon.
Hi!
Are you sure, that the custom filed content is right? Form what I can see on your site the image urls are simple numbers, like “58” and “57”.
It seems like the custom field value is a number instead of an image url, that’s why it isn’t working.No problem!
1. No worries, it won’t disappear on updates.
2. I see now. It’s not related to chrome, it’s because of the touchscreen. It’s an intended behaviour because some mobile devices had issues with disappearing keyboards, so I rather had it disabled. The next version will have it enabled, unless I find an issue with it. (so far it’s working)
That looks all right to me, that’s the standart wordpress htaccess indeed.
No, there should not be any .htaccess file in the plugin directory, so it’s ok as well.
Well, it means that the server is restricting the access to php files outside the root directory I guess.
Take fore example this file: http://wordpress.philiplee.ie/~philiple/wp-content/plugins/ajax-search-pro/filters.txt
It’s accessible because it’s a txt file.
Now try this one: http://wordpress.philiplee.ie/~philiple/wp-content/plugins/ajax-search-pro/functions.php
That’s a php file it should be executed, but it’s not, the server returns with an error 500, which is very unusual and it should not happen. It must be restricted somewhere, either on CPanel, or in the apache vconfig files, or the permissions are below 755.Other solution would be to bypass the thumbnail generating script and just show the raw image found. That’s not a very convenient option, because it would show the unresized, unscaled images.
Hi!
Then it’s a simple permission problem. I just tried to clear the cache and the files were cleared nicely. Then I tried searching again, and the files were not re-created, which means that the plugin cannot access the cache folder. It was working on your local MAMP server, because the permissions were ok.
If the permissions are set to 777 via ftp on the cache folder then it means that the server administrator has locked the permission changes via SSH. In other words, you might see 777 on the cache folder, but it’s actually something different in an SSH terminal.
I think you will need to ask the server admin to unblock the access to the timthumb.php file (unless it’s denied in htaccess) or to change the permissions on the cache folder.
You can try different permissions as well, some server hosts do not allow 777. These permissions should also work: 666, 655, 755, 766
755 is a standard for almost every host, you should try that first. You can try that on the timthumb.php as well, it might work.As for the file name differences: You copied the cached files from your local MAMP server to the live version. That’s not going to solve the issue, because the images are re-generated from time to time with a different name in case they are changed. The file names are generated based on the search instance id, image name, timestamp etc.. so that’s the reason why the file names are different.
Oh, I just replied to your other ticket.
Thanks for the details. It must have been a data inconsistency when installing the plugin. I have re-synced the data by saving all the options again, and now it works fine.
Hi!
It’s very hard to tell without further information. First you should try to go through the steps in this knowledgebase article: https://wp-dreams.com/knowledge-base/when-i-type-in-something-the-search-wheel-is-spinning-but-nothing-happens-why/
These issues are rare, and are mostly related to a 3rd party plugin or a theme (mostly duplicate function names or similar). If you can link me to a page where the search is active, I can check the ajax response, maybe it throws some kind of error message that I can examine. In this case temporary administrator and ftp access would be great, so I can do further debugging to find the source of the issue. You can safely provide those by editing your first post and filling out the desired fields.
Hi!
The theme stylesheet is causing the problem, it overrides the input field style and that’s the reason why it looks strange. Try to add the following code into the custom CSS field, which you can find on the search plugin “Theme Options->Custom CSS” tab: (http://i.imgur.com/ns4vcKl.png)
[html]
div[id*="ajaxsearchpro1_"] .probox .proinput input {
padding: 0px !important;
border: none !important;
}
[/html]
This should fix the icon and the input (blinking cursor) issue as well.As for the results, I’m currently testing on chrome, but everything looks fine to me. I tried several keywords and I got results so far: http://i.imgur.com/3IDbqu5.png
Just noticed, the link in the previous post is with https://… it was meant to be http://.. but it’s automatically converted, sorry about that.
Hi!
I just checked on your site.
I think there is either a htaccess or an apache rule set incorrectly, because when I tried to access the timthumb url I get the following error:
http://wordpress.philiplee.ie/~philiple/wp-content/plugins/ajax-search-pro/includes/timthumb.php?ct=0&cc=FFFFFF&q=95&w=200&h=300&a=c&src=http%3A%2F%2Fwordpress.philiplee.ie%2F~philiple%2Fwp-content%2Fuploads%2F2014%2F11%2FUrsula.jpgI’m not sure if this is a permission problem or something else, but you should definitely contact the server administrator. The timthumb library is never executed, because the server does not allow reaching it from the outside.
One thing you should probably try though is to set the permissions on the /wp-content/plugins/ajax-search-pro/includes/timthumb.php file to 777. If it’s not blocked via SSH, then it might help.
Hi!
The next update is focused more on creating radio buttons/range sliders/checkboxes to the frontend selection box.
This has never been an issue yet, because most multisite networks on which the search is used were small with only a few sites I guess, so this didn’t came up.
I will try to come up with something that will make them more distinguishable.
