Closed brianfeister closed 10 years ago
Hmm yes these URLs are leveraging symbolic links that will automatically exist if your project level modules actually do have public folders, but it is time for us to start testing if the files really exist before generating annoying 404s in the dev environment. Will clean this up. On Mar 26, 2014 12:49 AM, "Brian Feister" notifications@github.com wrote:
Not sure why or how this originated, but I've got 404's for the following:
modules/my-blog/js/content.js modules/my-case/js/content.js modules/my-groups/js/content.js
I don't know why the my-{something} directory would be searched for any content, I thought the way to override base functionality was to fork it inside /lib/modules/{original-dirname}?
Reply to this email directly or view it on GitHubhttps://github.com/punkave/apostrophe-sandbox/issues/40 .
This is fixed. No more freakouts about missing assets unless they really don't exist either in the original or the project-level module.
Not sure why or how this originated, but I've got 404's for the following:
I don't know why the
my-{something}
directory would be searched for any content, I thought the way to override base functionality was to fork it inside/lib/modules/{original-dirname}
?