Skip to content

Michael

My feedback

1 result found

  1. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  Wishlist » Widgets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Michael commented  · 

    Hello Oleg, it looks like this was not fixed in the 7.26 release. I would like to suggest that users who are running into third-party cookie issues consider running Wild Apricot as a subdomain of their primary domain, as that seems to fix the issue. For example if your website is mydomain.org, then set the WA primary domain to members.mydomain.org, and use this domain for all of your iframes. This seems to have fixed the issue for us.

    An error occurred while saving the comment
    Michael commented  · 

    Hello Oleg, regarding the third-party cookie issue... we were wondering if you could confirm that this should work for our client. We're in the process of testing it, but it may take a few days for the client to get us the necessary DNS information.

    We will be serving the client's WordPress site from clientname.org. We manage the client's DNS and plan to create a new subdomain; members.clientname.org. We will set this as the default subdomain in Wild Apricot. The iframe widgets and the cookies should then be coming from the subdomain, which is on the same primary domain as the WordPress site.

    This _should_ solve the issue with third-party cookies, right?

Feedback and Knowledge Base