The error you're currently seeing is a Kudu issue with running node/npm for deployments. On the next deployment, the script will be regenerated. This is the directory where Kudu caches kuduscript-generated deployment scripts. If something seems off with your deployment script, you can always use the Kudu console to delete the contents of /home/site/deployments/tools. Kuduscript will generate scripts with platform-appropriate line endings, but if those scripts are modified, or if you provide your own custom deployment scripts, it's important to make sure that your editor doesn't change the line endings. ![]() On Linux, it's important that any bash deployment scripts that get run have Unix line endings (LF) and not Windows line endings (CRLF). If your browser window was to be >2000px high, you would be able to see it, just hovering along by itself way below the rest of the site. And since it's now fixed in place, scrolling has no effect on it, which means its permanently located outside of your viewport. Once you enabled fixed positioning, and didn't provide any top value yourself, that number would still be top: 2000px. Since the footer takes up the full width of the screen, the left value likely defaults to 0 this is fine and that's not the source of the problem.īut, since the footer is located on the bottom of your site, its auto/default top value max well be like 2000px -> you have to scroll down to even be able to see it. ![]() In this case, the default values (which most likely reflect the effective top/left values with the default position: static) are just not ideal. Just because you haven't provided left/right/top/bottom properties, doesn't mean they are not in effect. ![]() Left/right/top/bottom properties set), it just disappears. I noticed that when I set a footer to have fixed positioning (with no Well, you've kind of hinted at the problem yourself already.
0 Comments
Leave a Reply. |