mabdelbari
Forum Replies Created
-
Thank you for sharing your valuable feedback and highlighting this specific design scenario.
Utilizing the “equal height” option is an effective solution for achieving the desired layout. We fully recognize the importance of advanced flex properties such as flex-grow, flex-shrink, and flex-basis, and our team already has their implementation on our development roadmap.
Your input is greatly valued and helps us make the plugin better for everyone!.
Thank you for sharing your insights and for investigating this in detail.
This issue is related to compatibility between your theme and Gutenberg. I recommend reaching out to the theme developer, who may have more tailored solutions or advice.Best regards
Hello,
Thanks for the screenshots—they’re very helpful.
The duplication option for Accordion items is a standard feature in the Gutenberg editor. If it’s missing, there’s a possibility it could be related to your custom theme.
Could you please try temporarily switching to a default WordPress theme (like Twenty Twenty-Five) and let us know if the duplication option reappears? This will help us test and troubleshoot the issue together.
We appreciate your cooperation in testing this.
Hello, We apologize for any inconvenience you’ve experienced.
Kindly check out this video demonstrating how to add/duplicate accordion items.
If the issue persists, could you please provide the name of your FSE theme and a complete list of all active plugins? Any additional details on the steps to reproduce the issue would be greatly appreciated.
Thank you for your cooperation. Your patience is truly appreciated
Thank you for your feedback and kind words!
We appreciate your perspective as a developer working on custom themes, and your suggestion about brand icon selection is very helpful. We’re glad you enjoy the plugin’s lightweight approach and will keep your idea in mind for future updates.
We’d also be truly grateful if you could please do us a BIG favor by rating Premium Blocks for Gutenberg, as your feedback truly makes a difference.
If you have any further questions, feel free to reach out!Thanks for your feedback and sharing your workaround.
Currently, filtering or fully replacing standard icons (Dashicons / Fontawesome Icons) with custom ones isn’t available. You can disable FontAwesome icons from the dashboard settings. For custom icons, the current workaround is to manually upload SVGs or images in each Icon Block.
We appreciate your suggestion and will brainstorm internally about improving custom icon flexibility in future updates.
Let us know if you have any other questions or ideas!
Hello,
Thank you for your detailed feedback and patience.
After Investigation, The issue persists in Firefox even with Premium Blocks deactivated, but not in Chrome when it’s active. This points to the core WordPress issue.Could you confirm if you’re using Firefox or a different browser?
Our team is investigating this further and we’ll keep you updated.Best regards
Hello and welcome back!
First of all, we apologize for the inconvenience you’re experiencing. Thank you for your detailed report and for keeping everything updated—it’s greatly appreciated.
To help us investigate this further, could you please provide the exact steps you follow to encounter the issue? Specifically which specific FSE theme, blocks, or settings are you using when the issue occurs?
Thank you again for your cooperation. We’re committed to resolving this as quickly as possible, and your input is invaluable.
Best regards
Forum: Developing with WordPress
In reply to: Isotope itemSelector issue with API Version 3I’ve logged the container and items and they have been correctly identified inside the frame. However, isotope had already recognized the container only but still couldn’t recognize the items.
Forum: Developing with WordPress
In reply to: Isotope itemSelector issue with API Version 3I appreciate your help, but I’ve already tried your suggested solution. Unfortunately, it didn’t work. Even after passing the items to the
itemSelectoroption, Isotope still couldn’t recognize them. According to the library documentation, theitemSelectoroption only accepts CSS selectors, not NodeLists or arrays. Am I right?