wpkina
Forum Replies Created
-
Hi @gloryous 👋
Thank you for reporting this, and I’m really sorry to hear that the update caused issues on your client’s site.
Our engineering team has recently released a new version (v2.8.0) which includes several fixes. Could you please try updating to this latest version and see if the issue persists?
If you’re still experiencing the error after updating, feel free to reach back out — we’ll be more than happy to assist you further.
Warm regards,
Kina
FAB Support TeamHi @tylercg 👋
Thanks again for your patience!
I’ve checked with our engineering team, and it looks like Beaver Builder isn’t officially supported yet at the moment. The good news is — they’ve confirmed this will be addressed in the next update! 🎉
We truly appreciate your understanding, and we’ll make sure to let you know once the update is available.
Warm regards,
Kina
FAB Support TeamHi @tylercg 👋
Thank you for reporting this issue, and I’m really sorry for the inconvenience it’s caused — especially when using Beaver Builder.
I’ve forwarded this to our engineering team for further investigation. We’ll keep you posted with any updates as soon as we have them.
Thanks again for your patience and support!
Warm regards,
Kina
FAB Support TeamHi @shelfgamer,
Thanks for your feature request! 🙌
We’re happy to let you know that FAB version 2.2.0 now supports this feature. You can exclude floating buttons from archive pages using Conditional Tags.
Here’s how to set it up:
- Go to Admin > FAB > All FAB > Edit
- Navigate to Metabox Location
- Select Location Rule Type as
Conditional Tags > Conditions - Set Location Rule Operator to
is not equal to - Choose Location Rule Value as
is Archive - Set Location Rule Logic to
OR - Click Save
- Done! The button will now be excluded from archive pages.
This should solve your issue! Let us know if you have any further questions. We’re always happy to help. 🚀
Best,
Kina
Floating Awesome Button Support TeamHi @shelfgamer,
Thank you for your feature request! That’s a great idea, and we really appreciate your feedback.
We have forwarded your request to our engineering team. We will do our best to add this feature in a future update.
Stay tuned for updates, and let us know if you have any other suggestions. Thanks for your support!
Best,
Kina
Floating Awesome Button Support TeamHi @shelfgamer,
Thank you so much for your thoughtful review! We’re happy to hear that the plugin works as expected and meets your needs.
We truly appreciate you reporting the bug and giving us the chance to fix it quickly. Your support means a lot to us, and we’re grateful for your decision to upgrade to the premium version!
If you ever have any feedback or need assistance, feel free to reach out. Thanks again for your trust and support! 😊
Best,
Kina
Floating Awesome Button Support TeamHi @shelfgamer,
We’re really sorry that this issue has been ongoing for several days. We truly appreciate your patience.
We’ve sent you an email to assist with this matter. When you have a moment, please check your inbox and feel free to reply.
If you haven’t received our email, please let us know, or you can also reach out to us directly at artistudio2020@gmail.com.
We appreciate your understanding and look forward to hearing from you.
Best,
Kina
Floating Awesome Button Support TeamHi @direktorob,
We sincerely apologize for the inconvenience, and we understand that the issue is still unresolved. We want to assist you as quickly as possible.
To make the troubleshooting process more efficient, would you be open to continuing this discussion via email? If so, please share your email address with us. Alternatively, you can reach out to us directly at artistudio2020@gmail.com.
We look forward to your response and are ready to help resolve this issue.
Best,
Kina
Floating Awesome Button Support TeamHi @shelfgamer,
Thank you for your patience! Based on your report, it looks like the issue might be caused by the rule not being saved correctly. Here’s a workaround you can try:
- Remove all conditions from Location Rules.
- Click Save and then refresh the page.
- Add a new rule: “Post Type is equal to [custom post type]”.
- Add an additional AND condition to ensure the rule is properly saved.
- Click Save again and check if the issue persists.
We’re also working on an update to ensure that the conditions have a default value to prevent this issue in the future. Let us know if this solution helps or if you need further assistance!
Best,
Kina
Floating Awesome Button Support Team
Hi @shelfgamer,
Sorry for the late response, and thank you for your patience! 😊
We have noted the issue regarding the button displaying on all pages despite the filtering settings, especially when using an Anchor Link.We wanted to check—are you still experiencing this issue? Let us know, and we’d be happy to assist further.
Looking forward to your response.Hi @shelfgamer,
Sorry for the late response, and thank you for your patience! 😊We appreciate your time and effort in bringing this to our attention. Our team has noted the issue, and we will address it in a future update.
If you have any further questions or encounter any other issues, please don’t hesitate to reach out. We’re always working to improve the user experience.
Thanks for your support! 🚀
Hi @dancolmorn,
Sorry for the late response, and thank you for your patience! 😊
The issue might have been caused by our recent update release. We’ve just released version 1.10.1, which includes several fixes and improvements. Could you please update to the latest version and check if the issue is resolved?
Let us know if you need any further assistance. Thanks for your support! 🚀
Hi @direktorobi,
Sorry for the late response, and thank you for your patience! 😊
The issue might have been caused by our recent update release. We’ve just released version 1.10.1, which includes several fixes and improvements. Could you please update to the latest version and check if the issue is resolved?
Let us know if you need any further assistance. Thanks for your support! 🚀