-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
BS4 - Alerts not showing #3686
Comments
Reported by @Jimmi08 before here: #2898 (comment) |
@Moc Would adding that to e107.css fix it? |
@CaMer0n Yeah it did, I just wasn't sure if that was the best solution. It seems more of a band aid than actual fix, but I personally don't know another way to fix it. |
@Moc Do you know where the conflict occurs in e107? |
Not sure if I understand your question. See my initial issue report. It conflicts with the transitions.css file from Bootstrap 4. |
I can confirm that this is still the problem. Next solution is for bootstrap 4 not insert class fade in for alert boxes. Problem is combination s-message + fade classes |
@Moc Is this still an issue? The alerts display for me. How about you? |
Still the same issue for me. I see it works on the boostrap4 theme, but I am getting the same CSS conflict for my own custom theme (www.nextgeneration.city) I have this is in my theme.php as a temporary fix. If I delete it, the alerts are not shown: // Fix for alerts not showing. Conflict with BS4 (transitions.css).
e107::css("inline", "
.s-message.fade {
opacity: 1 !important;
visibility: inherit;
}"); |
It works for BT4 because there is the same fix in style.css:
|
neither me. |
See my answer and quote above. I don't know if that's the best way. Sure it will fix it but I'm no expert in CSS to determine if that's the cleanest way to do it. |
@Moc Sorry, I should have read the whole thread. Commit coming. |
In a bootstrap 4 theme, alerts (info, warning, error messages) are not visible on frontend because there is a CSS conflict with transitions.css from Bootstrap 4.
If I add the following to theme.php, it is fixed:
I (Jimmi! 😄 ) took this code from the vstore plugin.
I am not sure if this is the right fix, so I created an issue for it. Perhaps there's a cleaner way to do it as this is more a bandaid.
The text was updated successfully, but these errors were encountered: