[Ernest Marcinko]

Hi!

Yes, I also modified one more file: ajax-search-pro/backend/index_table.php

That’s the only 3 files I have changed.

[Ernest Marcinko]

I think I might have a solution without touching the code. Normally it would require adding some HTML elements, but I’ve tried the following CSS on the demo and it worked for me.

[code]
.asp_option_cat {
width: 200px;
display: inline-block;
}

.categoryfilter {
width: 420px;
}
[/code]

That will make each option 200px wide displayed as inline-block and the container 420 pixels. That means it’s printed to 2 columns like so: http://i.imgur.com/UP0PMHA.png

[Ernest Marcinko]

No problem at all, don’t worry 🙂

We all make mistakes. A few days ago I was fixing something for 5 hours, when I realized one of the files in the editor (had like 25 opened) was from a different folder. I know the feeling 🙂

[Ernest Marcinko]

I do not understand the problem at all right now.

You have created 3 different search instances, but using only one of the shortcodes, with the ID of 6. The reason why the screenshot from the front-end is not looking like the one on the back-end is because those are two different search instances. One is number 6, the other is the 1.

If you correct the shortcode, it will display the correct one. Right now the 6. is displayed 3 times because the shortcode of that instance is used.

The reason why there were no changes on the front-end, is because you were styling instance number 1, and it’s not used on the front-end, only number 6. Therefore it’s not going to change ever, unless you correct the shortcode.

[Ernest Marcinko]

I just logged in and checked the back-end settings.

I see 3 instances on the front-end on the linked page. All 3 of them are with the search id “6”, which is the “Genre Search” you have created.

Then I went to check the “Genre Search” on the back-end and it looks exactly like on the front-end. Then I opened the settings on the search with the ID “1”, “Portfolio Search” and it is indeed looking like the first screenshot, but this search is not used on the front-end at all. All 3 instances you have use the shortcode with the ID 6.

Can you please check the shortcode on the second screenshot, it looks like it’s with the ID 6 and not 1.

[Ernest Marcinko]

I’m afraid there is no other way. The plugin executes extremely fast, way below 0.1 seconds, so it’s optimized to the maximum already. And the P3 profiler is not going to help in this case, because ajax requests usually act very differently from a page loading process.

It’s not possible to force other plugins to not load programatically unfortunately, so the search handler must wait for it’s turn. I’ve written an article about WP performance, you can read it if you want to, but the cause in your case is the very high number of plugins.

You can turn on caching on the caching options panel, but it’s not going to help much, because the plugin gets the results almost immediately. The cached handler is still going to get held up by the WP loading process.

Unfortunately I’m not doing freelance or contract jobs right now.

[Ernest Marcinko]

Did you install the plugin via the plugin manager?

This does not sound like it’s related to the ajax search pro. The menu links are built by wordpress, and it hasn’t changed since the initial release.

If you can provide temporary back-end and FTP access, I can take a look at the problem directly.

[Ernest Marcinko]

I have found the problem. There was an error in the grafity forms woocommerce plugin:

Fatal error: Call to undefined function wc_is_21x() in /public_html/wp-content/plugins/woocommerce-gravityforms-product-addons/gravityforms-product-addons.php on line 113

I’ve made a correction to that plugin code. I’ve added this line:

[code]if ( !function_exists( "wc_is_21x" ) ) return;[/code]

to the wp-content/plugins/woocommerce-gravityforms-product-addons/gravityforms-product-addons.php line 113.

For even better performance, consider lowering the active plugins number below 15. The ajax search plugin finishes within 0.1 seconds based on the performance tracker results, the rest is system and other plugin initialization and execution time.

[Ernest Marcinko]

Hi!

I’ve tried to log in with the details, but it does not let me, can you please check it?

Altough I think I might know the solution. On the Ajax Search Pro Compatibility Settings submenu turn off the Load the polaroid gallery JS? option, then refresh the front-end a few times. I see that the login form might use a similar script and it’s not neccessary to load twice.

Let me know if it helps.

[Ernest Marcinko]

Hi!

Thanks for the details. I can only access one empty folder. Can you please check the account permissions?

[Ernest Marcinko]

Thanks for the information, it’s coming in the upcoming version in 3 days. First I have to test potential security issues with this input method.

[Ernest Marcinko]

I was able to log in now, but only using a proxy. Something is still blocking my address range.

Please update the first post with FTP details as well (or you can upload a .txt file, both methods safe)

There is no error message nor any other information in the response header, the only thing I can do is debug parts of the site and plugin code.

[Ernest Marcinko]

I cannot access your site, nor the admin. Looks like there is a firewall or something blocking the access.

Please also update FTP details, if there is an error 500 there is almost no chance to debug it through the admin panel.

[Ernest Marcinko]

Also, don’t forget to turn on debug mode in the wp-config.php file. If there is a fatal error or a warning causing it, then it should print it to the response body.

[Ernest Marcinko]

Hi!

It looks more like to me that the file is missing, or blocked by .htaccess or on server level.

When I clicked on the link, it gives this error:

[code]Access to this resource on the server is denied![/code]

That means the file most likely exists, but the access is denied. This is 99% related to a .htaccess rule, as the error page is printed with a nice template. One other thing you can check is the file persmissions. It should be “644”, but you can try “755” or “775” to check if it’s permission related problem. 644 however should work without problems.

The file is accessible correctly if it gives “-1” as the output when you click on the link. Just like the one on the demo page: http://wp-dreams.com/demo/wp-ajax-search-pro/wp-content/plugins/ajax-search-pro/ajax_search.php

[Author]

Posts