Ad

Ok, it is solved.
Visibility Conditions returned with upgrade from 6.5.5 to 6.6.1…..

I most likely do not exceed the limits, afaik.
Did you try it with zero credits in your account?

I tested mine with the default 2024 theme and all other plugins deactivated, a new Openrouter.ai API key and Gemma 7B (free) selected.
Express mode, AI forms, Prompt base etc work without error. There are no errors in debug.log or ai power log.

I noticed that the Custom Mode Default Template parameters (AI Power -> Content Writer -> Custom Mode -> Parameters) do not reflect the general settings (AI Power -> Settings -> AI Engine -> Provider / other). Is that as intended or could it be that some settings are not synced?
I have to set all parameters each time I go to Custom Mode or choose to save them as a Custom Template. Settings: Openrouter, Gemma 7B (free), Temp 0.7, max length 3000, Freq/Pres Penalty/Top P 0.1, Topic: ‘Sports’. Question: ‘suggest (3) titles’.

BTW, I also installed and tested the plugin at: https://playground.wordpress.net/?networking=yes . That gave me another (I suppose unrelated) error:
“The model predicted a completion that begins with a stop sequence, resulting in no output. Consider adjusting your prompt or stop sequences.”

Sorry Paolo, I didn’t notice your reply.

The CSS works. Many thanks.
I need it mainly or the account page, so I’ll use
.uwp-account-form label.sr-only.form-label { … }

I agree, placeholders are nice and clean. But once people enter information in this field, they can’t see what is supposed to go there. On the account page that could be troublesome.

So I’ll use the CSS you provided (or maybe the field description). It seems more intuitive if the UWP formbuilder could decide. But I’m totally fine with the CSS solution provided.

Perfect! Thank you for your answer and pushing this theme so hard.

I looked at the pics and noticed that I was missing all the options underneath ‘Background’ and even the tab ‘Advanced’.

I found a conflict with Loco Translate and BlockStrap Page Builder Blocks. There is no problem when creating a new language .pot/.po, however when I translate the words ‘Background’ or ‘Wrapper Styles’ (or ..) the tabs or options of the block disappear. That’s why I could not find the option to change the background image.

I’ll deactivate translation for now.

“Regarding the error you mentioned, that’s because you’ve disabled some fields and those fields are required by your payment gateway provider.”

IMO, that’s seems unlikely. The payment provider has a fallback mechanism. That is why Cartflows free works as expected.

However, if Cartflow pro is enabled the mechanism breaks; that’s a WordPress plugin conflict. I hope you’ll bring it to the attention of your developers.

For me (Mollie users) it seems better to stick with Cartflows free for now until Cartflows pro gets fixed.

Thanks for all of your time.

I think I found the culprit. It is Cartflows Pro.
Unless of course, it is intended behaviour without error handling.

With Cartflows Free: Create a CF sequence with just email/firstname fields: optin -> checkout -> Thank you. This works with Mollie.

With Cartflows Pro: at the moment you activate the plugin it breaks the Mollie connection/fallback mechanism.
Once address fields are added to the CF Checkout it works again, afaik.

Can you confirm this?

Thank you, I’ve seen the supported gateways.
Ideal is supported.
Sepa is not supported.

For recurrent payment Ideal payment can be used for Sepa (as explained in the other link). Are you confirming that Cartflows supports Mollie Sepa payments through one-time payment with Ideal?

BTW I’m struggling with Ideal also, because testpayments fail with the following: “DEBUG Creating payment object: type Order, first try failed:” “Error executing API call (422: Unprocessable Entity): The following fields of the billingAddress are missing: streetAndNumber, postalCode, city, country.” While I would think email and name should be sufficient for one time payment.

FYI: https://docs.mollie.com/payments/recurring
Not sure if Cartflows follows these steps or will or could.

The next link maybe helpful to understand the question better. It is a similar question, although for a different funnelbuilder, but a more clear explanation:

https://www.ads-software.com/support/topic/ideal-bancontact-mandate-with-sepa-direct-debit-payments-for-subscriptions/

Is there working solution for Cartflows?

Thank you. The question was about protecting slugs with its childpages, not about creating member directory (though the shortcodes were new to me). I’m looking at protecting slugs like:
/members/*
/events/*
/jobs/*
/groups/*
et cetera.

I’ve created a ticket as a pre-sales question and got the following reply:

“Great question! It’s not a default option to grant access to complete directories using WooCommerce Memberships however, it may be possible with the help of some customization to get this working.”

In other words: it is not supported by default, but a developer could create it.

Oké. It looks like it’s solved. Thank you.

Thank you. After adding the $user_id that worked!