Forum Replies Created
-
Posts
-
Hi!
I’m currently working on the upcoming version and if I remember correctly I fixed this as someone reported something similar with the paths.
I think there are only 3 instances of ABSPATH there in the current version. The fixed lines look like this now:
[code]echo file_get_contents(WP_PLUGIN_DIR . ‘/’ . $style[‘magnifierimage’]);[/code]
Would you mind checking if this solution is working in your case? A core developer suggested using the WP_PLUGIN_DIR constant as it should hold the correct plugin directory at all times.
I will mark this path issue solved if you can confirm that this solution works, and we don’t need to worry about this in the future versions anymore 馃槈
Hi!
Could you please provide more information on this:
- An url where the search is visible
- Temporary admin and ftp details if possible (you can edit your initial post for this)
- What is the database size? How much posts/pages/custom content do you have?
- Are you running on a Virtual Private Server or a Shared web hosting? What is the server configuration?
- What type of content are you searching?
- Have you tried changin anything on the search options page?
- What is your site response speed if you test it on: http://tools.pingdom.com/fpt/
Thank you!
Hi!
I can only offer free support related to bugs and errors, unfortunately I don’t have the resources for paid support 馃檨
I’m more than happy to help if you have any issues or suggestions. Let me know!
Hi!
That extra space is coming from the container element in which the search shortcode is placed. It has 10px margin and 10px padding, which adds up to 40px extra space: http://i.imgur.com/2BmqhZs.png
By moving the shortcode from the container or removing the padding and margin should solve the problem.
Hi!
Indeed, it looks like it. If you can send me an url, I will be able to tell what CSS code might fix this.
Oh, that is the problem then, never use 2 cache plugins at once, it is a very bad idea.
I don’t think that issue should appear again, if you use only 1 caching plugin properly.
Hi!
It looks like that the Advanced Ajax Page loader options are enabled. Please disable those options and the search should work normally after 馃槈
You can do that on the “General Options->Advanced Ajax Page Loader options” tab.
Then it is possible that the WP Fastest Cache plugin cache was not cleared properly. You should rather try W3 Total cache instead. I’m using it on all of my websites, and it’s working extremely well, and it’s compatible with almost every plugin.
Hi!
It is possible to show it as part of the title. On the advanced options panel you will find a few fields regarding that. I also recommend this chapter of the documentation: http://wp-dreams.com/demo/wp-ajax-search-pro3/docs/#advanced_options_advanced_title_and_description_fields
No problem at all, You too 馃槈 If you like the plugin, you can drop a quick rating on your codecanyon downloads page: http://codecanyon.net/downloads
Have a nice rest of the day!
Sure!
On the Theme Options -> Typography panel, the last option “Show more font”. There you can change the color as well 馃槈
It returns to the search results page, but there is nothing to display. Something is not set correctly on the theme I suppose.
If I try the default search page like persona.org.il/?s=讗转专 驻专住讜谞讛
it gives me a very strange layout, no links, nothing.Also the ajax search is not working now, there is no response returned. I remember it worked correctly. If you changed anything you should try to revert it back. You should also remove that code you put there earlier regarding the url fix. (just to prevent any issues)
Hi!
Thanks, that works. I’ve found the problem. There were tens of thousands of custom fields defined and the settings could not list it so it failed. I limited the custom field count to 100, now it will work properly.
Hi!
I have no knowledge of PHP 5.5 issues with the current plugin version. I’m running this server (as well as the demo) on php 5.5 and it works fine: https://wp-dreams.com/phpinf.php
If you are using an older version of the plugin (3.5<) I would recommend updating the plugin - don't forget to check the update notes in the documentation. Are there any specific error messages related to the issue?
