New Login Screen?

[KitchM]

I am getting a different login screen than before. It shows a confusing and very busy screen with a warning up front that states:

Information

For the Admin console to work properly

1. Cookies must be enabled in your browser
2. Javascript must be enabled in your browser
3. Popup windows must be allowed for the following address:

Is that correct, of is something else wrong?

Thanks.

[staartmees]

Does it look like this? It's just information. Click on the "i" marked with the red arrow to close this information window

[KitchM]

No. It looks like the attached file.

[Jo Morg]

Judging from the scarce info you gave and from your attachment, looks like Javascript or css (or both) not being attached to the page... (or disabled from browser).

[KitchM]

That's all the information I had as well. But it didn't make sense since it was working before this happened.

I can state that I was attempting to tighten up security, and followed directions to change some things, including .htaccess. However, I believe I put it back like it was, but it didn't help. At one point, I lost all access to the server and it just came back a day ago.

I had removed all security measures and rebooted the VPS a couple times. After complaining to the hosting provider, something happened (they don't know what) and access was regained. However, this screen did not improve. It still has me baffled.

Can you describe where the need for CSS and Java comes into that display so that I might be able to track down the disconnect from that direction?

Many thanks.

[KitchM]

Does anyone have an answer as to if this problem has anything to do with .htaccess?

Thanks.

[faglork]

Try to clear the browser cache. I've seen issues like this - this may simply be a corrupted .css file. When you clear the browser cache, the .css gets loaded fresh from the server.

Cheers,
Alex

[KitchM]

Thanks very much.

I cleared the cache and it did not help. I am guessing here, but I believe that the problem is that the css is simply not connected to the admin panel code at all. Even if I use the odd login screen and ignore the message that things are not being sent in a secure manner, I still get the same bad layout for the admin panel as a whole.

I'm still confused as to what might have changed, and why.

Anyway, thanks again.

[Jo Morg]

...and ignore the message that things are not being sent in a secure manner...

What do you mean by that?

[KitchM]

A picture is worth a thousand words. Check out the attachment.

[Jo Morg]

A picture is worth a thousand words.

Actually, not this time it isn't. That just confirms (as I suspected from your previous post) that you have some mixed http and https protocols on the same page request. Most browsers don't like that. That does explain, to some extent, what you are experiencing, but...
I recently set up a site with https, without issues, so... without further info, like what steps did you take before this happened (if not you then ask who could possibly have done that), trying to help you is like a guessing game .
On my sig there is a link: Before Asking For Help! that you should read. It could spare you and us a few extra posts. Hence my previous comment about scarce info...
The more info you post, the more likely it is to have help, and better yet, to have quality help.

[KitchM]

I had assumed that one who views the screenshot would figure out that I would have had to select to continue. Therefore, it seems reasonable to expect the picture to give the answer to your question. I am sorry if that was not clear.

I do understand all the other you mentioned, and I cannot see what information I might not be supplying that will help the diagnosis. In any case, I cannot remember anything that could have happened or that I changed. And therein lies the rub.

What appears to be the problem is that people forget that sometimes there are things that happen out of any obvious sequence, making it extremely unlikely that one will be able to make any connection between cause and affect. In that case, it simply requires an expert into the inner workings of software to figure out what happened.

I won't learn to not do what I did (if I did something wrong) unless I know what I did. Nor will the problem be documented for the next person with the same problem.

Maybe that helps clarify why I must use the forum.

[Jo Morg]

Maybe that helps clarify why I must use the forum.

It's not about using the forum but how you use it. There are a few steps that people are expected to take before posting a question:

• - research to see if the issue is not more of a generic issue rather than a CMSMS specific issue;
• - search the forums for similar issues that might have been solved/answered;
• - then post your question with as much data as possible;

Some of the additional info that you need to answer:

• - Did you or anyone at any time set the config.php to make CMSMS serve admin pages via https?
• - Did you or anyone install a certificate on the server for that specific domain?
• - Are you accessing the backend through http or https?

The forum is a good place to learn, but you are expected to know the basics, and even some more advanced topics, and do some research if needed, as some of these fall out of the scope of this forum.

[KitchM]

It's not about using the forum but how you use it. There are a few steps that people are expected to take before posting a question:

• - research to see if the issue is not more of a generic issue rather than a CMSMS specific issue;
• - search the forums for similar issues that might have been solved/answered;
• - then post your question with as much data as possible;

I did all of those.

Some of the additional info that you need to answer:

• - Did you or anyone at any time set the config.php to make CMSMS serve admin pages via https?
• - Did you or anyone install a certificate on the server for that specific domain?
• - Are you accessing the backend through http or https?

1. Yes I believe so.
2. Yes.
3. Don't know how to tell.

Thanks.

[Jo Morg]

1. Yes I believe so.

Post (I shouldn't have to write this... ) your config.php being carefull to omit passwords and usernames.

3. Don't know how to tell.

Simple: in your browser instead of using http://adresstothesite.something/admin (non encripted) use https://adresstothesite.something/admin (encripted)...
Note the HTTPS on the secure address...