Title: htmlBurger's Replies | WordPress.org

---

# htmlBurger

  [  ](https://wordpress.org/support/users/htmlburger/)

 *   [Profile](https://wordpress.org/support/users/htmlburger/)
 *   [Topics Started](https://wordpress.org/support/users/htmlburger/topics/)
 *   [Replies Created](https://wordpress.org/support/users/htmlburger/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/htmlburger/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/htmlburger/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/htmlburger/engagements/)
 *   [Favorites](https://wordpress.org/support/users/htmlburger/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 161 total)

1 [2](https://wordpress.org/support/users/htmlburger/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/htmlburger/replies/page/3/?output_format=md)…
[9](https://wordpress.org/support/users/htmlburger/replies/page/9/?output_format=md)
[10](https://wordpress.org/support/users/htmlburger/replies/page/10/?output_format=md)
[11](https://wordpress.org/support/users/htmlburger/replies/page/11/?output_format=md)
[→](https://wordpress.org/support/users/htmlburger/replies/page/2/?output_format=md)

 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Mighty Blocks - Gutenberg on Steroids] High marks for not reinventing the wheel](https://wordpress.org/support/topic/high-marks-for-not-reinventing-the-wheel/)
 *  [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/high-marks-for-not-reinventing-the-wheel/#post-11989784)
 * Glad that MightyBlocks is working well for you!
 * We’re still early in the development, hopefully soon you’ll have a reason to 
   increase that review rating from 4 to 5 stars 🙂
 * Thanks,
    Emil, Viktor & Georgi
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] How can I do map in carbon fields?](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/#post-10872127)
 * Hi [@vitaminnnka](https://wordpress.org/support/users/vitaminnnka/),
 * The data in the screenshot looks OK as well.
 * Can you try adding `wp_enqueue_script( 'jquery' )` in the `crb_enqueue_scripts()`
   function?
 * If this doesn’t solve the issue, can you share the code with us with a read-only
   access to the repository or by sending it to us on [info@htmlburger.com](https://wordpress.org/support/users/htmlburger/replies/info@htmlburger.com?output_format=md)
   so we can try to reproduce the issue locally?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] How can I do map in carbon fields?](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/#post-10871485)
 * Instead of `add_action( 'carbon_map_api_key', 'crb_get_gmaps_api_key' );` you
   should be using `add_filter( 'carbon_map_api_key', 'crb_get_gmaps_api_key' );`.
 * In addition, change `$google_maps_api_key = '';` to `$google_maps_api_key = crb_get_gmaps_api_key();`
 * The rest seems OK.
 * Can you write `<?php var_dump( $post ); var_dump( $map_data ); exit; ?>` in the
   template and paste the result here? This way I can check if the correct values
   are being returned from `carbon_get_post_meta()` 🙂
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] How can I do map in carbon fields?](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/#post-10870804)
 * Hi [@vitaminnnka](https://wordpress.org/support/users/vitaminnnka/),
 * Can you send me the code which you are using to register the Map Field in the
   administration area?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] How can I do map in carbon fields?](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/how-can-i-do-map-in-carbon-fields/#post-10870498)
 * Hi [@vitaminnnka](https://wordpress.org/support/users/vitaminnnka/),
 * The `$map_data` variable contains the latitude and longitude that you’ve set 
   in the administration area. In order to display a Google Map with these coordinates,
   you will have to use JavaScript to manually initialize the map.
 * Here is an example code:
 * `<div class="map" id="map" style="height: 480px; width: 100%" data-lat="<?php
   echo $map_data['lat']; ?>" data-lng="<?php echo $map_data['lng']; ?>" data-zoom
   ="<?php echo $map_data['zoom']; ?>"></div>`
 * In `functions.php` load the Google Maps API:
 *     ```
       add_action( 'wp_enqueue_script', 'crb_enqueue_scripts' );
       function crb_enqueue_scripts() {
       	$google_maps_api_key = ''; // get from https://developers.google.com/maps/documentation/javascript/get-api-key
   
       	wp_enqueue_script( 'google-maps-api', '//maps.googleapis.com/maps/api/js?key=' . $google_maps_api_key );
       	wp_enqueue_script( 'theme-scripts', get_stylesheet_directory_uri() . '/js/functions.js' );
       }
       ```
   
 * And lastly in `js/functions.js`:
 *     ```
       ;(function ($, document, window, undefined) {
   
       	$(document).ready(function () {
       		var $map = $('#map');
       		var lat = $map.data('lat');
       		var lng = $map.data('lng');
       		var zoom = $map.data('zoom');
   
       		var center = { lat: lat, lng: lng };
       		var mapOptions = { zoom: zoom, center: center };
   
       		var map = new google.maps.Map( $map[0], mapOptions );
   
       		new google.maps.Marker({
       			map: map,
       			position: center,
       		})
       	});
       })(jQuery, document, window);
       ```
   
 * Hope this helps!
 * Let me know if you need more details 🙂
    -  This reply was modified 7 years, 7 months ago by [htmlBurger](https://wordpress.org/support/users/htmlburger/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Feature not working with Gutenberg](https://wordpress.org/support/topic/feature-not-working-with-gutenberg/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/feature-not-working-with-gutenberg/#post-10818247)
 * [@satyajett](https://wordpress.org/support/users/satyajett/) we’re working on
   Gutenberg support, you can see the announcement here: [https://carbonfields.net/2018/04/27/plans-for-carbon-fields-and-gutenberg-integration/](https://carbonfields.net/2018/04/27/plans-for-carbon-fields-and-gutenberg-integration/)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] How can i do a few columns options?](https://wordpress.org/support/topic/how-can-i-do-a-few-columns-options/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/how-can-i-do-a-few-columns-options/#post-10056961)
 * Hello [@makszhukov97](https://wordpress.org/support/users/makszhukov97/),
 * Sorry for the late reply!
 * You can use the `->set_width()` method to set the occupied width of the field
   in its container.
 * For example, the following code will set both fields to take 50% of the width
   of the container they are placed in:
 *     ```
       Field::make( 'text', 'crb_button_label', 'Button Label' )
         ->set_width( 50 ),
       Field::make( 'text', 'crb_button_link', 'Button Link' )
         ->set_width( 50 ),
       ```
   
 * Please refer to the **Width** section of the **Documentation** for more information–
   [https://carbonfields.net/docs/fields-usage/?crb_version=2-1-0](https://carbonfields.net/docs/fields-usage/?crb_version=2-1-0)
    -  This reply was modified 8 years, 3 months ago by [htmlBurger](https://wordpress.org/support/users/htmlburger/).
    -  This reply was modified 8 years, 3 months ago by [htmlBurger](https://wordpress.org/support/users/htmlburger/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Carbon Fields V 2.0](https://wordpress.org/support/topic/carbon-fields-v-2-0/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/carbon-fields-v-2-0/#post-9298616)
 * Hello [@bagerathan](https://wordpress.org/support/users/bagerathan/)
 * At this point we’re not quite sure whether(and how) to distribute Carbon Fields
   v2 via the WordPress plugin repository.
 * The best way to use Carbon Fields v2 is to install it via composer:
    `composer
   require htmlburger/carbon-fields`
 * Carbon Fields is not really a plugin — it’s a library that could be used by plugin
   and theme authors. Carbon Fields, on itself doesn’t do anything – you need to
   write PHP code in order to utilize it. So the best way to update it is via `composer
   update` rather than from the WordPress admin.
 * This post describes those issues pretty well:
 * > [Please do not submit frameworks](https://make.wordpress.org/plugins/2016/03/01/please-do-not-submit-frameworks/)
 * For time being we’re releasing bugfix releases in the WordPress plugin repo(on
   the 1.X branch). We try hard not to introduce breaking changes there.
 * In future we’ll probably add a banner here in the WP repo that the latest version
   lives in github. Or we’ll just delete the plugin and maintain just the composer
   package.
 * Thanks!
    -  This reply was modified 8 years, 11 months ago by [htmlBurger](https://wordpress.org/support/users/htmlburger/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Migrating from Magic Fields to Carbon Fields](https://wordpress.org/support/topic/migrating-from-magic-fields-to-carbon-fields/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/migrating-from-magic-fields-to-carbon-fields/#post-9081412)
 * Hi Nikhil,
 * I glanced at Magic Fields’s source code and it seems to me that the plugin is
   using custom SQL table to store meta values(rather than the WordPress’ standard
   wp_postmeta table). This is unfortunate for you because you can’t easily switch
   to different plugin – you have several options:
 *  * Add CarbonFields without removing MagicFields, define your custom fields in
   the new plugin, and manually copy-paste meta values in the administration; then,
   remove magic fields
    * Install and setup CarbonFields, and create a script to
   migrate the data for you from MagicFields to standard post meta
 * Whichever option you choose, you should also go through your front-end theme 
   code and switch the rendering code from magic fields to `get_post_meta` calls.
 * If I were you, I’d probably just add CarbonFields(without removing MagicFields)
   to the project and use that for new custom fields that are needed — I wouldn’t
   bother changing the old custom fields if they work fine. Both plugins should 
   work just fine together.
 * If you need to add repeaters to existing custom fields that are defined in MagicFields,
   you could change just those fields instead of all fields in the project. This
   isn’t ideal, but it might be the best option if you’re constrained by time.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Use get_posts and order by carbon fields](https://wordpress.org/support/topic/use-get_posts-and-order-by-carbon-fields/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/use-get_posts-and-order-by-carbon-fields/#post-9064234)
 * Closing this in favor of your GitHub issue here:
    [https://github.com/htmlburger/carbon-fields/issues/219](https://github.com/htmlburger/carbon-fields/issues/219)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Carbon Fields Version 2.0](https://wordpress.org/support/topic/carbon-fields-version-2-0/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/carbon-fields-version-2-0/#post-9021860)
 * Hi [@arkimedia](https://wordpress.org/support/users/arkimedia/)
 * We’re aimed at public release for May 15th.
 * We’re currently testing the new version internally and working actively on:
 *  * Backward compatibility testing and fixes (some things like extended fields
   will break, but we try to make upgrading from v1.5 to v2 less painful)
    * Documentation–
   for new features as well as migration guides for old projects
 * We welcome any interested developers to try the new version by
    `composer require
   htmlburger/carbon-fields:dev-milestone/2_0/react-ui`
 * Any feedback will be appreciated.
 * Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Carbon Fields and Yoast SEO Support](https://wordpress.org/support/topic/carbon-fields-and-yoast-seo-support/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/carbon-fields-and-yoast-seo-support/#post-8744456)
 * You can post a feature request over at GitHub ([https://github.com/htmlburger/carbon-fields/issues](https://github.com/htmlburger/carbon-fields/issues))
   and we will discuss internally if we will be adding this soon.
 * In the meantime, you can try and adapt an ACF+Yoast plugin to work with CF (it
   looks like it’s a matter of switching some calls from get_fields() to carbon_get_post_meta()
   etc.). If you go that route, you may even post a PR on GitHub or post it as a
   separate plugin for CF.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Gallery field type](https://wordpress.org/support/topic/gallery-field-type/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/gallery-field-type/#post-8705812)
 * Thanks for the kind words [@matt-k-1](https://wordpress.org/support/users/matt-k-1/),
   glad you like the plugin!
 * We definitely plan to add a gallery field and also many others, but right now
   we are doing a major overhaul of both back and front-end code, which pushes new
   features back.
 * If you are not willing to wait, here are some useful links (no tutorials, sorry)
   that might help you with the implementation of your own gallery field:
 * A boilerplate for making new fields: [https://github.com/htmlburger/carbon-field-template](https://github.com/htmlburger/carbon-field-template)
   
   A gallery field made by the community: [https://github.com/htmlburger/carbon-fields/pull/97](https://github.com/htmlburger/carbon-fields/pull/97)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] Post Meta on Options Pages?](https://wordpress.org/support/topic/post-meta-on-options-pages/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/post-meta-on-options-pages/#post-8622106)
 * > Is there a way to create meta boxes on the side of theme_options pages?
 * Currently, `set_context()` is only supported for the `post_meta` container (as
   WordPress’ post edit screen is the only screen which defines display contexts
   for meta boxes).
 * > I’m not sure what the show_on_post_type($type) attribute is supposed to be.
 * `show_on_post_type($type)` limits the visibility of a `post_meta` container to
   one or more post types. For example, `show_on_post_type('post')` will only add
   the container to posts but not to pages or other custom post types that may be
   defined.
 * PS:
 * Looking at your code you are creating a `post_meta` container, not a `theme_options`
   one. You can read more on the different types of containers here: [https://carbonfields.net/docs/containers-usage/](https://carbonfields.net/docs/containers-usage/)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Carbon Fields] vertical tabs](https://wordpress.org/support/topic/vertical-tabs-10/)
 *  Plugin Author [htmlBurger](https://wordpress.org/support/users/htmlburger/)
 * (@htmlburger)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/vertical-tabs-10/#post-8622060)
 * [@jonwaldstein](https://wordpress.org/support/users/jonwaldstein/)
    Adding tabs
   to complex entries in the way you need is currently not supported. You can add
   tabs directly to containers or display each complex entry as a tab but cannot
   have tabs inside each complex entry.
 * To improve readability you can use the separator field but it will still be showing
   all fields inside the complex entry.

Viewing 15 replies - 1 through 15 (of 161 total)

1 [2](https://wordpress.org/support/users/htmlburger/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/htmlburger/replies/page/3/?output_format=md)…
[9](https://wordpress.org/support/users/htmlburger/replies/page/9/?output_format=md)
[10](https://wordpress.org/support/users/htmlburger/replies/page/10/?output_format=md)
[11](https://wordpress.org/support/users/htmlburger/replies/page/11/?output_format=md)
[→](https://wordpress.org/support/users/htmlburger/replies/page/2/?output_format=md)