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

Minor clarification to README #56

Closed
wants to merge 2 commits into from

Conversation

NiklasBr
Copy link
Contributor

@NiklasBr NiklasBr commented Apr 8, 2020

I felt stupid for 30 minutes after double- and triple-checking why I got exceptions when using these in the routing.yml file, it seemed so logical at the time with the ch_cookie_consent: and all. This change might save other from the same ambiguity.

@@ -41,6 +41,7 @@ ch_cookie_consent:
### Step 4: Configure to your needs
Configure your Cookie Consent with the following possible settings
```yaml
# app/config.yml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For newer Symfony versions a file should automatically be created in config/packages/ch_cookie_consent.yaml, so in those cases it should not be in app/config.yml. So I rather see this be

config/packages/ch_cookie_consent.yaml

@@ -128,7 +129,7 @@ By loading Resources/public/js/cookie_consent.js the cookie consent will be subm
You can override the templates by placing templates inside your poject:

```twig
# app/Resources/CHCookieConsentBundle/views/cookie_consent.html.twig
# app/templates/bundles/CHCookieConsentBundle/cookie_consent.html.twig
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# app/templates/bundles/CHCookieConsentBundle/cookie_consent.html.twig
#templates/bundles/CHCookieConsentBundle/cookie_consent.html.twig

@NiklasBr NiklasBr closed this May 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants