[Ernest Marcinko]

Sorry about that. I wish I could afford more android devices to test with, or even better, I wish android worked the same on every device.

[Ernest Marcinko]

Hm. The only closest emulator I could find is the chrome dev tools emulator. I have tried all the android phones on the list, but no errors. I guess it’s not representing accurately the android platform.

I don’t know what else to do, because unfortunately it’s working on both of my android devices and I don’t know anyone near me with that phone model to test it with.

[Ernest Marcinko]

Hi!

Sorry, I see now, my bad. I have found the problem, it was actually a bad value in the relevance options panel: http://i.imgur.com/f1McpeE.png

It should work now as intended.

[Ernest Marcinko]

Hi Steve!

May I ask what type of browser was the phone using, and which version of android was it running? Also the mobile phone type would be helpful. I just tested your site with a random samsung phone (I guess its ace II or something) and with a samsung galaxy tab, and it’s working for me. I also tested the demo site, just to double check.

Android is very tricky, it has many many versions with lots of browsers and it varies for each device. To be honest with you, I have absolutely no idea why it wasn’t working on that phone. That’s the only reason I prefer apple, it makes the developers work less painful.

The problem can be anything, literally. The phone, the browser, a plugin, a javascript code, an unknown exception, a browser plugin, cache inconsistencies and many other stuff as well.

[Ernest Marcinko]

Hi!

Can you please link me to a page where the search is enabled? I can’t seem to find it anywhere.

Also, I’m glad you provided vps login info, but I still cannot log in to the backend of your site, and I don’t want to change anything yet with the hosting control panel. Can you please add a login to the musme.ru/wp-admin backend area as well? Then I can check the search configuration.

Thank you!

[Ernest Marcinko]

Hi!

Sorry, I had an urgent issue to fix today and had to leave eary, I didnt have time to check your problem. Tomorrow morning when I get back to the office I will do it first thing. Don’t worry, it’s probably only something with the configuration. Thank you for your patience!

[Ernest Marcinko]

Hi!

If the variations were enabled before, it might have been cached. If the search cache is enabled, please disable it and see if it works then.
Also, if you have other cache plugins (like w3tc or super cache) you should try to empty the cache of those plugins as well. Let me know if it worked.

If it’s not hepling, then please link me to the page where it’s happening, and I will take a look at the output.

[Ernest Marcinko]

Of course. Here is the version containing the changes, soon it will be available on codecanyon as well.

[Ernest Marcinko]

Hi!

I just looked at the site, I’m not sure if you fixed the saving issue, but I tried to change the theme and a few things, and it’s working for me. I enabled “force inline styles” and changed the javascript source, just to be sure.

The reason why there were no results, it’s because a fatal error was interrupting the ajax call:

Fatal error:  Call to undefined function aq_resize() in /home/shop4mic/public_html/kartuse-tonerji.si/wp-content/themes/neighborhood/includes/swift-framework/sf-content-display/sf-products.php on line 143

This is coming from the theme, more exactly some function is called somewhere, which is not declared. I fixed this by changing the ajax url in the search code. But this error in the theme may cause other ajax plugins to malfunction. In this case please contact the theme developer, otherwise it should be fine.

The search should work as normal now.

[Ernest Marcinko]

Hi!

It looks like I have found the problem. It was a very strange bug, it took me almost an hour to find it. Basically something went wrong on saving the values, because a statement ended up being true, while it was false. I don’t know why, usually unexplainable bugs are related to PHP versions, but I don’t know if that’s the case. Anyways by just adding 1 extra line to the code it fixed everything. I’m definitely including this fix in the future updates.

Thank you for the login details and for the prompt ticket.

[Ernest Marcinko]

Hi!

It’s because layer slider loads responsively and the window resize event is not fired afterwards. This is a javascript loophole, but you can try to add the following script to your site header or footer, it should “mimic” the window resize event:

<script>
jQuery(document).ready(function($){
   var scope = $;
   if (typeof aspjQuery != 'undefined')
       scope = aspjQuery;
   setTimeout(function(){
       scope(window).resize();
   }, 3000);
});
</script>

This code will basically wait 3 seconds, then execute a fake window init event, which should restore the search box input width in the layer slider.

[Ernest Marcinko]

Hi!

If you only want to display the custom post types and not other types, then you should disable the “Search in posts” and “Search in pages” option on the general options panel and select the custom post types you want to use on the same panel. (“Search in custom post types” option)

http://i.imgur.com/7zp19Lk.png

You can also find more details about that in the documentation.

• This reply was modified 11 years, 10 months ago by Ernest Marcinko.

[Ernest Marcinko]

Hi!

There is an extensive documentation in both pdf and html formats, you should take a look at it, it may give you a better insight of the plugin. You most likely don’t need change the 90% of the options.

Are you trying to search for posts, pages or custom post types (like products)?

Do you know if the property is stored in a custom field, or somewhere else?

Most of the time different properties are stored as custom fields – maybe that’s what you need.

I’m not going to be able to answer today, as I’m going home, but if you can describe exactly how you imagine the search and what data are you looking for, maybe I will be able to quickly configure it for you tomorrow morning – if you want it of course.

[Ernest Marcinko]

Hi!

It was a yet unknown bug, but on the compatibility settings panel I changed the javascript source to “Minified” from “Minified scoped” and the errors disappeared (both from the layout and the javascript console)

I’m not sure why it’s happening, but I will try to investigate this further and upload a hotfix to codecanyon as soon as I find the problem.

Thank you for the proper description of the problem and for the proper log-in details!

[Ernest Marcinko]

Hi!

I have a feeling that this is a yet unknown bug, if you don’t mind I would like to take a closer look to it. Can you please edit your ticket and add temporary ftp and administrator access? I would like to make some modifications on the search ode, and run a line to line debugging. Unfortunately I cannot reproduce this bug on my test servers, so I don’t know yet why it isn’t working.

[Author]

Posts