onur-km

<?php
/**
 * Extend WordPress search to include custom fields
 *
 * https://adambalee.com
 */

/**
 * Join posts and postmeta tables
 *

onur-km

First you need to [register_rest_fields][1] to adding custom endpoints in WP REST API JSON Response

add_action( 'rest_api_init', 'add_custom_fields' );
function add_custom_fields() {
register_rest_field(
'post', 
'custom_fields', //New Field Name in JSON RESPONSEs
array(
    'get_callback'    => 'get_custom_fields', // custom function name 

'update_callback' => null,

onur-km

Adding custom fields in the WordPress REST API

When we look at the standard REST API responses it’s clear to see that many download data operations will need additional queries to be effective. One possible solution for this issue is the addition of custom fields to the responses the REST API returns.

What’s the best way to add custom fields in the WordPress?

There’s two possible methods for adding custom fields to to REST API responses:

onur-km

<?php
    function create_ACF_meta_in_REST() {
        $postypes_to_exclude = ['acf-field-group','acf-field'];
        $extra_postypes_to_include = ["page"];
        $post_types = array_diff(get_post_types(["_builtin" => false], 'names'),$postypes_to_exclude);

        array_push($post_types, $extra_postypes_to_include);

        foreach ($post_types as $post_type) {
            register_rest_field( $post_type, 'ACF', [

onur-km

It's possible to some extent but won't be really accurate, the idea is load image with a known file size then in its onload event measure how much time passed until that event was triggered, and divide this time in the image file size.

Example can be found here: https://stackoverflow.com/questions/4583395/calculate-speed-using-javascript

Test case applying the fix suggested there:

onur-km

Is checking for the href starting with # a fully sufficient way to handle this? What about links that include a relative path, absolute path, or full URL to the same page with a fragment?

The last time I checked this, it appeared that browsers issue requests unless the href starts with #, however, I have rerun those tests today and they don't issue requests anymore. With that in mind, we can update the workaround to:

document.addEventListener('turbolinks:click', function

onur-km

CREATE TABLE `vergi_daireleri` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `plaka` varchar(3) COLLATE utf8_unicode_ci DEFAULT NULL,
  `il` varchar(50) COLLATE utf8_unicode_ci DEFAULT NULL,
  `ilce` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL,
  `daire` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
 
INSERT INTO vergi_daireleri (id, plaka, il, ilce, daire) VALUES (1, '01', 'ADANA', 'Merkez', '5 Ocak Vergi Dairesi Müdürlüğü');

onur-km

function successListener() {  
  var data = JSON.parse(this.responseText);  
  console.log(data);  
}

function failureListener(err) {  
  console.log('Request failed', err);  
}

var request = new XMLHttpRequest();