radykal | Support Center Chooser

For which product do you need support?

Fancy Product Designer Multistep Product Configurator Another

Start a new topic
Answered

FPD and UX Builder for Flatsome

Hi,


I'm not sure if this is already on a to-do log, but I noticed that the `fpd_products` meta was getting cleared when updating a product by using Flatsome's frontend builder.


I fixed it by adding the following code to `class-admin.php` in `update_custom_meta_fields` function.

if (defined('UX_BUILDER_SAVING') && UX_BUILDER_SAVING)
		    	return $post_id;

I don't feel comfortable editing plugins as they might get overwritten on update, but I couldn't find a way to remove the action in the theme's functions.php since the FPD_Admin class is not accessible via a global variable.


Can you guys take a look at this?


Thanks!


Best Answer

Johnny,


It was a server configuration denying direct access to `/wp-content/plugins/fancy-product-designer/assets/templates/productdesigner.php` file. Good intentions, but they weren't working for your plugin. Carlos's issue has been resolved.


The original issue mentioned on this post hasn't been addressed. Will the fix be included in future versions of the plugin?


Thanks,

Mihai


Hi,


Why has this been moved to the community discussions section?


It's a bug - the plugin is incompatible with a theme editor - and I feel it would benefit users if the fix would be included.


Thanks.

Mihai!


I also have FLATSOME and I just cannot use FPD too.  In the admin side the UI & Layout Composer, it just appers as INITIALIZING PRODUCT DESIGNER, does nothing.  Can you help me with any tips?  Im really lost here.


Thank you!!

Hey, Carlos.


I can sure try, but I'll need to take a closer look. Leave an address here and I'll drop you an email.


Thanks,

Mihai

Sure:  lineamovil from hotmail.


Thank you!

Answer

Johnny,


It was a server configuration denying direct access to `/wp-content/plugins/fancy-product-designer/assets/templates/productdesigner.php` file. Good intentions, but they weren't working for your plugin. Carlos's issue has been resolved.


The original issue mentioned on this post hasn't been addressed. Will the fix be included in future versions of the plugin?


Thanks,

Mihai

Login or Signup to post a comment