chriswww

Thanks for your reply, @shresthauzwa! Two other plugins also did not work well, so I made a backup of the site, deleted everything and reinstalled with fresh database. User Registration is working fine now ??

The problem has returned, too bad, I guess I’ll have to try another registration plugin.

• This reply was modified 2 years ago by chriswww.

Thanks, @shresthauzwa, working now. Must have been a conflict, but I don’t know with what. I modified a lot with deactivating other plugins, cleaning database, PHP version and suddenly it worked.

Kind regards
Chris

Okay, I will check this with the provider.

Thank you very much for your support, Roland!

Many thanks for your reply, Roland! It’s really strange.

On customers server it’s like this:
– “Use Alternate Session Method”: checked automatically, noch chance to uncheck
– Cookie “pdb-sess” can be seen in Chrome DevTools on all pages of the website

On staging server:
– “Use Alternate Session Method”: unchecked
– No Cookie “pdb-sess” can be seen, also not on PD pages

Additional info: I’m using PD with addons PD Combo Search and PD Pretty Permalinks.

Also had a look at session related server configuration with PHPInfo and the main info section shows this differences:
“session.gc_probability” on live server: 0
“session.gc_probability” on staging server: 1
“session.cookie_httponly” on live server: no value
“session.cookie_httponly” on staging server: 0

Can you help?

Stupid question, simple answer :-)))
Venues have to be created before making a new event. This way also a room number can be used and assigned with the selection bar.

Thank you, Ethan!
Yes, that helps … a little bit ??
For just saying “Thank you!” I usually don’t make an extra page. Having this message in the lightbox I consider as much more elegant. But that would need some ajax magic, right?
Anyway, I will use it with a confirmation page. A lot of fun working with Wpforms on the whole!

Perhaps something in the functions.php? I had to remove an obsolete filter “add_filter(‘relevanssi_modify_wp_query’, ‘rlv_remove_polylang’)” that I needed a long time ago.

Working fine now with 4.0! Thank you very much, Mikko!
Best,
Chris

Yes, using the latest version. Will perhaps the mentioned modifications in version 4.0 solve this issue?

A pity, can’t find a solution to fix it. When I deactivate Relevanssi, restriction is made correctly by Polylang. When 3.6.2 is activated again, also the restriction has gone again. So I hope version 3.6.1 will work as long as possible in future WP versions.

Mikko, just tested more old versions and noticed, that Relevanssi lost the language restriction with version 3.6.2, v. 3.6.1 is doing it well.

Many thanks for your reply, Mikko! Just wonder, why the restriction is working well with Relevanssi 3.5.8, but not with 3.6.2.2. Seems like changes in the update cause this, doesn’t it?