funkydan2 / alpha-church

Hugo theme for churches based on a html5up theme
https://alpha-church.netlify.app
Other
68 stars 59 forks source link

icons doesn't show up #32

Open quickzebra opened 3 years ago

quickzebra commented 3 years ago

I followed the instruction step by step. It works fine via locahost:1313. However, icons are not showing up after I uploaded the /public to my website.

theme-error
funkydan2 commented 3 years ago

Could you link to your site? Having a look at the HTML code should give a hint as to what's happening.

quickzebra commented 3 years ago

Daniel

Many thanks for your quick response. please see http://dev.gettocloud.com/ Really appreciated your help in advance!

On Sun, Nov 15, 2020 at 3:26 PM Daniel Saunders notifications@github.com wrote:

Could you link to your site? Having a look at the HTML code should give a hint as to what's happening.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/funkydan2/alpha-church/issues/32#issuecomment-727477928, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGBTNUZMMDY6OB4BA2BKLF3SP5J55ANCNFSM4TV2IDQA .

funkydan2 commented 3 years ago

Check your config.toml file. The first line should be `baseURL = "http://dev.gettocloud.com/".

For some reason, your site has references to http://localhost:1313, which is the URL of the testing server (i.e. when you run hugo server on your development machine. But that shouldn't be referenced in the HTML in /public.

quickzebra commented 3 years ago

Thanks for your response. Daniel. I've updated baseURL and regenerated index.html with right baseURL. However, the icons still don't show up.

funkydan2 commented 3 years ago

Screen Shot 2020-11-17 at 8 09 19 am

So, using the developer console in Firefox (I think Google Chrome has the same kind of tools - really worth learning to use if you're going to be developing websites), these are the errors your site is currently throwing.

I think the problem is how your web server is configured. It's serving css files with the MME type text/html rather than text/css. I reckon you might find some help reading this thread.

I don't think this is an issue with the theme or with hugo. You might be better off looking at an nginx specific forum.

quickzebra commented 3 years ago

really appreciated your guidance. I am using Amazon S3 to host the static files. I checked the individual files in the bucket, clicking the properties tab, then in the meta-data section confirming in 'text/css' as the value. But the problem still exist.
Anyway, I wonder if you could help me figure out a way to use static image files instead of using fontawesome. Thanks a lot for your guidance.

funkydan2 commented 3 years ago

I've not used Amazon S3 for hosting. But I think the problem is with your Nginx configuration.

I recommend having a look at this thread about configuring Nginx to serve CSS and JS files correctly

funkydan2 commented 3 years ago

And maybe these:

http://markgibson.info/2013/09/css-and-amazon-s3.html

https://discourse.gohugo.io/t/css-working-on-hugo-server-but-not-static-pages/9447/6