Vytis

Hi @ofmarconi, @kpbryce132, @silasveta2012,

Thank you for reporting this issue. We made a release today that should address it.

Let us know if you are still facing any issues.

Hi @amselrehhase,

Thank you for using Redirection for Contact Form 7 plugin.

There is an integrated toggle to the action that should trigger opening in a new tab: https://vertis.d.pr/i/D4e7jH

Have you tested this option? Doesn’t it work as expected? Thanks!

Hi @wizfinger,

Thank you for using Raft products and leaving your review. There are some notifications in the theme, however, if you dismiss them they shouldn’t be bothering you again. Apologies if it caused you a bad experience.

@rothschild86,

We did not convert any chart that was free to a paid one. We only made restriction that charts from PRO addon cannot be used with a free version of a plugin. If you have a column chart created from the past it means you used PRO version of the plugin in some way and that is the reason you’re currently seeing the popup.

Hi @rothschild86,

Thank you for using Visualizer.

Bar chart is not a paid feature, it is still free like it was. Maybe you have a column chart created (which is a paid feature) and confusing it with a bar chart? What was introduced with the recent versions of Visualizer is that if there is a PRO chart created (like column chart) we’re checking for the license and that’s why there is a popup about adding the license key appearing.

Let us know if you’re getting this with a bar and not a column chart (if you can share a screenshot that would be very helpful). Thanks!

Hi @lucgiu,

Thank you for sharing your experience with Feedzy.

Can you please share a screenshot of the advertisements that you’re referring to?

Hi @aarucanada,

Thank you for using Feedzy plugin and sharing your experience with us.
I’m sorry to hear that plugin hasn’t worked as expected and you face the issue described.

I tried to look for a thread created by you to understand the problem better if there are more details shared but I can’t find any, can you please share it with me?

If you’re a pro user and you have submitted a ticket to our support team, can you please reply to it so I can check what investigation was done by our team?
Looking forward to assisting you with this issue!

Thank you @senjoralfonso, we will review the provided information with our team.

Hi @dschwartzer,

Thank you for sharing your use case and I since we wanted to investigate and work on this request more I was trying to dig into the issue a bit more.

The part that is not very clear to me is how you’re using the email updates when there is new content in Feedzy? I’m asking because Feedzy does not have such a feature and based on the description you’re not using Feedzy import as posts, you’re using shortcode/block usage so with this method you add content to existing post/page and when cache period expires the content is refreshed but if my understanding is correct and you’re using some 3rd party service to send an email update when content is created/updated when Feedzy block fetches new data it can’t really trigger such an update as content itself inside the post isn’t updated, so even when it’s fetched first time it shouldn’t get triggered unless you manually Save the post/page (or have some automatic method to trigger that Save of the post).

Let me know if I understand your use case correctly or I’m missing the point.

Thank you!

Hi @valkirias,

I wanted to follow-up here and ask if you were able to solve the issue?
Also, a small update about the reply above that the custom code is no longer needed as with the recent update of the plugin we made an option to add your own API keys by default.

Since you’re facing 417 error from my experience, this could be a result of incorrectly configured account settings in X network, please take additional looks at the steps provided here:
https://docs.revive.social/article/1908-how-to-solve-453-twitter-error-in-rop

And especially on Step 8 which sets the App permissions.

Let us know if you’re still experiencing this issue. Thanks!

Happy to hear it @josegalan! Thank you for updating the review and enjoy using ROP! ??

Hi @josegalan,

Thank you for using Revive Old Posts plugin.

Due to the X (ex Twitter) changes in network limits, we cannot guarantee stable sharing using the default API keys that are setup with the App. We recommend using your own API keys.

Please make sure that you’re using the latest version of ROP pluggin and follow this guide to set up your own API keys for usage with X network:
https://docs.revive.social/article/1908-how-to-solve-453-twitter-error-in-rop

We made the latest update of the plugin to bring this option available by default (using your own API keys) to prevent sharing issue with X network.

I hope this helps!

Hi @volaticus,

We released a fix for the reported issue today, please update the plugin and you shouldn’t see the warning anymore.

Thank you for reporting this once again and have a nice day!

Hi @ambersquires,

Thank you for using Neve theme. I checked your website and I don’t see green color in the header:
https://vertis.d.pr/i/HEAqWJ

Can you share a screenshot of the section you’re referring to? Thanks!

Hi @hai3009,

We checked again and it seems to be working.

Example shortcode:
[feedzy-rss feeds="https://domain.com/feed?cat=2 "summary="yes" summarylength="5"]

Please make sure to use correct ” and not ″ next to each parameter.

I hope it works!

• This reply was modified 1 year, 6 months ago by Vytis.