-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File not found at path [...] when using SSG #178
Comments
Hi. Is it possible for you to extract a more detailed exception stack-trace by removing https://github.com/statamic/ssg/blob/master/src/Generator.php#L280-L291 Thanks |
Sure! Here's the stack trace:
|
This looks like console output. Is there anything in |
Yeah, sorry. My bad. Here's the log:
|
I can reproduce this. As a temporary fix, disable placeholder generation by adding Since we are using same code as
will also trigger this same error. |
Adding this workaround in |
Thanks for both suggestions, @ncla! I couldn't get it to work with the For reference, I added the snippet below line 112 of
|
You can fork the repository and add the changes there and reference the fork repository in composer.json
https://stackoverflow.com/questions/13498519/how-to-require-a-fork-with-composer
Another option is to do Composer patches. https://rias.be/blog/using-composer-patches
…On Tue, Nov 22, 2022 at 04:10, Jaime Smeke ***@***.***> wrote:
Hey, just a followup on this. While this works great on my local env, I realized it doesn't work in prod, since statamic/ssg gets downloaded from source within build.sh. There's probably a way around it, but my skill only goes so far. 🤷
—
Reply to this email directly, [view it on GitHub](#178 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABKAQCYBYR6X7CU7UUEKDY3WJQTP7ANCNFSM6AAAAAARQRJV6E).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
🤦♂️Of course. So many simple solutions and yet I ended up with ones like
messing with `sed` and moving an overwritten file around, which ended up
working fine but these solutions are obviously 10x more elegant.
Thanks!
…On Tue 22 Nov 2022 at 1:42 ncla ***@***.***> wrote:
You can fork the repository and add the changes there and reference the
fork repository in composer.json
https://stackoverflow.com/questions/13498519/how-to-require-a-fork-with-composer
Another option is to do Composer patches.
https://rias.be/blog/using-composer-patches
On Tue, Nov 22, 2022 at 04:10, Jaime Smeke ***@***.***> wrote:
> Hey, just a followup on this. While this works great on my local env, I
realized it doesn't work in prod, since statamic/ssg gets downloaded from
source within build.sh. There's probably a way around it, but my skill only
goes so far. 🤷
>
> —
> Reply to this email directly, [view it on GitHub](
#178 (comment)),
or [unsubscribe](
https://github.com/notifications/unsubscribe-auth/ABKAQCYBYR6X7CU7UUEKDY3WJQTP7ANCNFSM6AAAAAARQRJV6E
).
> You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#178 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHHTBDMHLEBQJ5JHPPJ5C3WJR2OVANCNFSM6AAAAAARQRJV6E>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am closing this as technically this is not an issue on this addon but Additionally as of v2.14.5, placeholder generation will fail silently and error will be logged instead, so in theory when deploying with SSG you should not see this error stop your deploy, the downside you will end up with no placeholders without knowing why. |
…eration in SSG context Workaround: spatie#178 (comment)
… SSG context (#209) Workaround: #178 (comment)
Bug description
Whenever I run ssg, I get an error saying
(File not found at path: containers/assets/site/[...])
How to reproduce
Run
php please ssg:generate
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
runtime (new)
Additional details
Started happening fairly recently. I noticed some similar issues but can't pinpoint to what's going on.
The text was updated successfully, but these errors were encountered: