buzut

This makes sense. I have just made a real payment, will keep you posted if anything.

I’ve leaved a positive review, hope it helps out.

Best,
Quentin

Hello @mrclayton

Sorry for my late answer, I was waiting to test it out before getting back to you!

First of all, thank for this incredible plugin and you for considering my request (it’s a huge plus for B2B, even more so as browsers don’t have an autofill feature for IBAN).

I can definitely see the save button when I enter the IBAN on checkout, but then it doesn’t appear in the saved payment methods. Is there something that I’m missing?

In any case I’m leaving a positive review right now as you guys deserve it ??

Thank you for getting back to me! Can’t wait this option, especially since no-one remembers their IBAN and browsers don’t support autofill for that ??

It is very useful for bigger amounts of B2B orders.

Kind regards

Hi Hannah,

Yes I know I can use custom ones if needed. But I think it would be a great addition given the recent rise of Tiktok.

Keep me posted ??

Best,
Quentin

Merci pour votre réponse rapide !
Le plugin Colissimo est encore jeune donc c’est normal qu’il ait certains soucis de maturité.

Le fait que La Poste soit derrière donne confiance tandis que CDI ne semble développé que par une seule personne… C’est de ce fait le support à long terme que je considère.

Je vais donc tester et me faire mon avis. Merci encore ??

Bonjour,

J’utilise pour le moment SendCloud et j’avoue hésiter à migrer vers CDI ou le plugin Colissimo officiel.

Est-ce que vous pourriez détailler en quoi CDI est mieux ? Il semble qu’il faille un abonnement en plus pour profiter de toutes les fonctionnalités.

My bad mate.

Thanks for this awesome plugin. Trying to help a bit with the translations ??

Thanks mate ??

It sure works and I understand you can’t break backwards compatibility.

Just had a look at the code, love how clean it is (not always the case in WP plugins sadly), good work man!

Also, while maintaining backwards compatibility, couldn’t you just check for filters, if some are hooked, don’t change anything. If none are hooked and WP_CONTENT_DIR is declared, you can safely take the constant into consideration.

Checking for filters is as simple as looking into $wp_filter['my_hook'].

Cheers,
Quentin

Sure, in my case, the uploads lies at the root, so:

define('WP_HOME', 'https://my-web-site.com');
define('WP_CONTENT_DIR', __DIR__);
define('WP_CONTENT_URL', WP_HOME);

In this case, __DIR__ translates to /home/alphapole/public/

https://ibb.co/7pDTcHL

• This reply was modified 3 years, 9 months ago by buzut.
• This reply was modified 3 years, 9 months ago by buzut.

I haven’t tried yet. I was waiting for your answer actually.

My assumption is that if someone uses such constants, it means that they have more knowledge and can use plugin filters.

That is true, it’s pretty easy to use filters, but imagine if each plugin needed its own filters when deriving from standard install…

I don’t know what someone can enter there and at this point there is a risk that it will not work or it will work wrong

If wrong data is entered, apart from your plugin, that would be the whole WP install that would behave in a weird way or just break.
You could just check whether the directory exists, and if it does, assume it’s all good.

It’s actually a usual way of doing things when using WordPress as a framework and managing dependencies with composer (wordplate, bedrock…).

I’m developing a starter theme based on these concepts: https://github.com/Buzut/steroids

Best,
Quentin

• This reply was modified 3 years, 9 months ago by buzut.

Hi Mateusz,

Sure I saw there’s a filter.

Nevertheless, I think that in addition, it’s a good practice to take into account default configuration constants.

Don’t you agree?

Best,
Quentin

• This reply was modified 3 years, 9 months ago by buzut.
• This reply was modified 3 years, 9 months ago by buzut.

Thank you for your answer!
So this isn’t possible without custom code. I’ll see how I tackle that.

Thank you for your answer, this aims specifically at default ordering options. It seems like if I really need to set a custom ordering by category, I’ll have to go down the route of creating an ordering attribute by category and then using a custom WC_Query.

Hey, thank you for pointing that out!
Unfortunately, it doesn’t work for me (cf screen).

The main screen is kinda split and the custom fields aren’t modified. I had no errors in the console.