ramblinollie

Thanks for your comment Phil, the details you shared enabled me to return a “Validation successful” message in the plugin settings. What I’m getting though when I make an actual request (using the Boomerang REST client from the Chrome store) is the following message. Do you have any more tips about how to get this working? Thanks!

{
“code”: “civicrm_rest_api_error”,
“message”: “Missing or invalid param \”api_key\”.”,
“data”: null
}

I figured out what was going on. I had tethered my laptop to my Android phone for the first time. The mobile browser obviously processes the HTML in a different way, pulling the contents out of all the external resources and rendering them inline. This looks to be causing some knock on problems but I’ll document them elsewhere.

Ah, nope, truemc was right, it’s the post-type-switcher plugin, there’s a conflict because it doesn’t recognise “widget block” as a post type in it’s select menu.

Hi, this has become an issue for me too. I’m wondering whether it has anything to do with me adding a my own custom post type and the wysiwyg plugin becoming confused by this…

Great plugin though! Apart from this issue I’m finding it really useful, thanks.

I forget what project it was that I needed this for, sorry! The following query looks similar to the one I posted here. I’m not a WP ninja so I probably can’t be much more help than this…

$custom_links_args =  array(
    'post_type'  => $post_type_array,
    'exclude' => $post_id,
    'posts_per_page' => $display_num,
    'tax_query' => array( array(
      'taxonomy' => 'post_tag',
      'terms'    => $page_tags_array,
    ) )
  );

Aha! Opening my eyes to the possibility that the bug wasn’t in your code made me realise it was probably in my code and I promptly found a bug. Fixed now! Thanks!