search

40fingers / StyleHelper-Sko

Manipulate DNNCMS HTML, JS and CSS in #dnncms
https://www.40fingers.net/Products/DNN-Stylehelper
7 stars 2 forks source link

default.css not removed on portal/0 #34

Closed leedavi closed 1 year ago

leedavi commented 1 year ago

We've added a rule to remove the default.css from the website when no users are logged in.

This works ok for all portals, but portal/0 still does not display the default.css when the superuser is logged in.

However, If a normal user logs in with a normal roles, the default.css is injected, like expected.

We have never noticed this before, we are running DNN9.11.

We also do not have a SSL cert, on portal/0. (not for public viewing) We thought this may be causing the problem.

Timo-Breumelhof commented 1 year ago

And you are using version 02.15.03 right? Are you saying this is only an issue on Portal 0 or did you just notice it on Portal 0?

leedavi commented 1 year ago

I was told it's the latest version... not checked that.
Yes, this only effected portal/0 and only the SuperUser. It's not a showstopper, but very odd. Maybe there is something wrong with our installation.

leedavi commented 1 year ago

This was a installation with about 5 websites on it, all worked apart from portal/0 with the SuperUser.

Timo-Breumelhof commented 1 year ago

Can you post what you added to the skin?

Timo-Breumelhof commented 1 year ago

As an FYI, if you want to check for Superusers you need to use IfRole="SuperUsers" as the role. When you create a portal as a superuser, it can be that the Host is also in the Administrator role, which could cause the difference between portal 0 and the rest of the Portals?

leedavi commented 1 year ago

We use IfRole="None"

As for portal/0 I "think" we usually make all portals have the host as Administrator. I cannot think of any reason SuperUser should be different on portal/0, but there is obviously something different.

leedavi commented 1 year ago

I'll close this, because I don't think we should waste time on it. We have a work around. But I thought I would mention it for someone else finding the problem.

Timo-Breumelhof commented 1 year ago

Actually I see now that "none" can also match a Superuser as depending on the way the portal was created a Host can be in no roles. Not very logical and there's code to "fake the Superuser" role, but I'll change the order as the check for None is before that..

leedavi commented 1 year ago

OK, thx. Let us know when you've done it and we'll test it for you.