-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
TL_CSS needs to be prefixed with “web/” for combined CSS files #300
Comments
The problem probably is the |
Fixed in dd2fa41. |
Repeating ourselves again… please do not commit changes that do not belong together… |
These changes belong together. What's your problem? |
leofeyer
added a commit
that referenced
this issue
Jul 23, 2015
leofeyer
pushed a commit
that referenced
this issue
May 9, 2019
Description ----------- One of the more frequently requested features for Contao 4.6 and up from the https://github.com/friends-of-contao/contao-privacy extension is the ability to use a splash image for YouTube and Vimeo video elements, to prevent client connections to these services upon visiting the Contao website. Since the future of that extension regarding Contao 4.6 and up is unclear, I think it would make sense to integrate this feature into the core. ![screenshot_2019-01-26 articles home content elements edit content element id 11 - contao open source cms](https://user-images.githubusercontent.com/4970961/51789660-878f5880-218b-11e9-8ce9-cf7e7fee6fa0.png) Commits ------- 98fb89ac add splash image to vimeo & youtube elements 7fd82d62 use a for splash image wrapper 6867aa8d remove class and streamline JS abba23c4 Merge remote-tracking branch 'upstream/master' into feature/video-splash-image f3900734 fix videoSplash template variable assignment 62467a1d Rename "videoSplash" to "splashImage" 736cad76 Add the splash image legend language string
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you add a stylesheet via
$GLOBALS['TL_CSS']
:The text was updated successfully, but these errors were encountered: