dalibor

Right. Thanks a lot for the upcoming fix. It’s only at testing staging site, anyway. There are a couple of more plugins that need fix too, so I’ll wait a bit till everything else gets fixed.

Actually I’ve setup 2 different stagins sites. It’s just the same at both of them.

Builders: both Elementor w. Halo theme and Bold Builder w. Primavera theme.

Lots of plugins, Wordfence is probably the most important of them.

Nevertheless, I don’t think it’s worth to get any deeper into this error. I think I’ll just disable this plugin. Thank you for your time.

What do you mean by config?

WPS hide login has only 2 options and it’s working just fine in the production. For testing purposes I setup a staging site at Kinsta with intention to test the compatibility with PHP 8.3. wp-debug is on, and the front page displays that error in the header.

Oh well, that’s sad. The issue resolves a mystery and resolved. But as I can see the people are also having problems with other page builders. I hope you resolve it some day. If it will ever suddenly start to work I’ll report here.

Regards,

Hi @jmatiasmastro. Told you the error codes had nothing to do with the plugin. I’ve already tried basically everything – even downgrading to 7.4, nothing seems to work.

Please note Kinsta no longer supports PHP 7.4. I’ve disabled the tabs option on my production site until it starts to work again.

I’m sorry it longer works, it was really great with theme’s shortcodes. Without it, the tab option is just “meh”.

Regards,
Dalibor

Since, we keep mismatching and it keeps taking time, I’m attaching the log through PasteBin as well, for your convenience: https://pastebin.com/qmJv3qt0

Hopefully this should do now. ??

Regards,
Dalibor

LOL, bad luck, I was just reconfiguring my entire network here. It’s been 5 weeks after my last reaply.

Anyway, should be okay now. I’ve tested it independently: https://microbin.echobit.hr/pasta/fish-falcon-deer

Regards,
Dalibor

I talked to Kinsta guys, and the logs I posted before were correct. It was my fault to put the files expiration of 1 week only since I thought we’d resolve by then.

But no worries, you may find the log here: https://microbin.echobit.hr/pasta/fish-falcon-deer.

Example page at the staging site (“Brand” tab): https://staging-disprom-tstperfbrand.kinsta.cloud/product/sens_us/zero-yellow-shampoo/

Thanks ??

@jmatiasmastro I would gladly shared the error.log with you. I’m just not sure what to send you.

I’ve enabled the debug in the staging environment and checked out the logs, however there is not a single records that points out to the Perfect Brands is producing any errors. If you like you may check them here: https://microbin.echobit.hr/pasta/raven-whale

Thanks in advance.

Wonderful. Thank you for your great support. Appreciate it. ??

• This reply was modified 2 years, 10 months ago by dalibor. Reason: Relevant tag added

@rogierlankhorst thank you. I will get in touch with them and ask to make the contact. Your plugin is just great and I think we should resolve this.

Thanks @rogierlankhorst, I’m afraid we’ll need to proceed with other solution. It’s a premium theme not available as free download. Demo here: https://primavera.bold-themes.com/.

Any other way to trap the error, maybe through the DevTools? To be honest, I looked there but couldn’t find anything meaningful to me.

@rogierlankhorst looks like the problem is with my Primavera theme (please see the above post). Anything I could do to further pinpoint where the problem lies?

So I got to the bottom of this: I removed all the plugins except the Woocommerce – it didn’t help. Then I set it back to the TwentyTwentyTwo theme and it’s now working. ??

So apparently – there is some compatibility problem with the Primavera theme I’m using and something new introduced with the latest version of Complianz.

I’d appreciate any suggestion in further pinpointing the problem and get some fix, if possible.

Thanks in advance.

• This reply was modified 2 years, 10 months ago by dalibor. Reason: minor changes

Hi Rogier,

In the 6.1.5 YouTube was never blocked.

The problems have started with 6.1.6. Everything is shiny with 6.1.5, as I’m still using this version on the production site, as opposed to the staging site where I’m sitting waiting on a fix and running 6.1.6.1.

Testing example: https://staging-disprom.kinsta.cloud/product/hsa/addmino-addplex-18x/