I've just set up a publish environment (port 4503), and I've Activated all of my content (/content/..., /content/dam/..., /apps/..., /etc/Designs/...) The homepage looks great on publish, but if I try and view a child page I get a "No resource found Cannot serve request to /content/site-name/en/news.html on this server". If I hit the same URL replacing ".html" with ".json" or ".infinity.json" I get a listing of all the content, and I can login to the /siteadmin on the publish site and see the pages there, so I know the content is there. But there seems to be a rendering component that is missing.
The logs aren't much help:
GET /content/site-name/en/news.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException org.apache.sling.api.resource.ResourceNotFoundException: No resource found
Thanks for the response. We figured it out - it was because the footer parsys had no content, and the child pages were referencing the footer resource. We weren't doing a proper check to see if there were any child nodes when referencing the footer component. The author instance was not showing the footer if wcmmode was anything but disabled on the child pages, which is why we only saw the problem on the publish instance.
Your #1 suggestion above did in fact cause the problem on authoring, and we narrowed it down to the footer component.