Save
Saving
  • edgrbnz

    Well, that worked!

    However I added the class _center-1200 inside the text-element like this:

    <p class="_body_huge _center-1200">Simone Klimmeck is a Berlin based…</p>
    

    The Custom CSS is super simple (which is a good thing) and looks like this:

    ._center-1200 {
    max-width: 1200px;
    margin: auto!important;
    }
    

    It doesn’t work when I right click the element and ‹add HTML class and id› inside the gridder, though. Which seems to be a bug of sorts?

    Anyhow now this works but super strange that didn’t work otherwise.

    posted in General Discussion read more
  • edgrbnz

    Back to Top link states unfortuntely need to be styled via Custom CSS.

    It would be way cooler to have a simple shortcode like #laynextproject or #layprevproject instead of the interface element in the editor. This way the text element is a hyperlink and therefore behaves like a textlink does.

    Until now one always has to add some Custom CSS to make the Back to Top have a hover state. E.g:

    .scrolltotop p:hover {
        color: #efcece !important;
    }
    

    Cheers!!

    posted in Bug Reports read more
  • edgrbnz

    @fr I tried that before…
    Unfortunately this doesn’t make any difference. (it’s online now)

    posted in General Discussion read more
  • edgrbnz

    Hey @fr I tried your code as follows:

    @media (min-width: 770px)
    ._center-1200.no-parallax.no-offset.col.push-1.span-10.align-middle{
        width: initial !important;
        max-width: 1200px;
        margin-left: auto !important;
        margin-right: auto !important;
        padding: 0 5% 0 5%;
    }
    

    It kinda works… but it’s completely ignoring the max-width: 1200ox; again – see for yourself right here↗

    It’s super weird what’s happening here; usually a centered text block with a max-width is a very easy thing to do, but I’m completely at loss what that CSS does and why it does it… 😔 might be due to the rather complex nature of the gridder?

    Any help is more than appreciated!!

    posted in General Discussion read more
  • edgrbnz

    +1

    Yeah, that’s probably a bug – the image container seems to be slightly bigger than the image itself. That’s why the background colour still shows in your example even though the image has been loaded.

    The coolest solution would be to fade out the placeholder colour as soon as the images have been loaded. That might be a bit tricky to do, though… because the site needs to know when the images are ready.

    But if that’s possible that would fix all the issues regarding the placeholder colours I read about in the forums. E.g. images with transparencies would also benefit from the solution described above.

    I guess @mariusjopen or @arminunruh might have some tricks up their sleeves 😉

    posted in Bug Reports read more
  • edgrbnz

    It seems to work again!

    Thank you 💐 Lay People 💐!

    posted in General Discussion read more
  • edgrbnz

    Hi @mariusjopen
    that also didn’t work as expected… the column-wrap unfortunately messed up the layouts on all the other pages and the text box was sticking to the top of the page. I tryed some stuff with vertical-align: middle; which didn’t work either.

    I came up with this solution based on your CSS which kind does the trick:

    ._center-1200.no-parallax.no-offset.col.push-1.span-10.align-middle{
        width: initial !important;
        max-width: 1200px;
        margin-top: 40vh;
        margin-left: auto !important;
        margin-right: auto !important;
        padding: 0 5% 0 5%;
        position: relative !important;
        left: initial !important;
    }
    

    It looks fine for almost desktop resolutiona. Unfortunately the text ist moving upwards when the viewport get’s smaller. So it sticks to the header in a tablet resolution ~ 1024×768 which kinda looks wrong…
    If you got any constructive criticism and tipps to fix that I’m happy to learn!

    posted in General Discussion read more
  • edgrbnz

    Hey @mariusjopen
    I just checked to make sure – No, there’s only very little custom CSS, none of that could possibly interfere with the burger as far as I can see:

    Custom CSS

    /*footer links*/
    
    #footer-region a {
        border-bottom: none !important;
    }
    .scrolltotop p:hover {
        color: #efcece !important;
    }
    
    
    /*caption styling*/
    
    .caption {
        margin-top: 4px;
    }
    .caption a{
        border-bottom: none;
    }
    

    Custom CSS for Desktop Version

    /*max-width & alignments*/
    
    ._center-block{
        max-width: 1440px;
        margin: auto!important;
    }
    ._center-1200{
        max-width: 1200px;
        margin: auto!important;
    }
    

    Thank you very much for checking!
    Talk soon!

    posted in Bug Reports read more
  • edgrbnz

    Hi there @arminunruh and @mariusjopen,
    I think I found a 🐞 with the mobile menues (sorry! 🙈):

    I deactivated the Mobile Menu Bar on this site and the burger jumped to a different position as it was in the same layout with the visible Mobile Menu Bar.
    I searched for an option to alter the placement of the burger but couldn’t find anything…

    Here are some screenhots w/ notes:
    0_1573085548309_Unbenannt-1.jpg

    Is there a way to fix this / get this fixed?
    Thanks in advance!!

    posted in Bug Reports read more
  • edgrbnz

    It’s still qTranslate interfering here I guess…

    qTranslate seems to add a http:// in front of that mailto. Since that’s not https:// this also makes the connection to your site to be rated as not fully secure :
    0_1573041077276_24825470-80c4-4ed6-8516-91fd22ccc416-image.png

    I’d deactivate qTranslate and stick with English for now 🙃


    That would be my advise anyway:

    As long as your site isn’t a shop or has a huge amount of sophisticated writing I’d always recommend to go international (aka. English) and drop the chore of maintaining a multi language site. You also may need a cookie banner since (I presume) qTranslate uses cookies to remember the visitors language.

    posted in Bug Reports read more