Prangesco
Forum Replies Created
-
Ok, I might have found a workaround to solve this, at least in my case. I am leaving it here in case anybody else might need it. I solved it by simply changing the HTML container tag to main from div in the Elementor Single Product Settings .
Awesome, thanks
Honestly, I had totally missed that menu item.Forum: Reviews
In reply to: [Import and export users and customers] it does it allno need javier, my message on the forum lays out how to make it work (in your earlier answers you forgot to add a second requirement to assign courses, there are more metakey to specify).
I though it might be helpful to other usersForum: Plugins
In reply to: [WCFM - Frontend Manager for WooCommerce] Priority support not answeringok, I will open a new one, thanks
Forum: Plugins
In reply to: [WCFM - Frontend Manager for WooCommerce] Priority support not answeringThere is no URL, I submitted your premium support form here https://wclovers.com/premium-support/
and then the conversation moved over email.Forum: Plugins
In reply to: [WCFM - Frontend Manager for WooCommerce] Priority support not answeringthe original email was open as a ticket on your support forum.
Mu first order with you guys was #104959solved with the last update.
Awesome again.
cheers !and the varints are cascading: meaning each auction product is a subvariant of the previous one (sorry for these dripping messages)
basically all auctions products are read as variants of the same product in FB, only standard product are left out as non-variants
see the edit to my comment pls, hpe this won’t complicate things;)
It worked like a charm.
Thanks a lot guys, super fast and super reliable.
I’ve just left you the review you I definitely owe you after having used your product for so long. This fast support of yours was top notch.There is only one problem left which I hope you can help me solve:
One of my product has now 26 variants in FB (all the other products in the end) despite in woocomerce they are not variants of the same one… What to do?Thanks again!
- This reply was modified 5 years, 11 months ago by Prangesco. Reason: found and extra issue
@kts915
Thanks mate!
you can’t imagine how useful your comments have been to me and mine. We’ve been struggling to fix this problem and eventually had to write a (very complicated) workaround. Your snippets solved it smooth and nicely and we wera able to revert to our original built design.Just passing by after some testing to say thanks.
Our issue was that no notifications went through when posting with FEP PRO (as you may read at the top of this thread).
Hail and Kudoz to thee!Forum: Plugins
In reply to: [Frontend Publishing] FEP pro conflicting with BNFW?I do confirm what @wp Gurus replied and take the chance to thank him publicly for his support.
BNFW notifications are not hindered completely, they indeed work if posts are submitted from wp dashboard but are not notified if submitted from the fron-end. I’ll be updating this thread with any solution any of us would be able to come up with for future users to get advantage of it.
Thanks to you to keep helping Jack,
as you pointed out this is actaually the case. I found one instance of wp_insert_post and none of wp_create_post .
It is located in the function responsible for inserting the post into the database. What would you advise?Anyway the function is commented as follows:
/**
* Inserts user submitted data into DB with WordPress’ own wp_insert_post(). If insertion is successful, sets terms, saves meta and creates the thumbnail.
*
* It traverses through the form fields and by checking their types puts the corresponding data items ($post_data[$key]) into either $post, $custom_fields, $hierarchical_taxonomies or $non_hierarchical_taxonomies. The first one is inserted using wp_insert_post(). It should be noted that the key of each field is used as the name attribute in the form. This is why we are able to access the right piece of information using $post_data[$key].
*
* @access private
* @param array $post_data An array containing all the data from the form. It is actually $_POST.
* @return int or WP_Error Either the ID of the new post is returned or a WP_Error object.
**/Let me know if there’s any other piece of info I can provide within the constraints of the plugin license or provide any email address of yours if it simpler for you to continue this conversation via email.
Thank you very much again