Support » Plugin: ACF PHP VARS » Please add support for custom DB table prefixes

  • Resolved Dave3o3

    (@dave3o3)


    Hi there,

    first of all, this plugin is exactly what I needed! Great work! 🙂

    But I have some issues for you:

    1. I needed to edit your plugin code because i don’t use the standard “wp_” table prefix 😉
    2. And I don’t know if it’s efficient to use the ‘_edit_last’ meta_key because the plugin will list also posts/pages which contain acf-related shortcodes. But I don’t know if this is causing the issue.

    Your plugin is very nice and useful! Keep on the good work!

    https://wordpress.org/plugins/acf-php-vars/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author samjco

    (@samjco)

    Oops did i make it restrictive to wp_?
    What line may I ask?

    Which version of ACF are you using, PRO?
    Can you elobarate more on number 2?

    Oops did i make it restrictive to wp_?
    What line may I ask?

    On lines 49, 51 and 128 (inside your SELECT statements).

    Which version of ACF are you using, PRO?

    5.3.9.2 PRO

    Can you elobarate more on number 2?

    I’m using a theme which is formally based on shortcodes and I’m also using custom shortcodes which call acf fields. But I don’t know if this is causing the issue. Furthermore I think that you are caching all postIDs of posts which have an “_edit_last” meta_key is causing the issue. So maybe you should define a new query which only looks for “acf-field-group”-post types.

    Best

    Dave

    Two enquiries in 2 days for table prefix support. If you could please consider adding, I am running multisite which means the $blog-id is also part of the prefix. This link https://paulund.co.uk/table-prefix-wordpress provides some insights if that helps.

    I altered the selects as per @dave3o3 but the results were incorrect. I too are using ACF PRO 5.3.9.2

    The first list of fields were all part of one field group, but the title in comments had another field group name.

    Thanks, Dean

    Here’s a clearer fix for the custom db prefix issue for single site installations:

    //Grab ACF Field Group Object
    
    	//Creates the table. The ID and Class make the sorting work. 
    
    	  
    	    if(!$ACF_PRO_active):
    	    $acf_field_group_VARS = $wpdb->get_results('SELECT * FROM  '.$wpdb->postmeta.' WHERE meta_key =  "rule"');
    		else:
    	    $acf_field_group_VARS = $wpdb->get_results('SELECT * FROM '.$wpdb->postmeta.' WHERE meta_key = "_edit_last"');
    		endif;
    
    		?>
    

    and

    
    //If ACF PRO
    		            $acf_field_field_VARS = $wpdb->get_results("SELECT * FROM '".$wpdb->posts."' WHERE post_parent = '".$acf_field_group_var_ID."' ");
    		        	$acf_field_group_keys_ARRAY = $acf_field_field_VARS;
    				endif;
    

    Where we replaced any queries that included the table prefix such as wp_postmeta and wp_posts with the proper method of calling a db object using the global $wpdb->object

    Plugin Author samjco

    (@samjco)

    Thanks for your support..
    What line numbers?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Please add support for custom DB table prefixes’ is closed to new replies.