The responsiveness disappears when I connect my page to a new domain - responsive-design

I have just finished an education in web development. When I studied did I get repos from school but when I did my final project did I get help to do a repo from scratch in Github.
I bought a domain (.se) to my final project, but when I connected my page I got at netlify.app the pages responsiveness disappeared. The page borjebrorson.netlify.app works perfectly in laptop, tablet and mobile, but when I connect it to borjebrorson.se the responsiveness for tablet and mobile disappears.
I tried to connect another repo to my .se (a repo I got from school) and then the responsiveness did work, so it is something with my repo I did from scratch that doesn’t work. Someone said it could be something with the stylesheet, I have compared my stylesheet to the repo that did work and I can’t see what’s the different between the two pages.
I have understood that this line is important, and I do have it in the stylesheet.
Anyone that can figure out why the responsiveness disappears for me?
Link to my repo [https://github.com/LovisaBrorson/final-project]

Related

Firebase Deployment: My web appear in "project.firebaseapp.com" but not "project.web.app"

I've completely deployed my website with Firebase CLI, and project.firebaseapp.com is accessible and works fine. However, project.web.app keeps showing "Site Not Found".
I'm building my web app with React and already set the folder to "build"
Edit1: I've tried safari, chrome, incognito of both, and also hard refresh and empty cache still showing SITE NOT FOUND.
Edit2: It's working on Line Application Built-in Browser (mobile), but not on Chrome (mobile).
Edit3: Sent the domain to my friends around the world and found out that it's not working for only people living in South East Asia.
As I mentioned in comments, try any other browser. Both the domains are working on my computer. It might just take some time for both to deploy and update the cache.
It's usually better to ask someone who stays far from you and maybe has a different ISP to test update website. I sometimes use Lighthouse and it turns up even it won't show up on my computer. (Apparently the older version gets cached).
I'd recommend disabling cache from network tab in browser console when in development stage:

Can't edit certain pages on DNN site after upgrade to 9.01.01

We recently upgraded one of our client sites to 09.01.01 to address a Telerik vulnerability, and then had to migrate the site from managed.com to Azure due to manage.com's outage. After the upgrade, a couple of pages on the site have been uneditable using the pencil icon in the persona bar, although the rest work fine. We're aware of the workaround of going into content > pages and clicking the pencil icon there, but even then not all of the areas on the page are editable. For example, there's one instance of the HTML module on the homepage where when you click on its pencil and then click "Edit Content," it just displays a pop-up with the text but no WYSIWYG or way to actually edit. Other instances of the HTML module work fine, on other pages and even other areas of the homepage.
What's more bizarre is that we just spun up another Azure VM and created a dev site from a clone of the live site so we could troubleshoot further, and this problem does NOT occur on that site even though it's an exact copy of the live site files and database and both sites are hosted in Azure.
Does anyone have advice on what might be causing this or how to troubleshoot? My original though was to clone the page and start removing modules one by one to see if anything made a difference, but it doesn't actually remove the module when I click delete. I've read about ways to do this directly in the database, but I'd prefer to avoid that if possible, especially since we're not seeing the same problem on the cloned site.
Thank you!
Could you please see if any error appearing on the logs folder? You can see the logs here. /Portals/_default/logs/2021.02.01.log.resources? The log file name may differ based on website's logging configuration.
A similar thing can be seen from the Personal bar as well using Admin Logs.

After i create a APK to PWA i see toolbar of browser

I have a problem with my first PWA.
I have created one with reactjs and configured good manifest.
I follow step by step google guide.
PWA, works perfectly, and i see "add to home button".
After QA i wanted to publish it in store.
I used https://appmaker.xyz/pwa-to-apk.
Now i have app publish in the store but when i open it, i see a browser toolbar and i can't use it as a native app.
Someone can help me?
How about using TWA (Trusted Web Activity)?
Using Trusted Web Activities
This can be achieved by proving that the app and the web trust each other.
If you can prove it, you can prevent the browser toolbar from being displayed.
I'm sorry if you don't get the answer you want.

Need guidance in debugging this DNN issue

I'm a beginner with DotNetNuke and am having trouble debugging this problem. We are using DNN version 5.
On our local development machines our DNN site renders just fine. But we recently deployed to our test server and on there the site only renders fine when logged in as the Host. When viewing the site as just a normal visitor, all the styles are messed up -- it is just a white page with images gone and menus stacked vertically.
Clues / Notes:
We recently added a new .ascx and module
There are javascript errors, but it hard to tell what is causing them
You may ask about the Log Viewer screen. I looked there and I see exceptions, but I think the exceptions there are unrelated ( will look into this)
Works fine in our local dev environment
In server, only renders fine when logged on as Host
What are some steps I can take to try to debug this? Where else can I look besides the Event Viewer to see what is going on here?
Thanks!
What is the "new .ascx" that you deployed? Is that a skin page?
If something is wrong in the skin page and it is the default site page (under Admin > Site Settings), that would explain why non-admin users have issues, but Admin/Host users (where the site's Edit skin is working) don't have issues.
This solved it:
https://stackoverflow.com/a/3831419/614263
Due to permission settings it looks like IIS was blocking requests from the root to javascripts and css files. When looking at the Network traffic in FireFox I noticed that 404 errors were coming from "login.aspx?ReturnURL=../../blahblah.css"
Thanks for all your help and suggestions.

Gumby framework - mobile nav doesn't work

I'm starting to build a new portfolio with this Gumby framework. I've chosen Gumby because I like SASS more than LESS, so I would like to try a framework based on this language.
The problem is that the mobile navigation doesn't work for me.
If I use the ui.html inside the downloaded package and I resize the browser window, the "three lines icon" appears, but if I click nothing happend!
If I use the Gumby's UI demo on the website it works...either for some website I saw here on stackoverflow that use gumby!
I've checked all the paths, the developer told me that I have to use gumby.min.js and it's uncomment by default, so i don't know why this mobile menu doesn't work for me.
Maybe I have to work online with the website hosted on a server? But I'ts strange...
I don't know what code to post, because it's simply the ui.html who all of you can find inside the downloaded gumby package.
I don't know javascript well so I cannot explain how/why this works but there is an issue with toggleswitch.js. Add e.stopImmediatePropagation(); to line 45. That's what worked for me.
If someone knows how or why this works I would love to learn.

Resources