zenjukai

Hello @dake,

This is good to know, but this should NOT be a default. This should be an option to select, not forcing people to scan through all the conditions.

Let’s talk about privacy as an example. Should folks have to go in and turn off all the marketing, sales, tracking features a browser or piece of software uses because they don’t want to be tracked? No they shouldn’t have to. So the same applies to you folks.

Promote your products, but it should be an option people CHOOSE to check and not checked by default. This is my personal opinion, but I feel the majority of folks out there feel the same way.

Perfect, thank you for the update.

Thank you @bsfherman for the help! =)

Cheers

Hey @bsfherman,

Thanks for the quick reply and update — will stay tuned for the update when it is ready. =)

Cheers

Hey folks,

Sorry to reopen this ticket, but again this error is back.

I just did the update for the Pro plugin and the Astra theme — I now have the same

Uncaught TypeError: Cannot read property '0' of undefined
    at n (frontend.min.js?ver=3.4.1:1)
    at frontend.min.js?ver=3.4.1:1
n @ frontend.min.js?ver=3.4.1:1
(anonymous) @ frontend.min.js?ver=3.4.1:1
load (async)
(anonymous) @ frontend.min.js?ver=3.4.1:1
(anonymous) @ frontend.min.js?ver=3.4.1:1

I am running on a local setup:

Astra Theme: v3.4.1
Astra Pro Plugin: v3.4.1

Cheers

Hey Stefan,

Actually I already did the other day and you folks were super fast to respond. Plus, you are already on the ball and making the those changes. So again, great job! =)

This was the featured request: https://github.com/zionbuilder/zionbuilder/issues/432

Cheers

Sounds good. Thank you.

Cheers

Hey Tom,

I appreciate the reply and I totally undertsand your point.

I also appreciate all thw hard work you have done … I am just finiding it interesting and a bit of an annoyance when I can replicate the same problwm with the CSS not applying four different times now.

All I am doing is creating a custom block and then injecting it via a hook. I am only using generateblocks …

Anyways, just my experince.

Hey there,

Yes I updated this morning to 3.0.3 and yes, it seems to have fixed this issue.

Thanks for the work folks.

Cheers

Hey folks,

Still getting the exact same errors as I did when I first posted this issue.

I know they are on top of it, but it does seem like they are having some issue with it.

Hopefully they can get it resolved soon.

Cheers

• This reply was modified 4 years ago by zenjukai.

Awesome, great work, thanks for the quick resolve. =)

Cheers

Perfect, thank you Suman for the quick reply and solution. =)

Cheers

I have the same issue

Fatal error: Access level to OneElements\Includes\Widgets\Testimonials\Widget_OneElements_Testimonials::print_content() must be protected (as in class Elementor\Widget_Base) or weaker in

I tried that resolve above but did not make a difference. Still getting the error.

Thoughts?

Thank you Andrea, excellent work … all is working now. =)

Plus I updated my review and message.

Cheers

• This reply was modified 4 years, 11 months ago by zenjukai.

Thanks for the clarification Predrag, I appreciate it. Do love the plugin and will continue to use it for sure. =)

Cheers