hey guys, just a quick heads up:
1) creating new easyblog posts (in admin or eb directly) associated with a group are not generating a stream entry in that group. when you create a blog in a group using the story panel it does generate a stream.
2) users can only post in groups where they're members - that makes perfectly sense. having said that currently this restriction also applies to admins, this shouldn't be the case at all. again, this problem only exists when you create a post directly in eb. if you'd go to the actual group as an admin and use the story panel it will work fine.
3) all extensions come with the JS option "optimize" that - by description and theory - is designed especially for the use of multiple stackideas extensions to only load foundry once. unfortunately at this point that good idea can not be utilized, EB uses foundry v5, ES uses v4, ED loads v3 and redactor wants v2... so to get things back to useful in terms of JS/foundry loading all extensions should run on the same version, which surely should also make it easier for you guys at the end - if you only have to manage one version as well
1) creating new easyblog posts (in admin or eb directly) associated with a group are not generating a stream entry in that group. when you create a blog in a group using the story panel it does generate a stream.
2) users can only post in groups where they're members - that makes perfectly sense. having said that currently this restriction also applies to admins, this shouldn't be the case at all. again, this problem only exists when you create a post directly in eb. if you'd go to the actual group as an admin and use the story panel it will work fine.
3) all extensions come with the JS option "optimize" that - by description and theory - is designed especially for the use of multiple stackideas extensions to only load foundry once. unfortunately at this point that good idea can not be utilized, EB uses foundry v5, ES uses v4, ED loads v3 and redactor wants v2... so to get things back to useful in terms of JS/foundry loading all extensions should run on the same version, which surely should also make it easier for you guys at the end - if you only have to manage one version as well