Publish instance looking in fonts/ instead etc/designs/somePackage/fonts | Community
Skip to main content
S
squid267
Level 3
April 29, 2016
Solved

Publish instance looking in fonts/ instead etc/designs/somePackage/fonts

  • April 29, 2016
  • 4 replies
  • 1096 views

I imported an AEM project but I'm having trouble getting the publish instance to render correctly on my local instance. Right now the console is saying it can't find few fonts. On Author they are stored on etc/designs/myPackage/fonts but on Publish it is trying to load from /fonts

Any idea why this would be occurring? I should mention it is loading /etc/myPackage/styles/screen.css fine. The fonts loads fine in author preview mode as well.

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by squid267

Good morning. I figured it out. Looks like the agency configured the 'Apache Sling Resource Resolver Library' to have the following specific URL mappings. Once I added those rules to my local, the fonts started working!

4 replies

smacdonald2008
smacdonald2008
Level 10
April 29, 2016

ALl the same files are on pub as on Author? Is this correct - there are no differences? 

S
squid267Author
Level 3
April 29, 2016

As far as I can tell, I tree activated everything. Is there a way to verify it using CRXDE Lite? I login into that interface on publish but on see /content and /bin.

smacdonald2008
smacdonald2008
Level 10
April 29, 2016

Try to package up all files that are working on AEM Auth and then deploy to Pub - it looks like there may be missing files somewhere. If everything is on Pub instance -- you will get the same result. 

S
squid267AuthorAccepted solution
Level 3
May 2, 2016

Good morning. I figured it out. Looks like the agency configured the 'Apache Sling Resource Resolver Library' to have the following specific URL mappings. Once I added those rules to my local, the fonts started working!

Terms & ConditionsAccessibility statement

Loading footer...