Skip to content

Allow for different strategies to get list of extension to use for site package #43

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

Open
sorenmalling opened this issue Feb 16, 2024 · 1 comment · May be fixed by #44
Open

Allow for different strategies to get list of extension to use for site package #43

sorenmalling opened this issue Feb 16, 2024 · 1 comment · May be fixed by #44

Comments

@sorenmalling
Copy link

I suggest that the default PackageHelper::getSiteListForSiteModule could be replaced by a extension configuration.

Reason

EXT:bolt requires extensions to have the prefix site_. In a current project, we use the concept of "layout" packages, that renders content. They are prefixed with a different prefix than site_.

Suggested solution

I have a POC at hand for this idea.

Via ext_conf_template.txt the strategy can be changed to a different class, implementing a single method, returning a collection of site packages that can be selected in the backend.

@sorenmalling
Copy link
Author

I've proposed a solution that takes a value from the extension configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant