[Ernest Marcinko]

Hi!

I see the problem now. The whole search bot was set to rtl direction, which is not supported 100% currently. However I made a few changes, so the input field is now directed to the right and the writing direction should be correct as well.

I’ve also corrected the settings position with visual composer. I added an extra line for the settings to appear below the box and set the results position to “Blocking” on the frontend search settings panel.

You can finish configuring your search now 😉

[Ernest Marcinko]

Hi!

If I try Napoli I see these results: http://i.imgur.com/riCPH2T.png
but no error message. Maybe it was just the cache.

[Ernest Marcinko]

Could you please check the login privileges? I can’t see the plugin manager nor the Ajax Search Pro menu item.

[Ernest Marcinko]

Hi!

Yes it is possible. By turning on the “Redirect to search results page when hitting the return key?” and “Override the default WordPress search results page?” the option in the “General Options -> Behavior” panel: http://i.imgur.com/j2sFKgM.png

[Ernest Marcinko]

Hi!

Could you please re-upload the screenshot and provide and url where the issue is visible as well as with temporary administrator and ftp details?

For starters you should try to switch your site theme and deactivating all other plugins temporary to see if this is a compatibility issue. Let me know!

[Ernest Marcinko]

Hi!

Currently only those options are available. There is an upcoming version very soon, which contains new options regarding user profile fields as they had been requested several times over the past weeks. I’m releasing updates as fast as I can, fulfilling many user requests 😉

[Ernest Marcinko]

I believe it’s the main menu causing that. Some menus tend to block event if there is a javascript handler declared inside them. The best solution in these cases is usually to move the search out of the menu for mobile devices.

However a simple custom CSS rule might help you out:
[html]
.probox .proinput input {
min-width: 200px !important;
}
[/html]

Try to add this to the Custom CSS field of the search or into your theme (if supports custom css). You can also use any of the theme css files. This should solve this issue immediately.

[Ernest Marcinko]

Indeed. It looks like some values within the database are corrupted for that instance. It can happen if the settings are only partially sent, usually at a tiny server outage.

Anyways, I have created another instance (main-search2), it should work perfectly as it holds the default options now. Please reconfigure and replace the one that you use, it should work properly now 😉

Sorry for the inconvenience.

[Ernest Marcinko]

.mo and .po files are not available yet, instead you can use the backend to change the visible text. The “Category filter caption” on the “Layout options -> Filtering options” panel.

[Ernest Marcinko]

Hi!

Some settings were missing for some reason on the frontend. I saved the search instance again and the search should work now.

[Ernest Marcinko]

Hi!

I think I have found the problem. It was a yet unknown bug, but I managed to fix it. The plugin should work correctly now. This fix will be featured in the upcoming version as well.

[Ernest Marcinko]

Of course. This should not be an issue anymore in the future versions.

[Ernest Marcinko]

It was the plugins/ajax-search-pro/search.php file lines 213-215, those lines are now currently inactive.

[Ernest Marcinko]

Hi!

I’ve found the problem. The search was still using fulltext for some reason. I’ve removed that conditional statement, now it should work correctly.

[Ernest Marcinko]

Hi!

The search results page is not part of the plugin, but your current theme. Usually it’s the search.php file in your current theme directory, but please ask the theme developer he will surely tell you where to look exactly.

[Author]

Posts