Hi Bret,
When you install your Wagn, it doesn't yet have the compressed version of the CSS yet. What's supposed to happen is the same process that happens whenever you save a new stylesheet, which is something like this:
- Wagn looks for the CSS file associated with that url
- It fails to find it and so generates a compressed file
- It sends a redirect, and
- Voila, your stylesheet loads. Thereafter the whole process is very speedy.
The fact that you're getting a 404 (as opposed to, say, a 302 redirect) means something is going wrong at least by step 3, but I'm guessing the issue is even sooner.
When you say "
domain.com", are you just substituting that for the real domain for privacy reasons, or do you literally mean "
domain.com"? If the latter (and, as I would presume, you're not actually installing a wagn into the root path of
domain.com!), then the question is where that domain is coming from.
Assuming you're just substituting that in, can you confirm that the domain of the css link is correct and that the wagn is running in the root path of the domain? (By root path, I mean that you don't have it installed such that the home page is something like
whateverdomain.com/mywagn/Home.) And can you see the 404 showing up in the wagn logs?
One last request: would you be willing to continue this conversation as a
Support Ticket? We try to keep these lists pretty low volume, and that would help!
Best,
Ethan