mishterk

<?php
// In a post/page template, loop over the ACF flexible field layouts and load the partial
// responsible for rendering the layout. 
while ( the_flexible_field('my_flexi_field') ) {
	get_template_part( 'components/'. get_row_layout() );
}

mishterk

<?php

add_filter('acf/settings/remove_wp_meta_box', '__return_true');

mishterk

<?php

// Define this in the site's wp-config.php file.
define('GOOGLE_API_KEY', 'your-google-api-key-here');

// Add this to your functions.php file, or a config plugin/MU plugin. 
add_filter( 'acf/fields/google_map/api', function ( $api ) {
	$api['key'] = GOOGLE_API_KEY;

	return $api;

mishterk

<?php
add_filter( 'acf/settings/show_admin', function () {

	// Get the current site url.
	$site_url = get_bloginfo( 'url' );

	// Define an array of protected site urls.  
	$protected_urls = array(
		'https://www.example.com',
		'http://staging.example.com'

mishterk

<?php
// Get all the local field groups and loop through them for processing.
$field_groups = acf_get_local_field_groups();
foreach ( $field_groups as $group ) {

	// If the field group has fields, load them into the 'fields' key. 
	if ( acf_have_local_fields( $group['key'] ) ) {
		$group['fields'] = acf_get_local_fields( $group['key'] );
	}

mishterk

Using ACF Custom Database Tables for attachment meta

The only thing stopping the use of ACF Custom Database Tables for attachment fields is the logic we currently have in place that limits the use of the UI depending on a field group's location rules. The plugin expects either a post type or a user location rule and if it can't find one, it won't allow a table to be enabled for the field group in question so, when an Attachment location rule is used, the creation of a DB table is blocked as there is no post type in the location rules array.

This can be worked around by simply adding the attachment post type to the Post Type location rule values list, as per the code snippet below.

You can then set up the location rules as follows:

![ACF Location Rules](https://gist.github.com/mishterk/fab2cd441c873b1884a0e446

mishterk

<?php 

$query = new WP_Query([
  
  // Standard query args. Using post__in can be much faster. If searching ACF custom 
  // database tables data, plugin the found post IDs in here.
  'post_type' => 'post',
  'post__in' => [1,2,3], // array of post IDs 
  
  // Optional args to improve performance. Use these to cut down on internal 

mishterk

Controlling JSON encoded flags in ACF Custom Database Tables version 1.0.x

The ACF Custom Database Tables plugin uses JSON encoding to prepare complex values for storing in the database. This differs to WordPress' core approach as WordPress relies on serialization instead. By default, the plugin opts to not escape slashes when encoding but there may be times where additional flags need to be used. e.g; JSON_UNESCAPED_UNICODE.

The following example demonstrates how to short-circuit the plugin's encoding algorithm in order to define custom args for the wp_json_encode() function. It uses the acfcdt/filter_value_before_encode filter found in \ACFCustomDatabaseTables\Intercept\ACFInterceptBase::maybe_encode().

This example is JSON only

Note that this example is using JSON encoding which is what the plugin expects when attempting to decode data for return from the database.

mishterk

<?php

get_header();
?>
<div class="Main">

	<?php if ( have_posts() ): ?>
		<?php while ( have_posts() ): ?>
			<?php the_post(); ?>
            

mishterk

<?php

class View {


	public static $view_dir = '';


	/**
	 * Render View Template With Data