-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #149 from clash82/cookies
EZP-24150: Implement privacy cookie law in demo bundle
- Loading branch information
Showing
4 changed files
with
6 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,3 +20,5 @@ | |
</div> | ||
</div> | ||
</footer> | ||
|
||
{{ show_privacy_cookie_banner() }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this thing broke the installer.
When doing a composer create-project ezsystems/ezplatform it results in:
assetic.ERROR: The template "eZDemoBundle::page_footer.html.twig" contains an error: The function "show_privacy_cookie_banner" does not exist in "eZDemoBundle::page_footer.html.twig" at line 24
[RuntimeException]
The source file "/var/www/ezpublish/ezplatform/ezpublish/../web/bundles/ezsystemsprivacycookie/js/privacycookie.js" does not exist.
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ilukac, can you try assets:install and assetic:dump?
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it doesn't matter what I will do afterwards, but the installer is broken. Somebody else who tries to install will fail that is the point ;)
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, only said that because i experienced the Same after updating, not tried with fist install though...
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, this is caused by no use of version (
dev-master
) in your use of the create-project command, or you can also say it is because there is nocomposer.lock
in v0.5. /cc @bdunogier :)c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, the "composer create-project ezsystems/ezplatform" should work like a charm.
Maybe to setup soem travis test for this?
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it should (just work), but when we tag relies on dev packages you get this basically, something to improve on for next tag I guess.
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The dev-master version on 2015.03 was a mistake.
The next release (very soon) will have "strict" version numbers, and won't update to master like this. I'll also take care of including a composer.lock file.
Do you see anything else that should be done there ?
c13fb0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other then that it is only @ilukac's remark about making sure we cover this in tests somewhere.
As our daily internal deployes should also have one for latests stable, and as they should ideally run a few BDD tests to verify that they boot, this might be it. (so Jenkins rather then travis for this, travis tests master stuff on purpose).