adalov

Resolved, the solution is:
Update language files (WordPress – Dashboard – Updates – Update translations)

Hi Dennis,

danke vielmals! Used the custom filter, that’s great. 5* for Germanized support + service.
Have a good day!

Best
e

Hi,

thank you very much for your reply!

Yes, of course, Rich Pins options have always been enabled in the Pinterest for WooCommerce plugin settings.

Merchant status was just approved. Some (very few) products now get shown with rich data (price, availability). However, when creating a new board in Pinterest (saved pins) as suggested by you, rich data does still not appear on pins in general, example https://tinyurl.com/gj-earrings.

On the other hand, when creating a new product group directly from the catalogue at pinterest.com/business/catalogs, rich data is included for recently added products, but still not for products (in the same product group created at the same time, post VMP) that have already been in the catalogue before getting VMP status. We have now made some changes in WooCommerce products so that the data source hopefully gets updated with the next import and maybe that makes a difference, I’ll check again tomorrow.

What’s super interesting anyway is that Pinterest shows some products from the catalogue with rich data, but when the same product gets added manually to a board (post VMP status), rich data is not shown, examples: https://tinyurl.com/gj-rich-yes and https://tinyurl.com/gj-rich-not. I believe that this is the case in general, but Pinterest does unfortunately not communicate this fact which is quite confusing (or they changed their rich pins policy at some point, idk).

Maybe you can give some insights regarding the point mentioned above about some catalogue products showing on Pinterest with rich data, some without (same catalog, same product group, same date added, same data source, data source includes rich data for ALL products). If still necessary, I’ll send the system report later on.

Thank you!

Thx Alaa!

@logisticscm?@smochen?@robotheater?Quick update: looks like a solution for the video bug is in sight. Not yet in 3.12 (just released) but in upcoming 3.13. Looking forward :D.

Hi @robotheater, sorry to hear about that. Which browser(s) did you test?

@logisticscm @smochen @robotheater you are welcome!

By the way, according to Elementor, the new update 3.11.4 that was just released is supposed to fix the issue (in some browsers?). You could try and it would be interesting to hear about your experiences in the browsers you are testing (especially Safari, Firefox, Chrome). I still see the issue at least in Safari (14) after updating to 3.11.4. If it doesn’t work for you either, you can always go back to 3.10.2 again …

@robotheater for backups, you could install UpdraftPlus https://de.www.ads-software.com/plugins/updraftplus/, if you do not already have it. This gives you the possibility to reinstall backups with just a few clicks directly in the WordPress backend. Plus you can also reinstall backed-up plugins only. So if, in your case, reverting to Elementor 3.10.2 would go wrong, you could reinstall the previous plugin version via Elementor version control OR via UpdraftPlus. The procedure in a few steps:

1. Install UpDraftPlus plugin
2. Run a backup with UpDraftPlus. Check if backup success message / log is correct: “The backup apparently succeeded and is now complete” ??
3. Revert to Elementor 3.10.2 as described in previous message. Check if videos show correctly. IF IT GOES WRONG:
4. Reinstall plugins backup via UpdraftPlus
   

And no, Elementor has not provided a solution for this bug yet although several customers/users have reported it over the last 2 weeks. In the meantime they went from delaying answers / saying that they do not see an issue at all to stating that the issue “is not consistently reproduced”. So, it looks as if this might take a looong time to get resolved. As Elementor has lots of (YouTube) videos on elementor.com (academy) and they still use 3.10, my last hope is that in the moment they update their own website to 3.11, they might get active a bit faster ;).

Hello Elementor,

this topic is still not resolved! Please get back with an answer soon.

Best regards

@lukiano880 welcome, as written above, rolling back to 3.10.2 solves the issue temporarily while waiting for a bug fix by the Elementor dev team. Support seems to have taken a day off today ??

Hope that rollback to 3.10.2 worked for you in Firefox as well. Good luck!

Hi robotheater,

I am another Elementor user/customer who has the same problem with the Elementor free version and I also reported it. As Elementor did not provide a solution yet, I would like to assist you in rendering your videos correctly in the meantime until Elementor fixes the bug.

You can revert/ roll back to a former version of Elementor, in this case to 3.10.2, and the videos will be shown as before. Prior to reverting, please make a backup. Then you can re-install the former Elementor version from the backend at Elementor / Tools (Werkzeuge) / Version Control / Rollback Version (Wiederherstellungsversion) 3.10.2. Voilà! Then everything should look like before (if not, empty cache and refresh browser after reverting).

Hope this helps!

Hi,

please open the link in Safari to view the bug: https://tinyurl.com/ycj9xn4u

Also, and I am sorry that I have to say this again: It is rather annoying that the Elementor team does not even take a look at reported bugs if users / customers do not provide links to websites right away. In this case, the video widget error can easily be reproduced on any site and I would expect Elementor support and dev teams to check that proactively and not slow down support and final solutions by always just asking for a link instead of working on the issue.

By the way, please understand that we also have customers and can not just leave the bugs on our client’s websites visible for anyone (and Elementor) but we revert to a bug-free version and then what is the use of a link for the Elementor team?

As much as I would like you to provide a quick fix of the bug in version 3.11.1 (persisting through 3.11.2), I would also like Elementor to overthink their support routines.

Please send me an answer to both issues, the bug AND the support problem. Thank you!

Thx!

Hi Marko,

thanks! The manual delete did not help, so we disabled DB cache as you advised.

Another quick and general question in this respect: Given the small / neglectable positive impact of disk caching and the advantages of Redis / Memcached, would you disrecommend using shared hosting that does not offer those in general? Maybe a dumb question, but some big(!) (German) hosting providers currently do not offer Redis / Memcached in their WordPress shared hosting plans at all and maybe that might be a reason to stay away from those “service providers” in the future? Just curious what is your personal take on that.

Found the solution, issue is resolved!