[Ernest Marcinko]

Thanks!

I see the error message when I enable the debug log, unfortunately it is not seem to be related to Ajax Search Pro.

I confirmed by turning off the plugin, the issue is still there on my end.

The error points to the theme directory, I copied the full message to the end of this reply. I tried multiple times to make sure it’s not something related, but the error message clearly points to an undefined function in one of the theme files, in /home/customer/www/dogthority.com/public_html/wp-content/themes/bb-theme-child/functions.php on line 531
It seems like a minor issue, call to an undefined function, a simple function check could resolve it, but I would ask the theme developer, he may know what that function is used for and how to avoid the issue.

b>Fatal error</b>:  Uncaught Error: Call to undefined function bp_get_messages_slug() in /home/customer/www/dogthority.com/public_html/wp-content/themes/bb-theme-child/functions.php:531
Stack trace:
#0 /home/customer/www/dogthority.com/public_html/wp-includes/shortcodes.php(433): bpfr_message_shortcode('', '', 'ksam')
#1 [internal function]: do_shortcode_tag(Array)
#2 /home/customer/www/dogthority.com/public_html/wp-includes/shortcodes.php(273): preg_replace_callback('/\\[(\\[?)(ksam)(...', 'do_shortcode_ta...', '[ksam]')
#3 /home/customer/www/dogthority.com/public_html/wp-content/plugins/bb-plugin/modules/button/includes/frontend.php(14): do_shortcode('[ksam]')
#4 /home/customer/www/dogthority.com/public_html/wp-content/plugins/bb-plugin/includes/module.php(10): include('/home/customer/...')
#5 /home/customer/www/dogthority.com/public_html/wp-content/plugins/bb-plugin/classes/class-fl-builder.php(2904): include('/home/customer/...')
#6 /home/customer/www/dogthority.com/public_html/wp-content/plugins/bb-plugin/classes/class-fl-b in <b>/home/customer/www/dogthority.com/public_html/wp-content/themes/bb-theme-child/functions.php</b> on line <b>531</b><br />

[Ernest Marcinko]

Hi Stephan,

Thank you very much for the details, it helped a lot!

I found a culprit, it was a style loader issue, it changed something on the output and was not longer working.
Luckily it was a very easy fix, I just added an exception in the plugin code to exclude all woocommerce ajax related actions, and it fixed the issue.

I will include this fix in the upcoming release as well, so you don’t have to worry about it anymore. It should be okay now.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

The alternative image source 2 is the problem there, it’s set to a page screenshot, which is always going to be there, and because the image is not empty, it will never fetch the PDF images.

Use this setup:
– Primary: Featured
– Alt 1: Post Content
– Alt 2: Default
– Alt 3: Disabled
– Alt 4: Disabled

That should do the trick.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Sure!

Can you please check if this option is also enabled: https://i.imgur.com/HkzCrGG.png
It should be ON by default, but just to make sure. Another common issue is that the imagick policy does not have the PDF allowed.

[Ernest Marcinko]

You can control what should happen when the user hits enter or clicks the magnifier icon – you can even turn off the redirection if you want to.
I’m not exactly sure how you want it to setup, but this should definitely help a bit.

[Ernest Marcinko]

That’s because the page is not stored in database, nor in repeter/flex fields, it’s generated via a template. Unfortuantely that can’t be indexed (yet).
The rest using the repeaters should be okay though.

[Ernest Marcinko]

Hi,

Thanks for the details!

Can you please add temporary FTP access? The file manager does not have privileges to access the files, it gives me an error message: https://i.imgur.com/xfPqaVG.png

It’s also much safer via FTP, as any mistakes can be reverted.

[Ernest Marcinko]

I have already re-indexed everything, so all sub fields for every single page from “home_page_builder” should be there.
I’m seeing 30 000 keywords, previously it was only 9000, so it is very likely indexed now.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Basically if the CSS is going to be printed inline (which will have higher specificity), then this will work:

div.asp_sb.searchsettings fieldset input[type='text'] {
  border: 1px solid red !important;
}

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts