I developed dotnetnuke skin. In my localhost both login and logoff time skin was working fine all images and skin.css file was loading. but in my live site logoff time skin.css file and images are not loading?
Check to see if you deployed the CSS files in production.
Check to make sure that the "paths" are correct, if you have any Includes in the CSS make sure that they are the proper path for production.
Post more details about what you are doing, what code, what errors, etc.
Related
Live Site
Repo
I just uploaded this project and the live site works fine. But for some reason the images are now gone when viewing it on localhost. It worked fine until I pushed and published the project.
The images folder is inside the public folder.
Also I just realized that when viewing the site on mobile, I seem to be able to scroll beyond the content (right and down). I’m not sure why that is..I also noticed that when viewing the site in the browser and enable touch simulation. Disabling it, it doesn't scroll beyond the content.
you have specified the file location as "./images/client-databiz.svg" for images
which is need to open the folder named images under the current JS file presents.
since during deploying it will build and make your code into static file
refer
you need to use "../../public/images/client-databiz.svg" to preview that actually.
I hope it will also work in production.
I have an angular.js web app, suddenly I have noticed that when I edit sources in WebStorm and click "Run" and my app opens in chrome browser, all sources are still old ones, they didn't updated! How can I fix that?
My local webserver hosts by node.js
As I said I'm very new to JS, and the problem was that sources in index.html were taken from example website and not from local sources, that it, pretty dumb issue, but it was a problem for me
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.
I have upgraded a site to DNN 7.2.1 following the recommended path from 5.6.8
If I stay in the skin MinimalExtropy, all seems fine.
If I change even to the Gravity skin, much goes wrong:
using "settings" on a page shows the settings dialog, but no changes are made on "update"
it is impossible to change out of the new skin without renaming the skin folders on the site, forcing a return to MinimalExtropy.
It appears that some part of the support for skins has disappeared.
Any suggestions of how to rescue the site?
Thanks
JC
It is likely that you are getting a Javascript error on the page and that is causing the postbacks in DNN to not fire properly. I would start by looking at your javascript console in your browser and trying to track down the source of JS errors.
Also be sure to check the Skin settings in the ADMIN/SITE SETTINGS page.
You might try a skin specifically setup for DNN7, I have one called HammerFlex, you can find more info about that skin at http://www.christoc.com/Projects/HammerFlex
I'm managing several DotNetNuke portals (as well as the main hosting itself). All of the portals have the default DNN icon in the address and when they're bookmarked. I want to have a custom favicon.!
It's the icon on the left side of this:
(source: dotnetnuke.com)
I've tried clobbering the default favicon.ico file in the root directory (where the web.config file is located). I've deleted, I've replaced, I've restarted the browser, I've bounced IIS. None of that works.
Has anyone come across a solution for the wonky favicon problem in DNN?
Times have changed in the DotNetNuke world since this question was answered. Now, the favicon is much easier to change.
Go to Site Settings underneath the Admin menu, and scroll down to Appearance. There should be an option to upload a new icon, or use one currently on your site.
You need to place the favicon in each portal's own folder (Portals/0/favicon.ico). Make sure you delete the icon in the root of your website, as that will (supposedly) override any portal-specific favicons and apply to all portals.
Have a look here as well: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/183454/scope/posts/threadpage/3/Default.aspx.
Favicons are notorious for being very aggressively cached by the browser. Sometimes even clearing the cache doesn't even do the trick, it can drive you mad. Clear cache, shift-refresh etc etc...
Have you tried clearing your browser cache? Or try using a browser on a different machine or just a different browser (FF versus IE for isntance). The favicon will cache and drive you crazy when it actually has changed.
The other thing to check is to see if you have more than one portal running on your DNN instance. If you have more than one portal, you can do a different favicon for each portal by putting the favicon in portal root and not the main web root.
http://www.hanselman.com/blog/FavIconicoCanBeABandwidthHog.aspx
Worth reading for performance purposes.