Code Amp

Hey @vgsvenice

Sorry to hear you’ve had such a negative experience…

The pro version adds some extra features (which bring technical challenges) because it support things like custom fields, ajax searching, DB optimized queries + cache and more.

However I realise you’ve had pain points with the plugin, and we’re already (2+ years in the making) working on addressing the UI to make it easier and more intuitive to use.

Not only that, we’re also adding the features you mentioned, so you’ll be able to change color schemes of your fields using a visual editor we’re building (+ more design options such as spacing, border, padding and fonts will follow later in the year).

Thanks for your feedback, I do hope you’ll give us another go in the future.

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

Thanks for the review @tylertork – hopefully in a few months (after a big update we’re working towards) we’ll get to add this in.

Ahhh John! yes I should have known better..! Thanks for those reviews it means a lot 🙂

Regarding the above filter, it still works with Gutenberg and blocks, its just they don’t get a Layout ID passed down as the second parameter.

So you couldn’t apply the conditions based on ID, like this line:

if ( absint( $layout_id ) === 123 ) {

Instead you could test against the current post / page or another wordpress conditional tag – eg:

if ( is_page( 'contact' ) ) {

More info on conditional tags: https://codex.ww.wp.xz.cn/Conditional_Tags

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

Hey @tylertork

Thanks for the feedback!

Regarding your requests:

1. Use the background of the page – this is already possible 🙂 See this gif I just made so you can see which setting to change:
https://drive.google.com/file/d/1ZhY-u6hB-pb0N6FDXJAij2C13EDkd9Gh/view?usp=sharing

2. You’re right on this – we should add an option to hide the image completely if no image is found – I’ll put that on the todo list!

We already have on the roadmap to add the ability to set a custom image.

Regarding the number requests, there should hopefully only be one extra – for our placeholder SVG – not ideal, but hopefully not too taxing.

All the best
– Ross

Hey John

As I now know you are not using the block editor, then you can modify it like this:

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

function layout_query_args_15156524( $query_args, $layout_id ) {
	if ( absint( $layout_id ) === 123 ) {
		$query_args['post__in'] = array( 1, 2, 3, 4, 5 );
	}
	return $query_args;
}

In this example, you would change 123 for the layout ID you do want to be affected (when you edit a layout, you can find the ID in the address bar).

Let me know how you get on with that?

Thanks

—-

BTW, if you feel like leaving a review it would be appreciated – https://ww.wp.xz.cn/support/plugin/custom-layouts/reviews/ 😀

Ahhh ok, then I think what you’ll need to do is, enable the featured image, position it to top (and remove the background image).

Then you should get what I’m experiencing.

You can even make the margin more negative so that the featured image “feels” like a background image.

Does that make sense?

Hey again @dsl225

Yeah I think you can do this.

To explain a little bit about the structure of our templates at the moment:

1. Everything is contained in an ourter container, the Template.
2. If you have the featured image enabled, you then have two containers – featured media, and section
3. Inside the section, are where all your other elements appear when you add them / drag them on to the template

So, what you want to do is:
1. Carefully select section
2. Edit the margins to add spacing to the side
3. Add negative margin to the top

Heres a little GIF I made of the process: https://drive.google.com/file/d/1fD2NnDeX_hSz_1Np76vakiPZO-1MLkCb/view?usp=sharing

I actually thought you would have to do this with CSS + custom classes, but it looks like the negative margin in our UI works just fine!

Let me know if that works out ok for you.

Best

Hey @sinnamon

That sounds odd indeed.

From what I can tell, nothing regarding our custom field element was changed in our recent updates – so it does sound odd its not working – but maybe a change has eluded me.

To get to the bottom of this can you confirm a couple of things?

1. Edit the yoga posts in question and double check the custom field is there with a value

2. Double check the custom field key – if you are using ACF to create custom fields, then this uses 3 keys for any custom field:

_my_custom_field
my_custom_field
field_123456

What you would need is the second version, without the underscore: my_custom_field – but its possible you’re not using ACF

3. Can you share a link to the page in question?

Thanks