I have deployed my next js app on to cPanel, everything is ok, but it shows just html, scss files are not working. How can I fix it?
I have searched on google but could not find proper answer. I have no idea what to do. Has anyone encountered this problem?
Related
I'm struggling on how to implement font icon in nativescript-vue, I decided to use font-awesome 5 and followed a bunch of different tutorials, unfortunately, It still now working for me. Some devs have an output of a question mark, but for me, nothing is displaying. I've been stuck on this task for a long time now. I would really deeply appreciate some help.
Thank you :)
I'm using:
Typescript-vue-decorator
Nativescript v6.4
This is one of the steps I have followed thoroughly
NativeScript + Vue.js + FontAwesome
Output
Total rookie here, but I was having huge drama getting it working. I reverted to using FA4.7. Still no joy. Ran up a Playground instance and the darn thing worked.
The only thing that was different for me was that my local default app.scss file started with these style references:
#import '~#nativescript/theme/core';
#import '~#nativescript/theme/default';
Whereas the playground defaults to the actual css files:
#import '~#nativescript/theme/css/core.css';
#import '~#nativescript/theme/css/default.css';
I updated my app.scss file to use the above css references and hey presto, font-awesome icons work. I have not gone to the effort of retrying with FA5 but its a good chance this might be the trick.
I hope this helps someone else. All the best.
The playground instance is available here.
I'm having a weird problem with Laravel application which has been at Linux Server previously and was working fantastic but while moving to a new IIS Server, I faced alot of problems and the last problem here is some problems in view, while css and JS files are loaded and there is no error in console.
I have posted this question previously, now I'm re-posting it again with more details.
e.g. In local and previous host the fonts are good and everything works correctly, but in IIS server the fonts are bigger than normal and in local and previous server,The Pop Ups are Shown and the fonts are fine As shown in this photo, but, in IIS server, The background gets dark but the popup is not shown and the fonts are bigger Like this photo.
When I check it via Inspect elements from Chrome no error is there and all CSS and JS files are loaded correctly, while everything works but all fonts are bigger and some designs are ruined.
What I have tried:
I tried php artisan dump-autoload and php artisan serve.
Updated the composer.
Cleared the cache.
rewrited the mod and removed index.php from the link.
However, none of them works. I'm loading CSS and JS Files this way: <link rel="stylesheet" href="{{ URL::asset('assets/css/mystyle.css') }}"> and <script src="{{ URL::asset('assets/js/main.js') }}"></script>.
It looks like a very strange and weird problem, I don't know what is wrong while every CSS and JS files as well as every option works fine, but the fonts are bigger, some padding are ignored and some designs are ruined, while in localhost and previous server it was fine.
Can anybody help? and say what is wrong with this?
your problem is not familiar but any way here some tips :
in IIS server you should use URL::secure to connect with assets
post some code so we can find something wrong
use firefox developer edition to find your css problems in production
find the css selectors that effects your font in production
I've got a silly problem. It's probably just down to me not being able to see the wood for the trees... one of you geniuses might spot the problem immediately, or at least I hope so!
I've developed a theme for a Magento site using Bootstrap. First I built static HTML templates, which were tested for responsiveness, and they all worked fine.
I then integrated those templates into Magento... and the responsive elements stopped working. They were working initially, but at some point during the site development, they stopped working.
I've looked and looked at it and I can't see what's wrong. I presume there's some sort of conflict with Bootstrap somewhere but I just can't see it. There are no script errors that I can see and everything is loading correctly, but the responsive elements refuse to work.
Can someone take a look at the site at http://www.collaredclergywear.co.uk/ and tell me what I'm missing? I think it's probably something simple but I can't see the wood for the trees anymore.
Cheers,
Willo
One thing in style.css try commenting it. better remove style.css completely and test
.wrapper {
min-width: 954px;
}
We can get the source HTML, JS and CSS for a website by right-click and getting the source code. Is there any way we can get the same for installed Mobile app?
It is for my app. I developed a UI and installed it in my mobile to test it. Later I made some changes to my UI and couldn't recover my old changes. So I'm trying to recover it from my mobile. Any help would be appreciated.
Change file extension from ipa or apk to zip.
Then extract it somewhere. By skimming through those files you could find those html, js and css files.
I am publishing my Web App using the VS2013 publish mechanism. For some reason it has just started corrupting the js and css filenames. e.g.
From
<link href="/Content/bootstrap.css" rel="stylesheet"/>
To
<link href="/Content/css?v=puREEettBuwGkRK7y27hOQwXg4qvcAYRnG8wxc0gvnU1" rel="stylesheet"/>
This is only happening on publish to the live site. It works fine on publish to the localhost site. It looks like possibly some kind of versioning.
The defined bundles in BundleConfig are not being expanded, instead parsed with the above result.
Any ideas? I have not seen it before and its not showing up on Google searches. Thanks for any suggestions.
ANSWER:
For anyone else getting this problem - Once I realised it was the Bundles I found this which gave a lots of thoughts. However my specific issue was that I had installed Select2 via NuGet which had added a css directory in Content. As I was creating a Bundle pointing at Content\css these clashed. I removed the css directory and republished. Still didn't work. But when I removed that directory on the server manually it all started working again.