-
AuthorPosts
-
February 26, 2024 at 9:43 pm #1435493
Hi there,
for no apparent reason, some styles are not loading anymore from the customizer while others do. 2 weeks ago it was all fine and I have not done anything to it since. Why might this be? I have not updated anything.
Any ideas why this might happen?February 26, 2024 at 10:49 pm #1435500Ok, they are loading now after I changed the order of the styles. I put the ones that were not loading at the top of the customizer. Now fine.
Except there is a new problem. Some of the boxes lost their margins/padding. eg. on the page über mich, the table with the dates was in the same line as the text above. NOw it is squashed to the side.
It happened after I pasted this morning a new style you sent for the flip boxes on the front page. After that the styles went crazy.Which one is the style that affects the margins of the text pages on all the pages?
Best
PeterFebruary 27, 2024 at 7:23 am #1435530Hi,
Thank you for the inquiry.
Would you mind posting the css code using Pastebin.com? We will check to see if there is any invalid css code that is causing the layout to break. You can also verify it yourself using the following tool.
// https://www.cssportal.com/css-validator/
Best regards,
IsmaelFebruary 27, 2024 at 9:07 am #1435550Ok I inspected the code with css validator. But no luck. The margins are still f*k up side wide..
February 27, 2024 at 9:07 am #1435551.justify-text {
text-align: justify;
-webkit-hyphens: auto; /* For Safari */
-moz-hyphens: auto; /* For Firefox */
hyphens: auto; /* Standard */
}#top .av-video-slide .avia-slide-wrap, #top .av-video-slide iframe {
background: #fff;
}.avia-icongrid-front,.avia-icongrid-flipback {
border-radius: 100%;
min-height: 300px;
min-width: 300px;
}.av-hriqo-df64f73a2229a5a484cc56fae9caca2e table tr th {
width: 20%;
font-size: 20px;
font-weight: bold;
text-align: left;
background-color: #000000;
padding: 8px;
}@media only screen and (max-width: 767px) {
#top .avia-icongrid.av-flex-cells.av-break-989 .av-icon-cell-item {
flex: 1 1 100%;
}
}@media only screen and (max-width: 767px) {
.responsive #top.page-id-472 .avia-data-table.avia_pricing_minimal tr {
padding-bottom: 20px;
}
}@media only screen and (max-width: 767px) {
.responsive #top.page-id-472 .avia_responsive_table .avia-data-table tr:first-child th {
display: block;
}
}
.responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th {
padding: 0;
}
}#top .av-82qhko-49fd44439e70710ba9259a5b8656603c .avia-data-table {
border: 0;
padding: 10;}
div .avia-table {
background: transparent;}
#top.page-id-472 #main .main_color .avia-data-table * {
border: none;
background-color: #fff;
font-size: 18px;
text-align: left;
}#top.page-id-472 .main_color .avia-data-table.avia_pricing_minimal th {
color: #666666;
width: 15%;
}#top.page-id-472 .av-hriqo-df64f73a2229a5a484cc56fae9caca2e .avia-data-table td:before {
display: none;
}.av-hriqo-df64f73a2229a5a484cc56fae9caca2e table tr th {
width: 20%;
font-size: 20px;
font-weight: bold;
text-align: left;
background-color: #000000;
padding: 8px;
}.avia-form-success {
text-align: center;
border-style: solid;
border-width: 0px;
padding: 20px 15px;
line-height: 1.4em;
border-radius: 2px;
clear: both;
Font-size: 14px;
font-weight: normal;
text-decoration: none,
}.page-id-1331 input, .page-id-1331 textarea {
border-color: #009BDD !important;
}.input_checkbox_label {
color: #6F6571 !important;
}.responsive #top #av_section_4 .container {
width: 100%;
}@media only screen and (max-width: 767px) {
#top #av_section_4 .avia-icongrid .av-icon-cell-item .avia-icongrid-flipback {
padding: 0 3em;
}
}@media only screen and (max-width: 767px) {
#top .avia-icongrid.av-flex-cells.av-break-989 .av-icon-cell-item {
flex: 1 1 100%;
}.avia-icongrid-flipbox .av-icon-cell-item .avia-icongrid-front .avia-icongrid-inner, .avia-icongrid-flipbox .av-icon-cell-item .avia-icongrid-flipback .avia-icongrid-inner {
padding: 0 3em;
}.all_colors h3 {
line-height: 1.3; /* Adjust the value to increase or decrease spacing */
}.keinspace span {
display: block; /* Ensure the span is treated as a block element */
margin-top: 0px; /* Adjust margin-top to reduce space */
font-size: 0.7em; /* Adjust the font size smaller */
color: #6F6571; /* Change the text color to grey */}
.avia-cookie-consent {
width: 100%;
position: fixed;
background-color: #009BDD;
z-index: 999;
color: rgba(255,255,255,0.9);
padding: 1.1em;
text-align: center;
opacity: 1;
visibility: visible;
transition: all 0.3s ease-in-out;
overflow: hidden;}
.avia-cookie-consent-button,
.avia-cookie-info-btn,
.avia-cookie-hide-notification,
.avia-button {
background-color: white !important;
color: black !important;}
@media only screen and (max-width: 767px) {
/* Add your Mobile Styles here */
#top #header .av-logo-container .av-main-nav>li.av-burger-menu-main {
display: block;
}
}@media only screen and (min-width: 768px) {
/* Add your Mobile Styles here */
#top #header .av-logo-container .av-main-nav>li.av-burger-menu-main {
display: none;
}
}#avia-menu .menu-item {
display: none;
}
.av-burger-menu-main.menu-item-avia-special {
display: block;
}
}.container_wrap {
border-top-width: 0;
}#scroll-top-link {
display: none;
}.avia_iconbox_title {
font-size: 18px;
color: #6F6571;
}.avia_iconbox_title:hover {
color: #009BDD; /* Set the font color on hover to blue */
}#header_main .av-logo-container {
margin-bottom: -14px;
}February 27, 2024 at 12:40 pm #1435584I have reinstalled the backup from 2 days ago. So really everythign should be fine. But for some strange reason, the small margins of some text boxes sidewide still remain. See here.
The text of the above boxes was aligned with the text of the bottom box. So somehow there is a broken settung? Style etc? I have reinstated the old backup with database and ftp. Everything else is fine except for that issue…February 27, 2024 at 6:29 pm #1435629In most cases it happens with media-query instructions. A bracket that is forgotten to be closed or one that is set too much.
here is one extra – or before the closing media query bracket is set to early?
.responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th { padding: 0; } }
next here is an opening bracket – with no closing ( i do not know if all the rest should be inside the media query – or if you like to close directly after that)
@media only screen and (max-width: 767px) { #top .avia-icongrid.av-flex-cells.av-break-989 .av-icon-cell-item { flex: 1 1 100%; }
.av-burger-menu-main.menu-item-avia-special { display: block; } }
February 27, 2024 at 6:50 pm #1435632btw. even if you are opening a media query – but have some other media querries inside that open and close correctly – a following closing bracket then have no effect.
see here some code of your css ( those rules that are correct are erased here )
@media only screen and (max-width: 767px) { .responsive #top.page-id-472 .avia_responsive_table .avia-data-table tr:first-child th { display: block; } } /**** closed too early ? ******/ .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th { padding: 0; } } /**** or an additional superfluous bracket ******/ @media only screen and (max-width: 767px) { #top .avia-icongrid.av-flex-cells.av-break-989 .av-icon-cell-item { flex: 1 1 100%; } .avia-icongrid-flipbox .av-icon-cell-item .avia-icongrid-front .avia-icongrid-inner, .avia-icongrid-flipbox .av-icon-cell-item .avia-icongrid-flipback .avia-icongrid-inner { padding: 0 3em; } .all_colors h3 { line-height: 1.3; /* Adjust the value to increase or decrease spacing */ } .keinspace span { display: block; /* Ensure the span is treated as a block element */ margin-top: 0px; /* Adjust margin-top to reduce space */ font-size: 0.7em; /* Adjust the font size smaller */ color: #6F6571; /* Change the text color to grey */ } .avia-cookie-consent { width: 100%; position: fixed; background-color: #009BDD; z-index: 999; color: rgba(255,255,255,0.9); padding: 1.1em; text-align: center; opacity: 1; visibility: visible; transition: all 0.3s ease-in-out; overflow: hidden; } .avia-cookie-consent-button, .avia-cookie-info-btn, .avia-cookie-hide-notification, .avia-button { background-color: white !important; color: black !important; } /**** missing closing curly bracket ******/ /***** some media querries inside here - that are correctly opend and close so the following closing has no effect to that before *******/ .av-burger-menu-main.menu-item-avia-special { display: block; } } /**** additional superfluous bracket ******/
It is therefore best to avoid nesting media queries and possibly combine the same ones.
There are a lot of single@media only screen and (max-width: 767px) {
February 27, 2024 at 10:23 pm #1435653Since this is all code that you supplied to me in the first place, could you be so kind to clean it up and deliver a version that works? And not just tell me what is wrong with it?
February 28, 2024 at 6:35 am #1435671this is hard to say – because i do not know where to close an opended media query on your code, because I don’t know whether these errors occurred because you inserted a new media query rule into an existing one or simply forgot to put a closing bracket.
So i can’t tell you whether you should remove it where i wrote “closed too early?” (because then the bracket at “or an additional superfluous bracket” would be correct. Or just remove that bracket ( at “closed too early?”) . That depends on the intention of what you want to achieve. Both leads to a working code but do different things.
in other words :
i do not know if you like to have:@media only screen and (max-width: 767px) { .responsive #top.page-id-472 .avia_responsive_table .avia-data-table tr:first-child th { display: block; } .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th { padding: 0; } }
or that:
@media only screen and (max-width: 767px) { .responsive #top.page-id-472 .avia_responsive_table .avia-data-table tr:first-child th { display: block; } } .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th { padding: 0; }
etc.
_______So, if I no longer knew exactly what belonged to which intention, I would first remove everything. Then reinsert the ones that are unproblematic (opening and closing brackets that are clear ) and then add the media queries step by step.
February 28, 2024 at 2:12 pm #1435745February 28, 2024 at 3:17 pm #1435765Bei dem Nick ausgesonnen, nehme ich mal an ich kann dir auch deutsch antworten:
Diese Fehler kann sind durch die vielen Media Querries entstanden. Eine Klammer die aufgeht – muß auch wieder geschlossen werden.
Da ich nicht weiß, was du mit deinen Regelen bewerkstelligen wolltest, kann ich auch nicht entscheiden ob der Fehler ein vorzeitiges Schließen der Klammer ist, oder eine überflüßig gesetzte Klammer ist.
Im Beispiel oben ob diese Regel nur unterhalb von 767px gelten soll oder eben generell:.responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th { padding: 0; }
Davon ist abhängig ob die Klammer oben zu früh geschlossen wurde, oder ob die andere zu viel ist. etc.
Da die Fehler mannigfaltig sind, empfehle ich alle zu entfernen. Die jenigen die leicht als korrekt zu erkennen sind wieder einzufügen. Also die nicht in media-querries gesetzt sind und auf/zu gehen.Und dann neu zu überdenken, was gemacht werden muss.
PS: um solche Fehler in Zukunft zu vermeiden; immer die Regeln, die du neu hinzufügen willst ganz an das Ende der Quick css zu setzen – niemals so zwischen drin reinzuschmeißen. Das birgt in sich Fehler Quellen. Dann am Ende – sortieren und die Media-Querries zusammenführen.
Ansonsten musst du eventuell auf die Hilfe eines Mods hoffen, der sich einloggt, und die verschiedenen Möglichkeiten durchspielt.
__________
With the nickname ausgesonnen, I assume I can also answer you in German:
These errors can be caused by the many media queries. A bracket that opens – must also be closed again.
Since I don’t know what you wanted to achieve with your rules, I can’t decide whether the error is a premature closing of the bracket or a bracket that was set superfluously.
In the example above whether this rule should only apply below 767px or in general:.responsive #top.page-id-472 div .avia_responsive_table .avia-data-table td, .responsive #top.page-id-472 div .avia_responsive_table .avia-data-table th { padding: 0; }
It depends on whether the bracket at the top was closed too early, or whether the other one is too much, etc.
Since the errors are manifold, I recommend removing all of them. The ones that are easy to recognize as correct should be reinserted. So the ones that are not set in media-querries and open/close.And then rethink what needs to be done.
PS: to avoid such mistakes in the future; always put the rules you want to add at the end of the quick css – never throw them in between. This is a source of errors. Then at the end – sort and merge the media queries.
Otherwise, you may have to hope for the help of a mod who logs in and runs through the various options.
February 29, 2024 at 12:11 pm #1435863Hi,
Try checking your css with this tool ▸ http://csslint.net/
in your css above I see an extra bracket that will mess up your stylesheet
Best regards,
MikeMarch 1, 2024 at 7:33 am #1435937Yes Mike – but i can not decide it because either your red arrow shows the superflous Bracket – or the blue arrow shows a too early set closing bracket.
Which one is to remove now. My guess is that the former (blue) is more likely to be removed.Further down there is also nesting of media querries, and I’m not sure if that works.
A bracket was opened, then new media query statements follow without closing the first one – after the insertions there is a closing bracket – but I don’t think that works. (maybe it works, because the parameters are the same).March 1, 2024 at 5:26 pm #1436000 -
AuthorPosts
- You must be logged in to reply to this topic.