ragulka

This issue should be fixed in the 1.1 release.

gabylinares – It’s hard to tell what’s going on without being able to see the settings in admin area. Can you perhaps post a of your widget settings in admin?

I am facing this issue when using WooCommerce Dynamic Pricing. It stores price groups as serialized data on post meta. But I would face it whenever I would store any serialized data in post meta.

It doesn’t make sense to exclusively maybe_unserialize a few fields based on their names (like you are doing with _file_paths) because you never know what kind of information users might store in custom meta fields.

You should simply maybe_unserialize all post meta fields. Keep in mind that get_post_meta does NOT unserialize any serialized values.

I’m having this issue with 3.0 and 3.0.1

Hey Gordon. Are you using a picture inside the widget title? Can you please copy your widget settings here, so that I can test on my system?

Yep, it is me.

Hi, just tested with 3.6 and 3.7 – it works for me. Please be more precise – what do you mean by “not working”?

Hi, can you please provide information about your setup? I cannot reproduce the issue on my system.

Sorry, I cannot see the link, so I can’t really help.

Hi, I would love to add WPML support, but I am not terribly familiar with the process. I tried to find information about how to do it, but did not find anything useful yet. Do You know how to do it or point me to a resource?

Hello, I am sorry for replying so late. I did not receive automatic notifications of new posts in this forum.

The plugin only works with widgets that use the widget_title filter as stated in the FAQ: https://www.ads-software.com/plugins/widget-title-links/faq/

Unfortunately You haven’t specified what widget you are using it with so I can’t really help any further at the moment.

I completely agree about taxonomy_id and term_id confusion in the database.

Also, I think a get_term_by_meta_value function would help ??

That’s not what I want to do.
I want to access the site at https://blog2.domain2.com, not https://domain2.com

Sure ??

Yep, some kind of mapping array would work great. And I just realized it would have to be before we extract the susbtring from the locale, otherwise, it could cause issues.