[jan]

Thanks, but I’m not sure where / how to add that line in my custom plugin.
If I add it into the actual function being called, it doesn’t seem to do anything, if I add it outside, $vendor_id is not defined. This is what I have now:

function custom_store_settings( $vendor_id ) {
    global $WCFM, $WCFMu;
    $wcfm_vendor_custom_options = (array) get_user_meta( $vendor_id, 'wcfm_vendor_custom_options', true );
    $wcfm_vendor_desc_website = isset( $wcfm_vendor_custom_options['website'] ) ? $wcfm_vendor_custom_options['website'] : '';
    // some more fields here
?>
    <!-- collapsible -->
    <div class="page_collapsible" id="wcfm_settings_form_vendor_custom_head">
        <label class="fa fa-file-image-o"></label>
        <?php _e('Winery Images', 'wc-frontend-manager-ultimate'); ?><span></span>
    </div>
    <div class="wcfm-container">
        <div id="wcfm_settings_form_vendor_desc_expander" class="wcfm-content">
            <?php

            $WCFM->wcfm_fields->wcfm_generate_form_field( apply_filters( 'wcfmu_settings_fields_vendor_store_invoice', array(
                "wcfm_vendor_descr_website" => array('label' => __('Website', 'wc-frontend-manager-ultimate'), 'type' => 'text', 'name' => 'wcfm_vendor_custom_options[website]', 'class' => 'wcfm-text wcfm_ele', 'label_class' => 'wcfm_title wcfm_ele', 'value' => $wcfm_vendor_desc_website, 'hints' => __( 'Your website URL', 'wc-frontend-manager-ultimate' ) ),
                // more fields here
            ) ) );
            ?>
        </div>
    </div>
    <div class="wcfm_clearfix"></div>
    // More containers and fields here
    <!-- end collapsible -->
    <?php
}
add_action( 'end_wcfm_vendor_settings', 'custom_store_settings', 20 );

function custom_store_settings_update( $user_id, $wcfm_settings_form ) {
    global $WCFM, $WCFMu, $_POST;
    if( isset( $wcfm_settings_form['wcfm_vendor_custom_options'] ) ) {
        $wcfm_vendor_custom_options = $wcfm_settings_form['wcfm_vendor_custom_options'];
        update_user_meta( $user_id, 'wcfm_vendor_custom_options',  $wcfm_vendor_custom_options );
    }
}
add_action( 'wcfm_vendor_settings_update', 'custom_store_settings_update', 20, 2 );

[jan]

There is an error sending that as well:
“There was an error trying to send your message. Please try again later.”
Very strange. Can I drop you an Email?

[jan]

I wanted to add a guide how to enable user search with custom URL for Ajax Search Pro, but trying to post this I’m always getting an ” ERROR: Your reply cannot be created at this time.”

So, sorry. I’ve tried without any curly brackets and stuff but it doesn’t let me post it.

[jan]

Great, thanks!

This:
“stores are nothing but site users”
was the missing piece.

Knowing that, I was able to achieve what I need thanks to that information.
For the default search, the WP extended search plugin mentioned above will do the trick as it adds users to the basic search.

Consider this solved 🙂

[jan]

Hi,

I can give you an account, but I’d suggest checking the default WordPress search first. If the default search can find a store site, Ajax Search Pro will be able to find it as well.
I double checked by deactivating the plugin, and the default search doesnt come up with store sites either.

Regards,
Jan

[jan]

When posting this I was on 5.2.6 yesterday, now I am on 5.2.7.
Both versions do not show the maps field, just the heading. Tested with products and articles. Other fields are displayed OK.

Thanks for checking 🙂

[jan]

Hi there 🙂
After all the updates the last weeks (amazing!) I tested again, but it seems the left over ACF issues have not been addresses, have they?
– ACF image fields unusable
– Append/Prepend info not displayed
– Maps field not displayed

Is this on your agenda or do I need to find workarounds?
Thanks and have a nice day!

[jan]

Hi,
sorry for the late reply. The plugin is https://ajaxsearchpro.com/
But I’m pretty sure that if the default search could find the stores, the plugin could do as well.
Thanks & Regards,
Jan

[jan]

Nobody knows why Ultimate update was not displayed but the other two were. I got the update now, two days later. WordPress magic 😀

Select field issues and datepicker issues are resolved – these were the most important ones. Awesome! 🙂

Append/Prepend hints are not shown yet.
Maps, I’m still testing, currently the field is not displaying yet.

Thanks for looking into the image issue as well!
Very nice to see progress so fast!

[jan]

Sorry guys, I just found another one, similiar to the post above from Dec 17:
ACF image fields get saved to the DB with their URL instead of their ID. ACF itself stores the images by ID
Result: value returned wrong, preview image not displayed neither in native ACF nor in store manager, not compatible to native ACF view.

[jan]

In v5.2.5 Changelog, it says:
Enhance – ACF and ACF Pro map field support added
Enhance – ACF time and date-time field type support added
Fixed – ACF date picker field issue resolved
Fixed – ACF select field index issue resolved

Unfortunately, I cannot confirm any of these changes/fixes :-/
Am I missing something or is it because there is no new according Ultimate version yet?

Nevertheless, appreciate you’re working on it! 🙂

Have a nice day!

[jan]

Hi,
just recognized another issue which is a bit worse than the others:
For ACF select fields, always the selected number is saved, not the value itself.
Example: ACF select field has selectable values 2018, 2019, 2020, 2021. In store manager, I select 2019. In the database, it’s saved as “2”, as I have selected the second value.
If I edit the product without WCFM Ultimate in WooCommerce directly, it’s saved correctly as “2019”.

I could probably get around this with another query, but this has several other ugly impacts besides just a wrong return value: Switching between WCMF and native product editing loads wrong values, and adding/removing another possible ACF value for the select would change all saved values.

Thanks & Regards!

[jan]

OK, understood. Until then, also the menu manager changes of the icon take no effect? Or is that an issue with my installation only?

(When I added FA5 to a plugin I have written some time ago, there were no issues, but I guess it might be different with the amount of plugins you have to ensure compatibility with. Amazing you can manage that all.)

[jan]

Alright, thanks. I just wanted to avoid another plugin and manually coding it into my custom post type. With ACF, it would have been in the right place already 🙂
Besides the datepicker issue , also the size values (rows for textarea for example) and the Append/Prepend values are ignored.

Thanks a lot for your great support!

[jan]

FYI:
Date Picker field type throws an error as well:
Notice: Undefined index: date_format in […]/wp-content/plugins/wc-frontend-manager-ultimate/views/thirdparty/wcfmu-view-acf-products-manage.php on line 192

[jan]

Hi,
Any update on this?
I see you are shipping two versions of font-awesome now, but all icons used still seem to be using the “fa” class, not “fas”. Also, when I try to change the icons in menu manager, there is no change, regardless of the version used?
Thanks & Regards!

[jan]

Funny, I just wanted to ask the same question:
jQuery Google map location selector don’t work for me when I use advanced custom fields with WCFM. It just doesn’t show in the Tabs. Is it planned to support this in future?
Also, the Append/Prepend values don’t show for number fields.

[Author]

Posts