Forum Replies Created
-
Posts
-
Hi!
Unfortunately it is not possilbe. Filtering by custom taxonomies in custom post types is not implemented. Many customers asked for it, but I still couldn’t find a solution.
Hi!
Thanks for noticing me and fixing the issue. The version 2.0 is not final yet. I sent a few out for testing purposes. I will upload it to codecanyon and all of my customers will get a notification email about the update! I attached the alpha version 2 of the search to this post, you may try it if you want, but errors may occur.
Notice: The old search boxes will not work after update. You may have to delete them in the search administrator area and create new ones.
Hi Matt!
Sorry for the late response. I had to do some crucial work on my bachelor thesis. Ok, so the issue is only happening if both the advanced custom fields and the search is activated? If so, then I will check it my test environment.
Oh, mystery solved. There was nothing wrong after all. The reason why the images are not showing, it’s because the site is protected with htaccess username/password and the search script and all the other php scripts are no authorized to access the files. The search tried to create a thumbnail image, but instead of the source image he recieved an error message. Once you remove the htaccess protection, it will work 🙂
Hi!
Can you also provide temporary ftp access? I’m working on this for like 3 hours, but it’s very slow through the plugin editor, and also I made a syntax error in the plugin file, now it doesn’t allow me to fix it, so I deactivated the search.
The problem is, that somehow the image files are getting corrupted until the search recieves them. The files are there, but the search is unable to create a thumbnail. This can be a server issue, plugin compatibility issue, php issue, so I’m still not sure. This is a very uncommon issue, I’m not sure there is a solution, but I will try my best.
Hi!
I managed to fix the issue. The template was using the 1.7.1 jQuery version, which is a bit buggy and conflicting. You may experience some issues with other plugins as well. The search was built with the highest compatibility possible, but somehow that jQuery version managed to break that 😀
The search should now work fine, as well as the page scrolling.
Hi!
I cannot modify the search plugin files in the editor. Can you provide temporary ftp access as well? Don’t know what causes the issue yet.
Hi!
In this case can I have a look at the site and maybe administrator/ftp access? It’s most likely an issue with the output or with another plugin is conflicting, I can’t tell.
Hi!
I’m glad you solved some of the issues. 70 plugins is a nice amount to have. There is a possibility that some of them are conflicting with each other, be aware of that. Try to chmod the ajax-search-pro/cache/ directory to 777, that is where the cached images are stored. Also, turn off all the caching in the search plugin caching settings page, while you are experimenting.
Are the images inside the post content, or in a custom field, or as a featured image?
Hello!
Sorry for the late answer, I was working on another project. I’m attaching a probably fixed version of the slider to this post. Let me know if it fixes any issues. If not, then I will connect to your server via ftp and solve manually.
Thank you!
That might be the problem. You should try to upload it via the wordpress plugin uploader. I’ve attached a screenshot where you can find it. If you upload the file named ajax-search-pro.zip which is inside the archive you downloaded from codecanyon.
If it’s still not working, then can you provide temporary administrator access to your website, so I can try to solve it manually? (you can edit your first post in this thread and there you can fill out the private fields, only you and me will be able to see the usearname and password).
Hi!
Have you unzipped the file you downloaded from codecanyon? It also contains the documentation and the actual plugin.
The aphostrophe is removed intentionally, it’s a security issue, for protecting the database. I’m afraid there wont be an opportunity to change this, it’s very risky. (mysql injections through search input field)
Well, page exclusion should work by entering the post/page id-s at the advanced options field on the search settings page. I couldn’t figure out a more convenient way yet to exclude posts/pages, technical reasons.
I can include this in the upcoming version, it sounds like a great idea!
