UX Themes
Create
Log in
Sign up
Home
Feedback
Flatsome Features
Boards
Flatsome Features
Powered by Canny
Flatsome Features
(Don't post issues or questions here please!)
Here you can post Feature Request for Flatsome Theme. You can also vote for the ones you like to see in one of the next versions of Flatsome.
Description
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
Complete
posts
Tabbed Dropdown
Option to have a Tabbed Dropdown like https://www.etsy.com/
47
·
planned
249
FS 4.0 Remove unused CSS
I noticed that some other themes are only loading the necessary CSS for the used shortcodes on a page. It would be great to have this feature in FS 4.0 / UX 2.0. This also speeds up the website as the unused CSS won't load.
11
·
planned
131
Font Awesome for Icon Box ++
Integrate font Awesome or other icon fonts to UX Builder.
43
·
planned
211
Search results page for blog only
If "Enable live search for products and pages." option is not enabled in Flatsome>Advanced>Site Search, results page should be "search.php" instead of "archive-product.php". Some users use Flatsome just for blogging and Woocommerce only for login feature. They don't want to see "No products were found matching your selection." in search results page.
5
·
planned
116
Disable UX Builder Altogether - Flatsome Theme & UX Builder Plugin
I really like your theme, it is definitely the best for any WooCommerce store. However it falls short in 1 major area. As per the wordpress theme guide a page builder shouldn't be integrated into the theme. It should be a seperate plugin that works along side of the theme. Look at all the major themes and page builders. Beaver Builder is the most popular and they have a beaver theme and and beaver builder plugin. This way I am free to use their builder on any theme and vice versa I am free to use their theme with any builder. Other page builders follow the same pattern such as Divi etc. The fact that flatsome UX builder is deeply integrated into the theme is very worrying. There is no option to enable or disable the UX builder and from testing with other page builders such as Divi and Beaver Builder there are compatibility issues with UX Builder. Now long term it would be even more ideal if UX Builder was a separate plugin. If you think that UX builder is good product then you would want it installed on other themes other than flatsome. However the main reason for separating them would be to allow customers to install their own preferred page builder which they are comfortable with. What happens if someone decides to switch themes in the future? They would have to recreate all their pages with another builder instead of continuing to use UX builder with their new theme.
31
·
planned
149
Powered by Canny