[ottie]

I guess it was more obvious than I thought:
Dambuster could still do its work but I added a padding with (the width of the vertical navigation) in the stylesheet to override Dambuster's padding:0.
.site-inner {
padding-left: 250px !important;
}
And then removed it in the mediaqueries:

@media only screen and (max-width: 1264px) {
.site-inner {
padding-left: 0px !important;
}
Hope this can help anyone with the same issues.
ottie

[ottie]

Thank you Brad for the hint.
I guess I won't remove the plugin as my customer's page was built on it.
I can understand what you mean - if I would swap it against another custom fields plugin (like Types/Views) or handcode fields, the code would still work as it is just a custom field filled with data.
The only thing that really worried me was the amount of echoes - I tied to concatenate, but ended up with a different page 😉
The way it is built now shows me structure and it even looks like html all the way.
Would the amount of echoes influence the speed?
Or should I just leave it like this?
Thanks.

[Author]

Posts