Camilla_Nielsen

Solution (if anyone is curious): @tuanphan was able to fix up a CSS code, that hides a section based on whether a user is logged in or not header#header:has(span.unauth) + #page section[data-section-id="65819dc08e4e16377d8cb3a0"] { display: none; } change span.unauth depending on criteria - unauth = not logged in - auth = logged in change section-ID with the correct ID

Hi, I know this only accounts for some of what you are looking for, but we got this code to work so our logo changes depending on the theme color of the header. It's only CSS, we are not using any code injection. //* CHANGE LOGO DEPENDING ON THEME *// [data-header-theme=""],.bright,.dark, .darkest, .black { &.header .header-title-logo a { content: url('INSERT IMAGE URL'); block-size: 50px; } &.header .header-mobile-logo a { content: url('INSERT IMAGE URL'); block-size: 30px; } } The "block-size" is to force the new logo to a certain size so it matches the original. Hope this can help you 🙂

I would love to see an option of adding two (or several) different logos to the menu that you set up to change depending on your color theme on the different pages: One logo for light backgrounds and one for dark background e.g. 🙂 Our logo is either dark blue or white, but some of our pages are a light grey and some are darker blue, so one logo doesn't work for the entire website.

I am trying to figure out how to best get our members to the correct landing page after logging in to our Member site or at least make them see the correct content. What we have done/tried so far: Making a "teaser site" publicly available, so everyone visiting can get a taste of the content on our Member site. After login in, members ended up on the wrong landing page or on this "teaser site" instead of the correct Member site frontpage (it looks the same but doesn't have the red text "login disclaimer" at the top). We then used this code injection to redirect members after login to the correct frontpage. That all worked well until now... New Problem: We send out newsletters with links to our Member site, but because they have to login before being able to read the new content, and because of code inject listed above, they now end on the Member site frontpage instead of the site they wanted to see/read. And several people are annoyed but this... I have now removed the code injection so the members land on the correct page linked from the newsletter after logging in. But now they don't land on the Member site frontpage after logging in from anywhere else... Questions/ideas: Is is possible to manipulate in greater detail which pages members land on after logging in depending on the circumstances? (e.g. "if login in via links land on those linked pages", and "if logging in from our websites homepage, land here instead") And if that isn't possible or way too complicated, then Is it possible to hide a section under certain circumstances? – E.g. can I have the "login disclaimer" on the "teaser site" visible when not logged in, but disappear when logged in, so the "login disclaimer" isn't an eyesore and confusing. Any other suggestions on how to solve this smoothly? 🙂 Thanks!