Code Amp

Hey @andreasja

Yeah I think this is the right approach.

A WordPress query, if ordered by a custom field will remove any entries that don’t have that custom field associated – which you’ve already discovered and worked around by adding this custom field to the “post” post type.

That’s the best way around it, but it is a work around, I wish there was a way to specific in a query whether or not we wanted to include results which don’t have the custom field but as far as I’m aware it’s not possible yet…

There was one point I mentioned earlier regarding conditionally loading this query modification.

If you are creating a specific page, with your layouts on, then you can simply add a check to make sure we are on the right page, before adding your logic:

function layout_query_args( $query_args, $layout_id ) {
	// Block editor way would be to check what the current page is
	/* if ( ! is_page( 'my-page-name' ) ) {
		return $query_args;
	} */
	
	// Because you created layouts in our admin pages, they have an ID so you can test for it here
	// Change 123 for your own layout ID
	if ( $layout_id	!== 123 ) {
		// If the ID doesn't match, get out of here
		return $query_args;
	}
	
	// Now we know the modifications will only apply to a layout with ID - 123
	// We can add our modifications
	$query_args[ 'meta_key' ] = 'list_number';
	$query_args[ 'orderby' ] = 'meta_value_num  date';
	$query_args[ 'order' ] = 'DESC';

	// Always return in WP filters
	return $query_args;
}

add_filter( 'custom-layouts/layout/query_args', 'layout_query_args', 10, 2 );

Here you can see, I’ve added $layout_id to the function, and tested against layout ID 123 – change this for your layout ID.

Also note, the add_filter(... line has a , 2 argument added, which allows us to get the $layout_id passed into the function.

Let me know if that makes sense

Best
– Ross

• This reply was modified 4 years, 3 months ago by Code Amp.
• This reply was modified 4 years, 3 months ago by Code Amp.
• This reply was modified 4 years, 3 months ago by Code Amp.

Hey @atoyansk

That code looks a little off.

Lets try to look at the issue another way (I hope I understood it correctly).

Why don’t we create 3 seperate layouts, and for each one, restrict them to a specific country?

If that sounds like what you are trying to do, or would work, then I can help with the logic to set that up.

The other question would be, how are you creating layouts, via the block editor, or via our admin pages?

Thanks

• This reply was modified 4 years, 4 months ago by Code Amp.

Hey @andreasja

You would need to use our custom-layouts/layout/query_args filter from here:
https://customlayouts.com/documentation/action-filter-reference/

And then add this (modified code) to your child themes functions.php file.

Try this:

function layout_query_args( $query_args ) {
	// Modify the query args
	$query_args[ 'meta_key' ] = 'your_key';
	$query_args[ 'orderby' ] = 'meta_value_num';
	$query_args[ 'order' ] = 'DESC';
	
	// Always return in WP filters
	return $query_args;
}

add_filter( 'custom-layouts/layout/query_args', 'layout_query_args', 10 );

You would need to change your_key to your custom field key (if you are using ACF, let me know, as its not as straight forward as you might think)

Also: just to warn you, this code will apply to all layouts on your site.

What you probably want to do is restrict this to a layout ID or specific page.

How are you creating your layouts, as blocks, or via our admin pages?

Thanks

• This reply was modified 4 years, 4 months ago by Code Amp.
• This reply was modified 4 years, 4 months ago by Code Amp.
• This reply was modified 4 years, 4 months ago by Code Amp.

Hey @wesdavisdev – sorry didn’t see this – not patroling the forums here too often.

Regarding your question, yeah, all our fields have unique classes so can be targetted individually for any custom css – this is the default way to use the pro plugin at the moment (with the actual design / WYSIWYG controls coming in version 3, for those that don’t want to / can’t code).

Thanks

• This reply was modified 4 years, 4 months ago by Code Amp.

Hey @sarju747 + @imavexadmin

I have a beta ready with this fix ready to go – https://customlayouts.com/documentation/beta/

Can you test it and let me know if it solves your issues?

Thanks

Thanks for the detailed video!

I will do some testing on this tomorrow and let you know what I find.

Hi @imavexadmin

Before we continue, let me just make sure I’ve got this right – it sounds like (correct me where I’m wrong):

– The admin area works, and you can change the restricted taxonomies
– You can save the admin layout, BUT the taxonomies you chose have been cleared when the page reloads (after the save)
– And, the frontend (the link you provided) does not apply the taxonomy restriction?

Thanks

Hey @ventilator

Right now there isn’t an easy way to do this – we have a bit of complicated setup so we can load SVGs optimally – essentially we register (while a page is loading) different SVGs we use via xlink:href, and then before the closing body tag we outout those SVGs via PHP – this ensures no SVG is loaded more thank once, and keeps the page size down too.

If you wanted to hack at it, the easiest thing to do would be to replace the SVG in our plugin, but as you mention that’s generally not advisable.

We do plan to an option so you can choose an image from your gallery as the placeholder image, but thats not coming for some time.

* I do have another idea, we have some PHP hooks, so you can filter the output of any of our elements – including the featured image.

You could conditionally check for the existance of the image placeholder in the content, and replace the html with your own:
https://customlayouts.com/documentation/action-filter-reference/

You would need one called custom-layouts/element/render_output:

add_filter( 'custom-layouts/element/render_output', 'cl_element_render_output', 10, 2 );

I hope that might help until we add this feature!

Thanks
– Ross

• This reply was modified 4 years, 4 months ago by Code Amp.