Ruben

@golinski @cmrockwell @reggie7 great discussion here - one comment on the access servlet: that is probably a permission issue in `/perapi/admin/access.json` that one should allow read for everyone - since...

@cmrockwell I think that is what I was trying to say - we should split the discussion into a different ticket - this issue is about `login does not work...

@cmrockwell not sure if we really should make per:Asset depend on nt:file - an asset does not need to be a file, right? its more the sub node that holds...

@reggie7 have you tried clearing caches? I currently do not see this issue but I also remember somebody else having an issue with composum and sling9 that was caused by...

@reggie7 and you try again? for me at least this is fixed by https://github.com/headwirecom/peregrine-cms/commit/f4735263c769e37aafcffddbae72595063aad7c2

closing this issue as this is solved by using the launcher/far from https://github.com/peregrine-cms/peregrine-builder - we had a bad repoinit script and an older version of composum configured

@ehdatheadwire it is still an issue but it seems to be limited to windows installations and seems to be an issue in https://github.com/apache/sling-org-apache-sling-starter (outside of the peregrine project). I have...

in general the server side rendered container is currently missing the rendering of the placeholder that can be found at [1][2] the drop target needs to be visible in authoring...

this issue is now limited to windows 10 and some newer jvm's - the problem is that some content from the initial bundle content are created as files instead of...

@cmrockwell @ehdatheadwire I think it would be nice to make sure we get server side rendering right again for the 1.0.0 release and start treating it with more attention going...