Marisa

But people from the CITY = London are always the first search results shown.

Even when I specify

COUNTRY = United Kingdom

Region = England

CIty = London

I get people from the region England, but from cities other than London.

There are so many different ways to do things in WooCommerce.

For example, you can get WooCommerce to handle a credit/debit card payment via Stripe directly and it sets up some sort of new Stripe account for you itself.

Or you can get WooCommerce to connect to an existing Stripe account.

So what I want to know is this a problem of my WooCommerce settings or do you always have to manually set a user as PAID after a WooCommerce payment?

Thank you. I’m sure anybody in New York or San Franciso will thank you one day. Or even High Wycombe for those not in the USA.

Thank you.

This is a very low priority issue. I have found a workaround.

I have found a workaround for this. This is a very low priority issue.

Thank you for creating this software.

If it helps, I have the option “Custom->Features->Allow multi choice in relation and sex” selected (checked).

OK. The problem is that is array of replacements for the city entered for searching just misses out ‘ ‘ for the list of things to replace by the empty string ”. I’ve only rushing looking at this, but it looks like the problem can be fixed easily.

If someone enters New York as their city, it cannot be found be searching for New York.

It can be found be searching for NewYork.

Therefore the city in the MySQL database is stripped of internal spaces before being compared with the string entered by search which is not stripped of spaces.

So we need things to be equally stripped of internal white spaces.

I think. I’ve only done very quick testing.

Thank you very much for this information and responding so quickly.

Thank you very much for this information and responding so quickly.

Final Post

So long as the right cookie is set, everything seems to work. Rencontre is perfect the way it is! Sorry for the initial post.

OK, search does work for a custom profile item/value. But I had to go into the users’ profiles again and re-save the My Portrait/My Search fields. Possibly the profile are somehow saved to the database in a language dependent way, but I don’t know as I’ve only done quick testing.

The problem is Rencontre reads the value of the lang cookie to work out what to display for the My Portrait language. The PolyLang language switcher does not set the value of the lang cookie. So I set the lang cookie to fr-FR and My Portrait switches. However this does not fix the problem, because the full Search functionality does not work when I try to search on the new custom Profile item/value I added. Search did work before I set the lang cookie.

• This reply was modified 1 year, 7 months ago by Marisa.