curve

Thanks @collizo4sky, but even after deleting cookies the cookie is still set. I’ve tried both adding the filter using code snippets, and adding it as the first line in functions.php. Neither route works.

• This reply was modified 2 years, 8 months ago by curve.

I have the same issue. I tried adding the code above into Code Snippets, but when the snippet is activated, the cookie is still set.

I couldn’t see an option in the plugin settings to turn off the cookie.

Please let me know what I should try next.

Thanks Marko, I’ve enabled those and no change. This forum is a bit public for sharing the URL.

Should this setting work on lighttpd?

Posting in case this solves for other posters. Had to remove cookie-law-info-public.js from my CDN to stop this error.

Posting an update in case anyone else has the same issue – looks like the problem was upstream domain config rather than anything to do with the plugin!

Once we’ve fixed that I don’t know if the UI issues would cause further problems, we’ve made some changes in the server lighttpd.conf file in the initial effort to solve this…

Hi @johnny5, I’m still having issues with this.

The server I have everything working on is running apache, whilst the server with issues is running on nginx. I’m not sure if its relevant, but the domain name begins with a number, which seems to cause issues with the UI as you can see on this screenshot – I don’t know if this is involved in the issue.

On the apache site the following redirect correctly to https://www.domain/trailingURL:

https://domain/trailingURL
https://www.domain/trailingURL
https://domain/trailingURL

On the nginx site, the following happens:

https://www.domain/trailingURL correctly redirects to https://www.domain/trailingURL

https://domain/trailingURL and https://domain/trailingURL both have the trailingURL stripped and are redirected to https://www.domain/

Please let me know how I can troubleshoot the issue.

Hmmm, thanks @johnny5. This lead me to try to recreate on a dev server and it works as intended. I think I may have a misbehaving production config. I’ll update this post if relevant.

Me too

Hi @wpinsider-1, I’m needing to implement a solution to this issue too. How is the coding work going – and thanks for your work!

I’m using the ‘Post – New Comment Awaiting Moderation’ notification type.

Ooops, found out this was actually to do with some non-related code rather than the WP update. I therefore recommend checking that you don’t have any javascript errors on your page because that’s what broke it for me!

Yep, me too. Any idea how to fix?

Actually, it looks like this is with all images…

I have this issue too. It seems that

div.wpcf7-response-output {display: inline-block;}

is overriding

.wpcf7-display-none {display: none;}

Sure, changing to the default theme solves the issue, but obviously that’s not a fix…

Worked it out – it was a memory issue. If others are having the same problem, try define(‘WP_MEMORY_LIMIT’, ‘256M’); or something similar in wp-config.php

• This reply was modified 7 years ago by curve.