I have started to build an app using The SB Admin 2 bootstrap theme (can be found here:https://startbootstrap.com/theme/sb-admin-2). Everything is working fine on my localhost but when I pushed the code to Heroku a lot of components did not show or work.
To make it easier to compare, I have pushed the entire code to another Heroku app on https://testweb55.herokuapp.com/, where you can see the difference with what I see on localhost (similar to https://startbootstrap.com/previews/sb-admin-2): the user menu on the upper right hand side does not appear, the side bar does not collapse etc.
Do you know what I need to do to make it work on Heroku?
Thanks
Ben
Related
I've been moving step-by-step (as a webdev newbie) through the GatsbyJS installation via the Terminal. All looked great, except the Terminal appears "stuck" and I'm not sure how to resolve (i.e. whether to close Terminal app or let the process continue). It's been over an hour without any change in the Terminal prompt. Please see screenshot for detailed info. Any help would be much appreciated.
screenshot: Current state of Terminal app:
screenshot: Message when trying to close Terminal app:
Your terminal is not stuck. Everything works as it should.
It is listening to code changes which enables hot reloading. This way you can change code and you see the changes almost instantly in your browser. This makes for a pleasant developer experience and is industry standard.
Beware the old times when you had to manually restart your server everytime you made the tiniest code change.
Try opening a browser with url http://localhost:8000. Change some text inside your index.js. You should see it reload in the browser.
I'm developing on my localhost a new Blazor server-hosted app. I launch the template that it starts you out on... looks very nice. I change the text in the tag, refresh my browser... and no change. I refresh and refresh only to notice no change. Is something wrong?
Then I rebuild and rerun the app again and the change happened. Why do I have to restart the entire server for a small front-end change? I have to do this on every change I make? Even though the changes are for the front-end? If so, then the development experience for MVC apps is way better. I don't have to restart my server for changing the code for the front end.
I know dotnet watch exists, but it doesn't help. It still restarts the server for every change I make for the front-end. I have to wait like 10 seconds for just changing some CSS? Please tell me if I'm doing something wrong, or if this is by design.
Also, I tried the web-assembly version of Blazor. Same results.
I guess you are running the app with the debugger connected? this prevents the recompilation. You need to:
Press Ctrl-F5 to run the app without the debugger.
This should work on Windows using IIS, but on Mac "it's a bit more complex". According to a MSFT representative, they are planning on enabling this functionality for Mac users, but this info is already over a year old (from April 2020).
This issue still happens, and for me is a major downside. It doesn't make any sense to have to recompile entire project just because I changed some text on a page. If this is a design choice, it's doomed! Can't have a designer dependent on developers to recompile whenever a small change is required on simple html! Even if you change an element style you have to recompile!
I have a weird problem, everything with my Laravel app is setupped and was working fine both in local server and shared linux server, now in dedicated windows server some fonts has been larger and some functions are not working properly such as twitter bootstrap confirmation model, it reduces the background light but it doesn't show the pop up as well as footer items has no padding, it have came to the very top of the footer. I checked the inspect elements and everything is loaded. Have anyone faced the same problem?
I converted my website to an APK and it installs fine - the problem is that when trying to scroll up or down - the page sticks and the page refreshes to a page not available - the live site works perfect.
Try to use momentum scrolling. I don't know exactly what can cause your issue, but
Android 3+ and iOS 5+ implemented a new property called overflow-scrolling that enables momentum scrolling. And it works beautifully.
Look here: http://www.mobify.com/blog/beginners-guide-to-perceived-performance/
Hope that helps.
I was using a service from GoNative that packages mobile web sites into APKS - kind of a wrapper to allow mobile sites to function like apps. One of the configuration options was to use "web pool" services that cached pages to allow for faster processing - I deleted that feature and the site/app works fine.
I'm using font-awesome-rails to generate some icons on my site. When I run the site locally, the image icons appear correctly (they are styled to be different colors). However, when I push to production via Heroku, the styling is messed up (some icons don't appear, and none of the icons are the right color). What could I be doing wrong? I'm not even sure what could be wrong with my code, so if any particular snippets would be helpful for me to share, let me know and I'll add it.
The image on the left is a snapshop of the website in production, and the image on the right is the website running locally.
EDIT:
After restarting my development server, I'm finding the icons appear incorrectly locally as well. What could have gone wrong?
It seems like it was an issue with my Gemfile; when I checked out an older version of my Gemfile and Gemfile.lock, I was able to get rid of the problem.