Skip to content
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

Serverless pages can't access collections #2268

Closed
cfjedimaster opened this issue Mar 9, 2022 · 5 comments
Closed

Serverless pages can't access collections #2268

cfjedimaster opened this issue Mar 9, 2022 · 5 comments
Labels

Comments

@cfjedimaster
Copy link

Describe the bug
I've got a template being used by the Serverless plugin. It can't seem to access collections.

To Reproduce
Try to use collections in a serverless page. :)

Expected behavior
That it should work. If it isn't supposed to work, then it should be documented.

@zachleat
Copy link
Member

Cross posting discussion from Twitter here https://twitter.com/roobottom/status/1459106529781686285

Notably,

For the record precompiledCollections is a stop gap—the goal is to get collections working on serverless without manual intervention.

@vnourdin
Copy link

vnourdin commented Apr 3, 2022

Is this supposed to work with 11ty 1.0.0 ?
I reproduced what you shared, but in my serverless page collections is still empty.

@ryangittings
Copy link

@zachleat is there any sort of release version aim for this being included as standard without manual intervention? I'm working on a project that requires this, but don't want to invest too much time if it's something that might be coming shortly.

Thanks as always! ❤️

@lehrblogger
Copy link

I ran into this bug too, and @zachleat suggested in #2437 that I use Edge functions, which I finally had a chance to try out today.

With them, I'm seeing collections.all is undefined inside of the {% edge "liquid" %} blocks. The branch I used to test is here. Am I doing something wrong, or might there be another regression?

Let me know if I should create a new issue. Thanks again!

@zachleat
Copy link
Member

zachleat commented Apr 9, 2024

Stale per project slipstream changes in #3074.

@zachleat zachleat closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants