Stiofan O'Connor

You are welcome! 🙂

Hi Jeff,

There are a number of different ways this can be done, the default timing fields hooks will only fire if it has a value, so it could be replaced only if it had a value, You could use this filter ‘geodir_filter_geodir_post_custom_fields’ to give it a value even if it does not have one, or you could use that filter to add a brand new field on the fly in any position you want or you could simply use the address hooks to add it after the address.

Then you have these 3 hooks you can use:

/**
                     * Called before a custom fields is output on the frontend.
                     *
                     * @since 1.0.0
                     * @param string $html_var The HTML variable name for the field.
                     */
                    do_action("geodir_before_show_{$html_var}");
                    /**
                     * Filter custom field output.
                     *
                     * @since 1.0.0
                     *
                     * @param string $html_var The HTML variable name for the field.
                     * @param string $html Custom field unfiltered HTML.
                     * @param array $variables_array Custom field variables array.
                     */
                    if ($html) echo apply_filters("geodir_show_{$html_var}", $html, $variables_array);

                    /**
                     * Called after a custom fields is output on the frontend.
                     *
                     * @since 1.0.0
                     * @param string $html_var The HTML variable name for the field.
                     */
                    do_action("geodir_after_show_{$html_var}");

It would be great if you could use the below filter to add the business hours to our schema output also:

/**
     * Allow the schema JSON-LD info to be filtered.
     *
     * @since 1.5.4
     * @param array $schema The array of schema data to be filtered.
     */
    $schema = apply_filters('geodir_details_schema', $schema);

If you have any questions feel free to ping me on skype.

Thanks,

Stiofan

Hi Brik,

You seem to have a coming soon page up now so i cant check, can you provide wp-admin details in a private reply? (only staff can see private replies)

Thanks,

Stiofan

Hello,

For the map problem, please replace this file in core: https://github.com/GeoDirectory/geodirectory/blob/master/geodirectory-functions/map-functions/get_markers.php

Thanks,

Stiofan

Hello,

Yes our fields are not standard meta data, we do this for many reasons.

We have a few helpfull functions if you already have an ID, https://wpgeodirectory.com/docs/codex/geodirectory_functions/geodir_get_post_info/

but if you want something like a query, this should do it:

global $wpdb, $plugin_prefix;
        $post_type = 'gd_place';
        $table = $plugin_prefix . $post_type . '_detail';

        $post_arr = $wpdb->get_results($wpdb->prepare(
            "SELECT * FROM $wpdb->posts p JOIN " . $table . " gd ON gd.post_id=p.ID WHERE gd.gd_city=%s ",
            array('manorville')
        )
            , ARRAY_A);

The good thing about this is you can filter by anything and multiple fields, if you have a complex query you want me to make a example of, just ask.

Thanks,

Stiofan

You need the CPT manager installed.
GD>Custom Post Types>Edit>Revisions – allow for post content (not custom fields) revisions to be stored (not recommended).
Tick that, then check.

Stiofan