-
Notifications
You must be signed in to change notification settings - Fork 36
Template file could not be read on modulus #62
Comments
Hm, I wonder if this is related to XervoIO/docker-build-meteor#14 and thus fixed by #61. Are you able to try the solution in #61 ? |
@johanbrook - Thanks for responding.
|
Hm, I see two different logs here:
and
That's kinda weird. There's always the full path that's being logged when there's an error. Did you set the |
In Mailer.js, I see the following: Utils.Logger.error( Looks like this should log only 'template.path' which is just the file name. On Mon, Apr 25, 2016 at 2:25 AM, Johan Brook [email protected]
Thanks |
Update: The previous log that I posted was not correct. I re-dployed and restarted the app.
I tried changing APP_DIR to /mnt/app/bundle in code by setting process.env.APP_DIR just before
|
I don't know if our issue is related, but we are seeing a similar error, but with a deploy to Meteor's Galaxy servers. One interesting thing we saw was that if we changed the name of the missing template file, the error switched to a different template file in our /private directory. This tells me it is something related to the load order of our templates, but I am struggling to identify the issue. |
@vjain20 I was able to figure out the root cause of our issue...we had two email templates that had the exact same html contents. When they compiled, meteor got confused as to which template mapped to which html. Not sure if this is your issue as well, but you might want to check that :) |
Hi,
I am using lookback:meteor-emails package and it works fine on my laptop, but it throws an error when I try to deploy my project to modulus.io. In the Template , i just use the name of the file as path (welcome.html). But I am always getting a "Could not read template file" error . Following is the log:
The text was updated successfully, but these errors were encountered: