Conversation
supportHi It looks that my login screen layout is suddenly broken. Might this have something to do with incompatibilities of Erident Custom Login and Dashboard with WordPress 5? Kind regards, Richard The page I need help with: [ log in to see the link]
Hey, As far as I know, there are no conflicts with WordPress 5. Can you check by disabling other plugins? If it is still not solving please give me admin access and I’ll debug it for you.
After I upgraded to WP 5 a PRIVACY link appeared below my login panel. https://aspacinvestor.com/wp-login.php I am assuming that this relates to the most recent WP upgrade. If not, how do I hide this link? Kind regards Alistair This reply was modified 7 years, 5 months ago by zelacorp .
I have since solved the issue I flagged above … I simply hid the PRIVACY page … making it only visible to ADMINS. Regards Alistair
Hey Alistair, I’m not seeing any privacy link in your login page. And I’m not aware of any privacy link adding to the wp-login page by WordPress. It may be coming from some extension you have installed in the browser. Check the page in incognito mode. If it still appears, can you show me a screenshot?
Oh cool. Glad you solved it.
@libinvbabu Sorry to come back to you after some time. I haven’t had the time to dive deep into it. Thank you for the offer you are willing to look into it when I give you admin-access. The website is not owned by me. Therefor I’m a little reserved to do that. If you don’t mind I’ll postpone this opportunity for later. I did some other quick checks. I duplicated the whole website to my nas to find out is the issue remains and give me the opportunity to ‘ruin’ the website offline. Unfortunately there it works as designed. I meanwhile think it is probably not related to Custom Login. The debugging gives me a “Resource interpreted as Stylesheet but transferred with MIME type text/html:” error. This is a more generic error I have to sort out first. After that I’ll have to see if my problem with Custom Login still exists. (It worked before.)
Hi @wijngaardr , Glad that you are digging the exact problem. “Resource interpreted as Stylesheet but transferred with MIME type text/html:” error usually comes when you give a relative path in a local setup. Giving an absolute path to the CSS file might fix this error.
Hey, As far as I know, there are no conflicts with WordPress 5. Can you check by disabling other plugins? If it is still not solving please give me admin access and I’ll debug it for you.
After I upgraded to WP 5 a PRIVACY link appeared below my login panel. https://aspacinvestor.com/wp-login.php I am assuming that this relates to the most recent WP upgrade. If not, how do I hide this link? Kind regards Alistair This reply was modified 7 years, 5 months ago by zelacorp .
I have since solved the issue I flagged above … I simply hid the PRIVACY page … making it only visible to ADMINS. Regards Alistair
Hey Alistair, I’m not seeing any privacy link in your login page. And I’m not aware of any privacy link adding to the wp-login page by WordPress. It may be coming from some extension you have installed in the browser. Check the page in incognito mode. If it still appears, can you show me a screenshot?
Oh cool. Glad you solved it.
@libinvbabu Sorry to come back to you after some time. I haven’t had the time to dive deep into it. Thank you for the offer you are willing to look into it when I give you admin-access. The website is not owned by me. Therefor I’m a little reserved to do that. If you don’t mind I’ll postpone this opportunity for later. I did some other quick checks. I duplicated the whole website to my nas to find out is the issue remains and give me the opportunity to ‘ruin’ the website offline. Unfortunately there it works as designed. I meanwhile think it is probably not related to Custom Login. The debugging gives me a “Resource interpreted as Stylesheet but transferred with MIME type text/html:” error. This is a more generic error I have to sort out first. After that I’ll have to see if my problem with Custom Login still exists. (It worked before.)
Hi @wijngaardr , Glad that you are digging the exact problem. “Resource interpreted as Stylesheet but transferred with MIME type text/html:” error usually comes when you give a relative path in a local setup. Giving an absolute path to the CSS file might fix this error.