- 🇯🇴Jordan omar alahmed Jordan
If your site is hosted on platform.sh then make sure to allow the bakery's cookie names → in the platform.sh routes.
I have a domain based VPS server, using wildcard DNS and responding on Apache virtual servers foo.com, one.foo.com, two.foo.com, etc... Settings for cookie_domain is '.foo.com' . Users can login on any subdomain and then hop through all subdomains. Login on foo.com is prevented in httpd conf.
I have now set up a plain D6 installation on a separate VPS (responding on alfa.foo.com) the idea being that the first server could be used as bakery master. However as soon as I enable the bakery module on the first server, user's can't login anymore and the watchdog logs the following error. Is that the result of the page caching bug?
Type bakery
User test
Location ://one.foo.com/frontpage?no_cache=1260778728
Referrer ://one.foo.com/?no_cache=1260778728
Message Logging out the user with the bad cookie.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
If your site is hosted on platform.sh then make sure to allow the bakery's cookie names → in the platform.sh routes.