[Ernest Marcinko]

And the background zoom is caused by the parallax scrolling script. Because the upper mentioned error stopped further script execution on the page, the parallax was not working when the plugin was deactivated, so no zooming happened.

[Ernest Marcinko]

Hi!

I’ve just done some testing.

After deactivating the plugin from what I can see there is an error in one of the header scripts, which is most likely causing the whole problem: http://i.imgur.com/aDFlcE4.png

The error states:

[code]Uncaught TypeError: $ is not a function[/code]

Which happens if the jQuery object is not mixed into the “$” object. The reason why it worked with the search active is, that the plugin tries to fix this issue. This is definitely not caused by ajax search pro, as a de-activated plugin code has no effect on the site whatsoever – because simply no code is executed from it’s directory.

After looking more into the error message, the following code is giving the error in the site header:

[html]jQuery(document).ready(function(){
$(".wpurp-user-menus-by").before( "<div class=’sHeadTxtsidebar’>Your saved meal planners</div>" );
$(".user-menus-input-container").before( "<div class=’sHeadTxt’>Your planner name:</div>" );
$(".user-menus-input-container").before( "<div class=’sHeadsubTxtNote’ >(default is date and username, but you can change it)</div>" );
$(".user-menus-selected-recipes").before( "<div class=’sHeadTxt’>Recipes in your grocery list and planner:</div>" );
$(".user-menus-buttons-container").before( "<div class=’sHeadsubTxt’>don’t forget to adjust the number of servings</div>" );
$(".user-menus-ingredients").before( "<div class=’sHeadTxtgrocerylist’ style=’padding-top:40px;’>your grocery list</div>" );
$(".user-menus-buttons-container button").first().text("SAVE YOUR PLANNING");
$(".user-menus-buttons-container button").last().text("PRINT PLANNER");

})[/html]

This code is actually adding elements, menu items into the page. And the problem is that while the function waits for the jQuery document ready event, it then uses the “$” variable as jQuery, which of course is not defined. So I would try to change it to something like:

[html]jQuery(document).ready(function(){
jQuery(".wpurp-user-menus-by").before( "<div class=’sHeadTxtsidebar’>Your saved meal planners</div>" );
jQuery(".user-menus-input-container").before( "<div class=’sHeadTxt’>Your planner name:</div>" );
jQuery(".user-menus-input-container").before( "<div class=’sHeadsubTxtNote’ >(default is date and username, but you can change it)</div>" );
jQuery(".user-menus-selected-recipes").before( "<div class=’sHeadTxt’>Recipes in your grocery list and planner:</div>" );
jQuery(".user-menus-buttons-container").before( "<div class=’sHeadsubTxt’>don’t forget to adjust the number of servings</div>" );
jQuery(".user-menus-ingredients").before( "<div class=’sHeadTxtgrocerylist’ style=’padding-top:40px;’>your grocery list</div>" );
jQuery(".user-menus-buttons-container button").first().text("SAVE YOUR PLANNING");
jQuery(".user-menus-buttons-container button").last().text("PRINT PLANNER");

})[/html]

Or maybe leave it unchanged and rather move it to the footer.php file in your theme, so it won’t block the page rendering.

This is the only error as far as I can see, but there might be more after fixing this one. I suggest fixing the page with the plugin deactivated to make sure it’s working properly.

[Ernest Marcinko]

Hi!

There is a 50 category per taxonomy limit set to display in the plugin code, that’s why you couldn’t see them all. I’ve increased the limit to 600, now you should be able to see and exclude the ones you need 🙂

[Ernest Marcinko]

I think I know what the problem is, it’s actually a wordpress related bug as I found out.

When using the index table engine, the Author of each post is parsed with a single query by using the get_users() wordpress core funtion. Turns out, there is something wrong with it and freezes for over 10 seconds. Someone else had a very similar issue, but I thought it was only his system affected.

There are 2 things I can suggest for now:

1. Use the regular engine until the next update. I’m working on it right now, and I’m definitely going to find another solution to the user related problem, so it’s going to be fixed.

2. Disable displaying the author names on the Layout Options -> Results layout panel and still use the index table enigne.

I’m sorry for this inconvenience, I didn’t know about this wordpress related issue before.

Prioritizing the results by user is not implemented yet, it’s also coming with the next update. The relevance options panel will be extended a bit, where you will be able to set the priority for the author field as well.

[Ernest Marcinko]

Hi!

It was something with the caching. I went to the search caching options, cleared the cache, disabled the image cropping, now I’m getting 0.5 second responses, the performance tracker confirms as well: http://i.imgur.com/v4pxgBf.png

It should respond in 0,5 – 2 seconds on the front-end, based on the amounts of plugins (32) active and the site load time (~9 seconds: http://tools.pingdom.com/fpt/#!/eOLKYn/http://www.kommunen.dk/ ).

If you want to return authors (users) as results, you can enable it on the General Options -> User Search panel: http://i.imgur.com/LWsaxS7.png

The index table only affects post, page and custom post type search. The author data there means that it indexes the author name, description to posts created by him, so looking for the author name should return his posts.

[Ernest Marcinko]

Well, you can change the url where the search redirects, but the results wont transfer over there: http://i.imgur.com/jULnR1N.png

[Ernest Marcinko]

Hi!

On the General Options -> Behavior panel you can enable the Trigger search when changing a facet on settings? option, and changing the options will trigger a search operation.

Also, you can lower the character count to 0, so empty phrases will work as well: http://i.imgur.com/67hJYkG.png

[Ernest Marcinko]

First try other JS Sources, like “Minified”, “Non-minified” – see if anything changes.

If not, then can you re-enable the FTP account? I will take a look and see what I can do.

[Ernest Marcinko]

Sure! I see some other plugin, Product filter (?) is using the same scroll script as the search, it might be causing the conflict I guess.

You can try switching the JS source option back to the default Minified Scoped on the Compatibility Settings submenu. It was designed to handle duplicated cases like this. I’m not sure if it’s going to help, but it’s worth a try: http://i.imgur.com/tIAWn7S.png

[Ernest Marcinko]

Hi!

Thanks for the details, it helped me a lot. You are using a bit older version (4.5.1, current is 4.5.4), which had a known bug in the result count calculation. I’ve fixed it via the FTP details.

You don’t need to update or change anything, version 4.5.4 is not much different from your current version 🙂

[Ernest Marcinko]

Hi!

The plugin is for search purposes only, it cannot import files to your database.

There are however a few plugins that might help you importing your excel data to a custom post type:

Import CSV with Ultimate CSV Importer
WP CSV plugin

[Ernest Marcinko]

Hi!

Thank you for your kind words 🙂

Yes, it’s normal. The “etc” is for the author and date content. If empty, it’s only for placeholding.

[Ernest Marcinko]

Hi!

Yes, if the custom field is not set, the post is filtered out – that explains the situation 🙂

I’m guessing that the NoUI slider script is disabled on the Compatibility Settings submenu: http://i.imgur.com/Y4r9oVu.png

If you turn it back on, it will start working again.

[Ernest Marcinko]

No problem, I’m happy to help.

Your search instance configuration was incorrect. On the search instance options General Options -> Sources panel I’ve selected the Index table engine, since you have the index table generated now. The products were not selected either, so I’ve selected it as well: http://i.imgur.com/PmnbwxN.png

It should return products now 🙂

[Ernest Marcinko]

Hi!

It worked for me, everything is indexed now.

I’ve increased the posts count to 100. Your server is fast enough to handle 100 posts per indexing.

You don’t need to re-create it now, unless you change the configuration.

[Author]

Posts