Forum Replies Created

Viewing 30 posts - 4,651 through 4,680 (of 11,513 total)
  • Author
    Posts
  • in reply to: Bleeding a box to the end of the screen #1260017

    but please try the second solution. It seems the better one for responsive case:

    #fullwidth-content .container .content {
      vertical-align: top !important;
    }
    
    #fullwidth-content .post-entry {
        position: relative;
        top: 5%;
    }
    
    #fullwidth-content .container {
      max-width: 100%;
      width: 100% !important;
      padding: 0 !important;
      margin: 0 !important;
    }
    
    #fullwidth-content .flex_column.first {
      width: 55%;
      padding: 20px 20px 10px 10vw;
      background: rgba(255,255,255,0.7);
      position: relative;
      float: left;
    }
    
    #fullwidth-content .flex_column.avia-builder-el-last {
      position: relative;
      float: left;
      width: 30%;
    }
    
    @media only screen and (max-width: 767px) {
      #fullwidth-content .flex_column.avia-builder-el-last {
        float: none;
        width: calc(100% - 100px) !important;
        margin: 0 50px !important;
      }
      #fullwidth-content .flex_column.first {
        float: none;
        width: calc(100% - 50px) !important;
        margin-right: 50px
      }
    }
    in reply to: Bleeding a box to the end of the screen #1260013

    hm ?

    in reply to: Button #1259864

    or do you mean this “sticky” behavior: https://webers-testseite.de/sticky-elements/

    in reply to: Button #1259858

    you can see that example on nearly most of enfold pages that have longer content: the scroll-top link is a button that is in fixed positon.
    Fixed positioning needs position values ( top, bottom, left or right)

    so first give a custom-class or unique ID to that button element: in my case it is ID: fixed-button
    f.e. to quick css:

    #fixed-button.avia-button-wrap {
        position: fixed;
        left: 50px;
        bottom: 50px;
        z-index: 1050;
    }

    but my advice would be to place a button via button shortcode outside wrap_all container by child-theme functions.php.
    There is a hook : ava_after_body_opening_tag that can be used for it.
    ( this is site-specific only for my testpage – adjust page-id to your needs):

    add_action('ava_after_body_opening_tag', function() {
        if(is_page(457)){
          echo do_shortcode("[av_button label='fixed-button' icon_select='yes' icon='ue800' font='entypo-fontello' link='manually,http://' link_target='' size='large' position='center' label_display='' title_attr='' color_options='color_options_advanced' color='theme-color' custom_bg='#444444' custom_font='#ffffff' btn_color_bg='aqua' btn_custom_bg='#444444' btn_color_bg_hover='blue' btn_custom_bg_hover='#444444' btn_color_font='custom' btn_custom_font='#ffffff' id='fixed-button' custom_class='' av_uid='av-khd9fkov' admin_preview_bg='']");
        }
    });

    see here f.e.: https://webers-testseite.de/impressum/ left bottom corner

    in reply to: Bleeding a box to the end of the screen #1259819

    this is css for the possibility to have a neightbour container to that “flag” on the left
    second color-section got a unique ID : fullwidth-content2

    #fullwidth-content2 .container .content {
      vertical-align: top !important;
    }
    
    #fullwidth-content2 .post-entry {
        position: relative;
        top: 20%;
    }
    
    #fullwidth-content2 .container {
      max-width: 100%;
      width: 100% !important;
      padding: 0
    }
    
    #fullwidth-content2 .flex_column.first {
      width: 55%;
      padding: 20px 20px 10px 10vw;
      background: rgba(255,255,255,0.7);
      min-height: 150px;
      position: relative;
      float: left;
    }
    
    #fullwidth-content2 .flex_column.avia-builder-el-last {
      position: relative;
      float: left;
      width: 30%;
    }
    
    @media only screen and (max-width: 767px) {
      #fullwidth-content2 .flex_column.avia-builder-el-last {
        float: none;
        width: calc(100% - 100px) !important;
        margin: 0 50px !important;
      }
      #fullwidth-content2 .flex_column.first {
        float: none;
        width: calc(100% - 50px) !important;
        margin-right: 50px
      }
    }
    in reply to: Bleeding a box to the end of the screen #1259816

    Layout – or similar :

    give a custom class or in my case a unique ID to the color-section: fullwidth-content
    then to quick css:

    #fullwidth-content .container {
      max-width: 100%;
      width: 100% !important;
      padding: 0
    }
    
    #fullwidth-content .flex_column.first {
        width: 55%;
        padding: 20px 20px 10px 10vw;
        background: rgba(255,255,255,0.7);
        min-height: 150px;
        position: absolute;
        top: 20%;
    }

    see example page: https://webers-testseite.de/rmatus/

    in reply to: How to remove H3 in Slider accordeon #1259705

    if you open the icon-box Element you do not have 3 General Tabs on top ( see screenshot above )
    Content, Styling and Advanced !

    on default the option is not activated ( “Hide template builder developer options” ) – see dashboard – Enfold – Layout Builder:
    https://kriesi.at/documentation/enfold/intro-to-layout-builder/#developer-options

    in reply to: How to remove H3 in Slider accordeon #1259610

    yes that is the normal way.

    but if you had to change it on many pages / post all headings at once this will be the best and fastest way to do it.

    in reply to: How to remove H3 in Slider accordeon #1259521

    Just for info: some ALB Elements got extra-args for that filter – so you can influence f.e. on timeline.php the date and the title headings
    Date is on default : h2 – and the title is h4
    if you want to influence those ALB Elements with extra args you had to do following:

    function my_avf_customize_heading_settings( array $args, $context, array $extra_args = array() ){
      //so here comes the extra_arg date with that filter 
      if( $context == 'avia_sc_timeline' && is_array( $extra_args ) && in_array( 'date', $extra_args ) ) {
        $args['heading'] = 'h3';            
        $args['extra_class'] = 'my-timeline-date-class';   
      }
      //so here comes the extra_arg title with that filter
      if( $context == 'avia_sc_timeline' && is_array( $extra_args ) && in_array( 'title', $extra_args ) ) {
        $args['heading'] = 'h1';            
        $args['extra_class'] = 'my-timeline-title-class';   
      } 
      return $args;
    }
    add_filter( 'avf_customize_heading_settings', 'my_avf_customize_heading_settings', 10, 3 );
    in reply to: How to remove H3 in Slider accordeon #1259518

    @Nikko
    https://kriesi.at/support/topic/how-to-remove-h3-in-slider-accordeon/#post-1202501

    this was new to my – and a look to source code is right – the filter ( avf_customize_heading_settings ) is indeed part of this on line 875:

    if ( ! class_exists( 'aviaccordion' ) ) 
    

    if i use the filter i always took as victoria intends to do the context from the beginning:

    if ( ! class_exists( 'avia_sc_slider_accordion' ) )
    

    it seems to be a specific thing for accordion slider !


    @mtrebbi
    the iconbox has on top of the alb source code:

    if ( ! class_exists( 'avia_sc_icon_box' ) )
    

    so context of the filter is : avia_sc_icon_box
    only the title is set with conjuction to that filter – so this will be enough:

    function my_heading_settings_for_iconbox( array $args, $context, array $extra_args = array() ) {
      if( $context == 'avia_sc_icon_box') {
        $args['heading'] = 'h1';            
        $args['extra_class'] = 'my-iconbox';  
      } 
      return $args;
    }
    add_filter( 'avf_customize_heading_settings', 'my_heading_settings_for_iconbox', 10, 3 );

    the extra_class you can set by yourself – it is only for additonal Styling Options.

    in reply to: ?iframe=true custom dimensions (width and height) #1259137

    the max-width is set on :

    .mfp-iframe-holder .mfp-content {
        line-height: 0;
        width: 100%;
        max-width: 900px;
    }

    so set on quick css f.e.

    .mfp-iframe-holder .mfp-content {
        max-width: 80vw;
    }
    • This reply was modified 4 years, 8 months ago by Guenni007.
    in reply to: Spracheinstellung ändern #1259136

    sollte – wenn du auch die deutsche WordPress Version installiert hattest eigentlich automatisch so sein.
    Sonst geh bitte und schau unter Dashboard – Settings – General nach ob du dort umstellen kannst. : “Site Language”
    Wenn du dort nicht auf Deutsch ( Sie oder Du) umstellen kannst, musst du für WordPress die Sprachfiles nachinstallieren.

    in reply to: Element color stretch to left or right side of viewport #1258652

    and for the breakpoint for responsive case ( in my case it is 990px ):

    @media only screen and (max-width: 989px) {
      .gridcontent-special .flex_cell {
        padding-left: 50px !important;
      }
      
      .gridcontent-special .flex_cell {
        padding-right: 50px !important;
      }  
    }
    in reply to: Element color stretch to left or right side of viewport #1258650

    with custom-class on grid-row element : gridcontent-special

    @media only screen and (min-width: 1510px) {
      .gridcontent-special .flex_cell.avia-builder-el-first {
        padding-left: calc((100vw - 1510px)/2 + 50px) !important;
      }
      
      .gridcontent-special .flex_cell.avia-builder-el-first {
        padding-left: calc((100vw - 1510px)/2 + 50px) !important;
      }  
      
      .gridcontent-special .flex_cell.avia-builder-el-last {
        padding-right: calc((100vw - 1510px)/2 + 50px) !important;
      }  
    
      .gridcontent-special .flex_cell.avia-builder-el-last {
        padding-right: calc((100vw - 1510px)/2 + 50px) !important;
      }
    }
    
    @media only screen and (max-width: 1509px) {
      .gridcontent-special .flex_cell.avia-builder-el-first {
        padding-left: 50px !important;
      }
      
      .gridcontent-special .flex_cell.avia-builder-el-first {
        padding-left: 50px !important;
      }  
      
      .gridcontent-special .flex_cell.avia-builder-el-last {
        padding-right: 50px !important;
      }  
    
      .gridcontent-special .flex_cell.avia-builder-el-last {
        padding-right: 50px !important;
      }
    }
    in reply to: Element color stretch to left or right side of viewport #1258648

    see now with new css above:
    https://webers-testseite.de/grid-again/

    in reply to: Element color stretch to left or right side of viewport #1258637

    for my setting 1510px and 50px setting on Grid-Cell padding overall:
    ( Sorry this for my page id specific – remove it or replace it to your IDs – or even better give to the grid-row a custom-class )

    @media only screen and (min-width: 1510px) {
      .flex_cell.avia-builder-el-first {
        padding-left: calc((100vw - 1510px)/2 + 50px) !important;
      }
      
      .flex_cell.avia-builder-el-first {
        padding-left: calc((100vw - 1510px)/2 + 50px) !important;
      }  
      
      .flex_cell.avia-builder-el-last {
        padding-right: calc((100vw - 1510px)/2 + 50px) !important;
      }  
    
      .flex_cell.avia-builder-el-last {
        padding-right: calc((100vw - 1510px)/2 + 50px) !important;
      }
    }
    
    @media only screen and (max-width: 1509px) {
      .flex_cell.avia-builder-el-first {
        padding-left: 50px !important;
      }
      
      .flex_cell.avia-builder-el-first {
        padding-left: 50px !important;
      }  
      
      .flex_cell.avia-builder-el-last {
        padding-right: 50px !important;
      }  
    
      .flex_cell.avia-builder-el-last {
        padding-right: 50px !important;
      }
    }

    see: https://webers-testseite.de/grid-row-layout/

    the 1/1 Container shows you the standard of 1510px width on my setting.

    • This reply was modified 4 years, 8 months ago by Guenni007.
    in reply to: Element color stretch to left or right side of viewport #1258600

    Take the grid-row element and set your 2/3 – 1/3 grid cell settings – one of those paddings had to be in relation to screen width
    you had to set a calculated relative padding left or right ( depends if your 2/3 grid cell is on the left or right ) – and only set the rules for screen-width less than 1400px ( your 1340px + 2x30px (if this is the alb padding setting ) case if you like to preserve a left / right padding of your alb setting ( in my case 30px )
    on responsive case Enfold has its own rules for padding.

    @media only screen and (min-width: 1400px) {  /*** it depends on your setting on the alb - i got 30px on all sides : 1340px + 60px ***/
      .flex_cell.avia-builder-el-first {
        padding-left: calc((100vw - 1340px)/2) !important;
      }
      
      .flex_cell.avia-builder-el-first {
        padding-left: calc((100vw - 1340px)/2) !important;
      }  
      
      .flex_cell.avia-builder-el-last {
        padding-right: calc((100vw - 1340px)/2) !important;
      }  
    
      .flex_cell.avia-builder-el-last {
        padding-right: calc((100vw - 1340px)/2) !important;
      }
    }

    these rules can be used for all grid-cell sizes because only the first and last are selected!

    See example page with 1/2 grid-cell size – but it is the same rules as above ( i have 1510px standard setting for content)
    https://webers-testseite.de/grid-row-layout/

    in reply to: Auto Added Paragraph Tags #1258583

    Kann sein, dass du
    a) das Merging der css und js files: Unter Enfold / Leistung: “Alte CSS- und JS-Dateien löschen?” erneuern musst
    b) den Browsercache refreshen musst #
    und c) natürlich darfst du nicht erwarten, das alt angelegte Layouts sich dadurch verbessern.
    – es werden nur neu erstellte Texte beeinflusst.

    welche p tags stören dich? manchmal werden nämlich auch lästige leere p-tags erstellt.
    da gäbe es eine Lösung für.

    in reply to: Auto Added Paragraph Tags #1258547

    by the way – the line in textblock.php is now on the newest enfold on line 222.
    the wpautop had to be erased – so from

    
    $params['innerHtml'] = "<div class='avia_textblock avia_textblock_style' data-update_with='content'>".stripslashes(wpautop(trim(html_entity_decode( $params['content']) )))."</div>";

    to

    
    $params['innerHtml'] = "<div class='avia_textblock avia_textblock_style' data-update_with='content'>".stripslashes(trim(html_entity_decode( $params['content']) ))."</div>";
    

    if you are working on a child-theme you can have a whole edited textblock.php on your child-theme/shortcodes/ folder by having this little snippet in your child-theme functions.php:

    function avia_include_shortcode_template($paths){
      $template_url = get_stylesheet_directory();
          array_unshift($paths, $template_url.'/shortcodes/');
      return $paths;
    }
    add_filter('avia_load_shortcodes', 'avia_include_shortcode_template', 15, 1);
    • This reply was modified 4 years, 8 months ago by Guenni007.
    in reply to: Icon Grid backside links #1257719

    off topic : it would be nice to have on a backside image link – for the image a title attribute too.
    these images on backside linking to lightbox do not have a title.

    in reply to: Icon Grid backside links #1257542

    ok on an absolute fresh install – it will have effect – but only with pseudo before container setting. But Overlay images are not well placed then.

    with:

    .avia-icongrid-borders-all li .avia-icongrid-wrapper::before, 
    .avia-icongrid-borders-between li .avia-icongrid-wrapper::before {
    	z-index: -1 !important;
    }

    with:

    .avia-icongrid-borders-all li .image-overlay,
    .avia-icongrid-borders-between li .image-overlay {
        left: 0;
        top: 0;
    }

    the overlay are positioned correct on hover.
    These settings are on .image-overlay-inside but that seems to be not enough

    in reply to: Spread main menu across the entire screen? #1257527

    you can try to have here a flexed container – and the li’s as flex-items.
    Try on quick css:

    #avia-menu {
        display: flex !important;
        flex-flow: row wrap;
        justify-content: space-between;
    }

    this could end up in a multi line menu – but i guess the hamburger state will be effective before that happens

    in reply to: Responsive Background Image in Color Section #1257526

    in order to get a responsive background, you have to include the aspect ratio of your image in the height calculation of the container.
    So if you use an image in 16:9 format as a background, set the color-section to this relative height.
    The best way is to give the color-section a custom class or a unique ID like on my test page: https://webers-testseite.de/responsive-colorsection/

    #responsive-bg {
        width: 100vw;
        height: 56.25vw;
    }

    on that the background is perfectly responsive – But what would you like to do if the container height does not offer enough place for the content?

    You have to have on that case less content or totaly responsive content inside that container. That may lead to too small and non legible font-sizes.
    See heading on mobile view f.e 375px screen width.

    in reply to: Icon Grid backside links #1257435

    does not solve my filp-card behavior – i did all hard-refresh i can do.:
    on standard case without the css settings in icongrid.css there are only :before rule – so what should do an :after rule solve?
    – without content, positioning etc. pp for the after-rule there will be no effect only with z-index setting.
    https://webers-testseite.de/flipcards/

    even setting it to !important and replacing the before construction with the after container does not solve it

    and setting the before containers to -1 will work for the links – but then the borders are partially gone ( not seen)

    
    .avia-icongrid-borders-all li .avia-icongrid-wrapper::before, 
    .avia-icongrid-borders-between li .avia-icongrid-wrapper::before {
    	z-index: -1 !important;
    }

    Do you have an example page where your css hack does work ?

    • This reply was modified 4 years, 8 months ago by Guenni007.
    in reply to: Masonry and Blog Posts Grid Behavior #1256287

    With the normal blog functionality, you can specify a page to include the blog. This is done under Enfold : Theme Options.
    Then you can choose between different blog themes – Enfold : Blog Layout.
    There are three predefined styles and some layouts.
    If you choose Gridlayout the whole thing looks like this: https://webers-testseite.de/pureinstall/beitrags-blogseite/
    there are ways to have more than 3 Columns on the Grid-Layout even here or-

    you can also use the Blog-Alb element or the Gallery or Masonry elements to create different layouts without setting the page under Theme-Options.

    in reply to: Best practices for specific build #1256226

    the layout itself is not so hard to style – but the dot-navigation on the left ( or right) it is a bit more complex.
    See here with a lot of code: https://webers-testseite.de/pureinstall/dot-navigation-with-colored-sections/
    Mine has the active section as title and on hover the others

    these “edited Alb Elements” are deprecated.
    Since a lot of these options are now standard from Enfold. Thanks to Günter.

    mir würde schon reichen, wenn du eine analoge Seite in den Demos verlinken könntest.
    z.B. sowas hier: https://kriesi.at/themes/enfold-shop/shop/
    da dort viele der drüberliegenden Container mit overflow: hidden gesetzt sind müsste man das aufheben um den ja aussenliegenden Schatten zu sehen.

    div .products .product a,
    .product .inner_product,
    .product .thumbnail_container, 
    div .products .product a img {
      overflow: visible;
    }
    .woocommerce-LoopProduct-link:hover .attachment-shop_catalog {
      box-shadow: 2px 2px 8px #888;   
    }


    oder
    man gibt dem entsprechenden Container der den Schatten hat soviel margin, dass der Schatten wieder innerhalb desselben liegt:

    .woocommerce-LoopProduct-link .thumbnail_container {
        margin: 10px !important;
    }
    
    .woocommerce-LoopProduct-link:hover .thumbnail_container {
      box-shadow: 2px 2px 8px #333;
      transition: all 0.3s ease;
    }

    liegt meist daran, dass man vergisst den übergeordneten Containern ein overflow: visible zu geben.
    Mit einer Linkseite wäre ein besserer Tip in Form von css code möglich

    in reply to: page-id alternative #1255417

    maybe this little snippet in child-theme functions.php helps you to have on body (#top) the page/post name as new class:

    function add_slug_body_class( $classes ) {
    global $post;
      if ( isset( $post ) ) {
        $classes[] = $post->post_type . '-' . $post->post_name;
      }
      return $classes;
    }
    add_filter( 'body_class', 'add_slug_body_class' );

    f.e.
    a page “Contact” will have then the class at body: page-contact
    a portfolio “news” will get portfolio-news
    etc.

Viewing 30 posts - 4,651 through 4,680 (of 11,513 total)