Konstantinos Pappas

Whoops, my bad. Caught me time traveling! Thanks for the sharp eyes, @petranca. I’ll fix that in the next version.

Hey @garvitj, just wanted to let you know that I’ve replied to your email about this issue.

Hey @maverick2you,

Are there any errors on the console? (on Google Chrome, CTRL + Shift + J on Windows, or CMD + Option + J on macOS)

Also, if possible, could you please share a link to your website so I can investigate it in more depth? If you don’t want to post it publicly here, feel free to email me at [email protected].

For anyone who might be experiencing similar issues, this can occur for a variety of reasons. Please do not hesitate to contact me on this support forum, via email ([email protected]), and/or by opening an issue on the plugin’s repository.

Hey @giuseppebuccheri,

I’m sorry it took so long to reply, life happened and I got distracted. ??

Yes, the plugin is compatible with the latest version of WordPress (at the time of writing, that is 5.6), I just hadn’t had the time to test it and update the “Tested up to” version.

Thanks for reminding me, I just updated it.

Hey @mstudioil,

you should be able to find a “Lottie” widget, under the “General” widgets category of Elementor Page Builder.

You can also watch this video by WPCrafter, starting at about the 7:00 minute mark, which does a great job at explaining the whole process.

If you have any further questions, just ask! ??

Hey @pixelmorph,

I’m glad you like it!

Unfortunately, that feature hasn’t been implemented yet.

There is an open issue on the plugin’s GitHub repository (#4), so you can follow its progress there.

Thanks for following up, I really appreciate it.

I’m going to mark this as resolved, but feel free to reach out again if you have any other issue and/or question ??

Hey @sellific,

I added to the .htaccess file “Header set Access-Control-Allow-Origin” * “” and the problem with the console is gone.

That’s great!

Unfortunately, AdBlock still blocks the animations

This is unexpected behavior and possibly a bug of the AdBlock extension (perhaps a false positive triggered by a weird filename or something like that). It might be a good idea to bring that to the attention of the AdBlock developers.

Nevertheless, I took a look at your website and the animation doesn’t seem to get blocked. ??

I tested the following extensions on Chrome Version 87.0.4280.88 on macOS:

• “AdBlock — best ad blocker”
• “Adblock Plus – free ad blocker”
• “uBlock Origin”

Please let me know which AdBlock extension is blocking the animation for you.

Access to XMLHttpRequest at ‘https://mydomain.pl/wp-content/uploads/2020/12/lf20_bp1bwvhv-1.json from origin’https://mydomain.pl’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

This is likely an issue with your server configuration.

• Is your website both loading over HTTPS and requesting the JSON data file via HTTPS? If not, take a look at issue #12.
• Is mydomain.pl the same domain in all occurrences of the error message? You have to load the data file (i.e. lf20_bp1bwvhv-1.json) from the same domain as your WordPress installation. If the file lives on a different domain (and possible being served from a different server), you have to set the Access-Control-Allow-Origin header on the server that’s handling the files.

Please let me know if that fixed it for you. ??

If it didn’t, could you please share a link to your website, so I can investigate it in more depth? Feel free to email me at [email protected]

Thanks for following up, I really appreciate it.

I’ve opened an issue on the plugin’s GitHub repository (#21), so you can follow its progress there.

I might have a solution, though I haven’t tested it yet.

Basically, modifying the widgets/lottie-widget.php file, lines 137-140:

'selectors' => array(
  '{{WRAPPER}} .elementor-widget-container'   => 'display: flex; justify-content: {{VALUE}};',
  '{{WRAPPER}} .elementor-widget-container a' => 'display: flex; justify-content: {{VALUE}};'
),

to

'selectors' => array(
  '{{WRAPPER}} .elementor-widget-container'                            => 'text-align: {{VALUE}};',
  '{{WRAPPER}} .elementor-widget-container a'                          => 'text-align: {{VALUE}};',
  '{{WRAPPER}} .elementor-widget-container .animentor-lottie-widget'   => 'display: inline-block;',
  '{{WRAPPER}} .elementor-widget-container a .animentor-lottie-widget' => 'display: inline-block;'
),

Unfortunately, I might not have time to test it and release an update for a while, so if you don’t want to wait you could try to manually modify the file (make sure you keep a copy of the original file, in case it’s not working as expected).

I’ve posted a GitHub gist with the updated file.

If you do test it, let me know if it works (or if it broke it even more ??).

Hey @afplaktape,

Unfortunately, that feature hasn’t been implemented yet.

There is an open issue on the plugin’s GitHub repository (#8), so you can follow its progress there.

Hey @studioeighteenfifty,

I’m sorry you’re experiencing this issue.

If possible, could you please provide a link for an additional page where the “Lottie” widget isn’t absolute positioned?

I don’t think the conflict is intentional, it’s probably caused due to a generic name/id used somewhere in the widgets’ code.

As for the reverse on second click feature, I definitely intend to implement that in a future update. There is an open issue on the plugin’s GitHub repository (#8), so you can follow its progress there.

Though, keep in mind that I generally prioritize fixing bugs (like this one) before implementing additional features.

I haven’t checked it myself yet, but according to the open issue(s) on the plugin’s GitHub repository, it won’t.

Unfortunately, there is a conflict due to Elementor Pro 2.10 using the same name (or id, or something like that) for its “Lottie” widget, so it will override the Animentor one.

Thanks for following up, I really appreciate it ??

I’m sorry for any inconvenience this may have caused you.

I’ll look into it and I’ll let you know once this issue is resolved.