HelgaTheViking

FYI – this can be resolved by declaring the core property in the Alg_WC_Admin_Bar_Addition main class like so:

/**
 * Core class
 * @var Alg_WC_Admin_Bar_Addition_Core
 * 
 * @since 1.4.0
 */
public $core = null;

PR sent

• This reply was modified 8 months ago by HelgaTheViking.

thank you Sayf! Let me know if there’s anything you think is missing

• This reply was modified 8 months ago by HelgaTheViking.

The tested version will get bumped when the new release is shipped. Just ironing out a little additional documentation to explain how best to use it in the Site Editor. I actually find the block sorta confusing in the Post Editor.. but feel the same about the WordPress core Post Title block.

What kinda settings would you want to see added? I was thinking one setting might be to auto display… it’s not ideal for HTML markup but you can filter in the subtitle value automatically into the post_title filter.

Well now you got me thinking…. so today I built a subtitle block. It should be fairly handy in the Site Editor. If you have time to test it out I would appreciate it: https://github.com/helgatheviking/KIA-Subtitle/releases/tag/4.0.0-beta.1

Hi there… I’m glad you like it. I will try to remember to update the tested WordPress version in the readme. But if it works there’s nothing else to really update.

The plugin doesn’t handle any styles… that’s all left to you. If you want to serve different styles to different devices you need to write what’s called a CSS media query.

As an example, the following sets the subtitle class size to .75rem. But then any device wider than 300px (so everything but mobile) will have a size of 1.5rem.

.subtitle {
	font-size: .75rem;
}

@media (min-width: 300px) {
	.subtitle {
		font-size: 1.5rem;
	}
}
  

You should be able to get pretty custom this way. You can read more about media queries in the documentation.

My plugin supports anything WP_User_Query can query for.

Presumably a multi check is saving an array of values which would then be serialized in the database. You could probably work something up with some custom code, as you can get quite advanced by filtering the different WordPress SQL clauses.

but I believe it would always have to be a fuzzy and therefore inefficient search.

Sounds like you need to add compatibility for the block checkout and at a minimum declare support.

Take a look at how the Dummy Gateway has added support. Maybe Roxy can link you to appropriate woo docu… I couldn’t find anything on first search.

Hi @drowranger any chance you were able to make that screenshot?

is something not working?

i updated the tested version at GitHub but it didn’t deploy properly. I’m working on an RTL display fix at the moment and when that’s done will be updated with the bumped tested version as well.

locally the radios are correctly lined up with their labels, so I’ll need to see you’re screenshot with notes to understand better.

Would y’all please give this version a trial and let me know if it solves the RTL problems. It is a beta (And I also tweaked my build scripts) so please test locally if you can.

https://we.tl/t-6ZkTl9JVq0

• This reply was modified 9 months, 3 weeks ago by HelgaTheViking.

@drowranger thanks for your patience. I think I finally see the problem…. in RTL, the labels are somehow misaligned from their buttons. Here’s what I experienced in my test:

And I can see that finally in your screenshot… the LTR your display mode is “Show” and in rtl it looks like “Hide”. Underneath I think the value is still correct, but I see how that’s very confusing.

Now that I have a better idea I can look into it more.

i apologize, but I’m not sure what you mean by “fix” in this case. Could you try explaining a different way? Could you draw on the screenshot where you think the radio should be?

hi, thanks for reporting. I’m not entirely certain what the problem is. What are the radios doing versus what you expect?

Not the author, but this plugin should be entirely front-end. It doesn’t interact with Orders as far as I remember, so I am fairly certain you can use it with HPOS enabled. You should test in staging to confirm.

It would be nice if they added the explicit declaration though so Woo doesn’t keep showing the notice.