• timichango

• in reply to: How can I retrieve fields from an options page using the REST API (v5.11)?
• December 10, 2021 at 4:59 pm

Retrieve data from the endpoint in JS (in my case, this is inside a Vue.js method):

fetch('/wp-json/canopy/v2/acf--colspec/')
.then(resp => {
  // Yay, data!
  return resp.json();
})
.then(data => {
  // Do stuff
})
.catch(function() {
  // Handle errors
});

• timichango

• in reply to: How can I retrieve fields from an options page using the REST API (v5.11)?
• December 10, 2021 at 4:59 pm

Thanks to your suggestion I wound up learning how to create a custom endpoint, so thanks for that!

I wound up creating a custom endpoint that executes and returns the result of a get_field(); call against my options field, which worked a charm.

Here’s what I wound up with, in case it’s helpful for anyone else trying to do something similar:

Set up the endpoint and callback:

function cp_colspec_endpoint() {
  $field = get_field('col_spec','options');
  return $field;
}

//expose acf options page field(s) through custom endpoint
function cp_register_api_endpoints() {
  register_rest_route( 'canopy/v2', '/acf--colspec', array(
    'methods' => 'GET',
    'callback' => 'cp_colspec_endpoint',
  ) );
}

add_action( 'rest_api_init', 'cp_register_api_endpoints' );

• timichango

• in reply to: How can I retrieve fields from an options page using the REST API (v5.11)?
• December 10, 2021 at 4:58 pm

Hm — I posted a reply with a a bunch of details, but it seems to have disappeared while editing it for some reason. Bummer 🙁

Re-posted my original notes below…

• timichango

• in reply to: Anchor in WP-Blocks
• September 1, 2021 at 4:50 pm

Anchor IS indirectly mentioned in the documentation: the documentation states:

supports
(Array) (Optional) An array of features to support. All properties from the JavaScript block supports documentation may be used. The following options are supported:

If you read the linked documentation at https://developer.wordpress.org/block-editor/developers/block-api/block-supports/ — anchor is the first parameter on the list.

• timichango

• in reply to: Required fields in Gutenberg editor
• August 4, 2021 at 11:28 pm

Bump — just curious if there’s been any progress on this deficiency?

Thanks!

• timichango

• in reply to: All ACF Post fields suddenly in sidebar
• February 21, 2021 at 7:02 pm

I’m having the same issue — I accidentally clicked an arrow, and now I can’t retrieve my field set from the sidebar — and attempting to change the position from the fieldset’s own edit screen has NO effect. I’m not sure what the intended functionality is supposed to be here, but it’s not working.

Any advice about how to get my fieldset back to where it’s intended to be, other than trashing it and remaking it, or disabling Gutenberg, would be very appreciated.

Thanks!

• timichango

• in reply to: Fields showing on all Pages despite Field Group location rules.
• December 19, 2018 at 1:16 pm

I’ve now tested 5.8-beta3, and it does fix the issue for me as well. Whew!

Thanks ACF team for tackling that!

• timichango

• in reply to: Fields showing on all Pages despite Field Group location rules.
• December 19, 2018 at 12:38 pm

Are those betas available anywhere for download/installation? I’ve got clients giving me some serious stink-eye about the mess in admin right as they’re smack in the middle of populating content for the launch of their new website, and I’d sure like to resolve this for them ASAP if possible.

Cheers

Edit: figured out that they’re available through the account screen (I’d previously looked at the github repo to no avail).

• timichango

• in reply to: How can I filter a posts relationship field by the current category edit screen?
• November 18, 2015 at 8:31 am

thanks — I’ll give that a shot and report back!

• timichango

• in reply to: How can I filter a posts relationship field by the current category edit screen?
• November 14, 2015 at 10:30 am

Bump?

• timichango

• in reply to: V5 and theme customizer
• July 14, 2015 at 10:23 am

+1 on this

• timichango

• in reply to: Preview solution !
• October 22, 2013 at 7:49 pm

Holy. Heck.

This is great—I’ve been bashing my head against the wall trying to figure out what was going on with this whole postmeta black-hole issue. I have encountered it with both ACF and another custom plugin which leverages postmeta to store supplementary content.

I’m off to test this immediately.

Is the WP community at large aware that this behaviour is occurring? I’ve done a bunch of poking around, but can’t find any formal documentation of this bug anywhere, but I can concur that it definitely exists.