shrumdidly

Ok I turned it off, and will see how it goes. Thank you.

After some emails back and forth with the support team, I have realized that if there is no trading pair for the token on Binance.com then the autosettlement will not work, and the tokens will just stay in the wallet.

My project is focused on the BSC and BEP-20 tokens which have new projects coming out everyday.

It would be nice to have an autosettlement feature with Metamask that autosettles to BUSD.

As we move into more of a cross-chain ecosystem with many different cryptocurrencies and the popularity of decentralized finance (DeFi) getting more and more popular, autosettling to Metamask makes more sense imho.

MyCryptoCheckout payment ID: 230533
MyCryptoCheckout payment ID: 230540
MyCryptoCheckout payment ID: 230505

All three of these didn’t work automatically, but I’m leaning towards this being an issue with congestion on the BSC and gas fees needing to be higher to get transactions through.

I have updated the plugin to Version 2.93 and I will do another test.

The token I’ve been testing with is $CAKE.

Something must have changed because today the gas price defaults to 20 and the gas limit defaults to 450,000 when I pay.

The transaction is going through now, but the green check mark does not show up to verify the transaction with MCC.

Ok, just setup credentials and emailed you.

Ok I see multiselect for front end now. The only problem I foresee with changing from an attribute to term is it will affect my property feed elements. I would prefer to use the attribute instead of term. I will mark this resolved after the next update corrects the import multi-select attribute behavior.

@maxim I thought to use terms, but there is no way to do a multi-select search on terms on the front end. There is only the dropdown single select option with terms.

**I noticed on the All Apartments page in backend there is a way to choose multiple terms, but there is no equivalent for front end on website.

I’m using the field for bedrooms: Studio,1,2,3,4. I will need to allow the visitor to search 2 AND/OR 3 AND/OR 4, Studio AND/OR 1, etc.

Here’s what I’m thinking… If I change the Search Input and Data Entry to Free Text for this field it will import correctly. But, searching forces the user to type free text on front end which is not ideal. Should I do this for now, and when you push the update to fix multi-select I can change the search input from Free Text to Multi-Checkbox for this field or will that not work like I’m thinking?

Let me know.

I was giving you more info about the TRUE/FALSE, Yes/No, and 1/0 after more testing on my end.

Also, I wanted wordpress community members to know about the issue in case anyone else is struggling with it.

Thank you Maxim. This was the fix!

Thanks Maxim. Yeah it’s definitely related to the property settings.

When I do a fresh install of wp-property locally everything works fine when adding/editing properties. It’s not until I import the wp-property settings that the php warnings start appearing.

I sent my settings file to [email protected] per your request.

Did you ever figure this out? I’m trying to do the same thing.

Is anybody out there?