Forum Replies Created

Viewing 30 posts - 1 through 30 (of 31 total)
  • Author
    Posts
  • Great!
    Is there anyway for the menubar to be fixed at top and let the header disapear like it does in desktop mode?

    Remove the snippet and changed some other code and now it looks fine.
    Guess I’ll have to live with the fact I can’t get the header to be fixed on all mobile platforms.

    Regards

    Yeah I can see that it works much better without that snippet. It’s wierd though as it has been working fine just until recently.?
    So what’s your suggestion to solve the mobile menu issue?

    Seems that android/chrome is the only browser I can where this occures. Works like a charm on an iPhone…

    Well that’s not it… The emulator actually worked fine yesterday, but not the page on my smartphone..
    In my previous reply I provided you with a http-link to a image which I screen captured from my Samsung S5 -which shows the problem…

    When I press to mobile menu so it opens, the image/logo along with the header content jumps to the right.
    BUT if I click a menu with a sublink, it corrects it self and moves back to left (where it’s suppose to be) just as it does when I click to close the menu…

    My opinion is that the problem therfor should be connected in some way, to the logo/image or the header information as all of this started from the moment when I added the code provided from here:
    https://kriesi.at/support/topic/change-order-of-header-elements-i-mobile-view/

    Thanks!

    • This reply was modified 8 years, 3 months ago by Sunique.

    See message

    Hey!

    See attached information!

    in reply to: Change order of header elements i mobile view #639317

    That pretty much did it, You may close the subject!
    Thank you!

    Changed some value, so my code looks like this:

    
    @media only screen and (max-width: 767px){
    .responsive .phone-info {
        position: absolute;
        top: 0px;
        left: 0px;
        width: 50% !important;
    }
    
    #header_meta .sub_menu>ul {
        position: absolute !important;
        top: 30px;
        width: 100%;
    }
    #header_meta {
        min-height: 60px !important;
        }
    }
    in reply to: Change order of header elements i mobile view #639198

    Use this instead

    in reply to: Change order of header elements i mobile view #639197

    Sorry about that! You can find it at: businessolutions.se

    Your absolutely correct! Silly me! :/
    You may close this subject!

    in reply to: Error fetching content #638728

    Hi again,

    After the FTP update it seems that all new pages that I create can be re-edited which is Great news!
    I am/ I was still not able to edit the old “faulty” pages, so I worked my way around it and created new pages, copied the text from the faulty ones, saved and thereafter had a new version of the page. I then deleted the faulty ones and I now don’t get the same message!

    I guess the update didn’t apply instantly for some reason, but it worked by it self the day after.

    The reason why I asked what countries you work from, is that wordfence don’t have the possibility to save country block settings as a template.

    You may close the subject! Thank you!

    in reply to: Error fetching content #636840

    I guess help is no where to be found? Thanks for nothing.

    in reply to: Error fetching content #635198

    That’s what I did the first time…
    I took a backup of the enfold theme-folder, deleted the theme folder on my FTP-side and uploaded a new folder named enfold.
    Which I got by extracting the themefolder file.

    So what I understand now, is that you want me just to OVERWRITE existing files instead (according to the video)?

    Correct?

    UPDATE 1: Just performed the FTP-update according to the video, it didn’t solve the issue… :(
    UPDATE 2: As mentioned before I can edit SOME old pages, only some pages, and all new pages…?
    I’ve narrowed it down to that EVERY PAGE CREATED FROM 2016-02-17 is giving me the error message.
    All pages created prior that date works fine… so WHAT IS GOING ON!?!

    • This reply was modified 8 years, 3 months ago by Sunique.
    in reply to: Error fetching content #635173

    Any new ideas?

    I’m rRunning the latest WP & enfold version, but editing existing pages which contains text-fields that was created with enfold layout composer is not possible. Still returns “Error fetching content”.

    I can create a NEW text field, but after it is saved I can’t edit it…
    Please advise as I need to update a lot of pages which simply isn’t possible right now! :/

    in reply to: Error fetching content #633742

    UPDATE
    If I hover the child theme link, I get a link that looks like this:

    
    http://businessolutions.se/wp-admin/admin.php?page=avia

    But if I change the link to:

    
    http://businessolutions.se/wp-admin/admin.php?avia_welcome=true&page=avia

    it works fine...

    So what’s missing !?

    EDIT/UPDATE:
    The new framework/shortcodes.php files looked like this from row 29:

    class avia_shortcodes{
    	
    	function __construct() {
    		
    		add_action( 'admin_init', array( &$this, 'action_admin_init' ) );
    		add_action( 'wp_ajax_scn_check_url_action', array( &$this, 'ajax_action_check_url' ) );
    		add_action( 'admin_print_scripts', array( &$this, 'extra_shortcodes' ),20);
    		add_action( 'admin_print_scripts', array( &$this, 'extra_styles' ),20);
    		add_action( 'admin_print_scripts', array( &$this, 'avia_preview_nonce' ),20);
    	}
    	

    But the old one looked like this:

    class avia_shortcodes{
    	
    	function avia_shortcodes() {
    		
    		add_action( 'admin_init', array( &$this, 'action_admin_init' ) );
    		add_action( 'wp_ajax_scn_check_url_action', array( &$this, 'ajax_action_check_url' ) );
    		add_action( 'admin_print_scripts', array( &$this, 'extra_shortcodes' ),20);
    		add_action( 'admin_print_scripts', array( &$this, 'extra_styles' ),20);
    		add_action( 'admin_print_scripts', array( &$this, 'avia_preview_nonce' ),20);
    	}
    	
    

    I changed the value to the old one and now that part works… But still not to edit pages (specifically t the text modules..

    • This reply was modified 8 years, 3 months ago by Sunique.
    in reply to: Error fetching content #633741

    What country do you need access from?

    in reply to: Error fetching content #633740

    I’ve updated to enfold 3.5.4 now. But have run into some new problems.
    If the theme it self is used, theme settings works fine EDIT: Enfold theme settings is not working unless I manually enter the adress: http://businessolutions.se/wp-admin/admin.php?avia_welcome=true&page=avia (as stated in a later post). If I do so I can enter the theme settings and see that I’m running 3.5.4.
    If I don’t enter the page adress manually the theme returns the following errors…

    Warning: require(/home/busines4/public_html/wp-content/themes/enfold/framework/php/avia_shortcodes/shortcodes.php): failed to open stream: No such file or directory in /home/busines4/public_html/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 149
    
    Fatal error: require(): Failed opening required '/home/busines4/public_html/wp-content/themes/enfold/framework/php/avia_shortcodes/shortcodes.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/busines4/public_html/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 149

    The webpage still works but like I said, I cant’t enter the theme settings.
    Trying to edit a page using enfold page builder is still not working either…
    Error fetching content - please reload the page and try again

    Where do we go from here!?
    Re-installing WP 4.5.2. didn’t seem to help either? I used the reinstall-button located under Panel->updates->”Re-install now”..

    • This reply was modified 8 years, 3 months ago by Sunique.
    in reply to: Error fetching content #633607

    Sorry about that, most common countries are not blocked. I’ll turn it off for a while.
    Let me know when you have looked at it!

    I’ll try to update during update everthing within this hour!

    //Jimmy

    in reply to: Error fetching content #632565

    Hi!

    So where do I get the Theme update?
    In Enfold theme settings there’s no update – I’ve also checked manually?!

    in reply to: Error fetching content #632497

    Nothing? :(

    in reply to: Error fetching content #632049

    Vinay,

    Login information was provided in the original post.. :)

    I’ve reinstalled wordpress 4.5.2.but there’s no update for enfold to 3.5.4?
    I’ve checked manually and at themeforest..??

    Didn’t help to reinstall wp… any more suggestions?

    Thanks!
    //Jimmy

    in reply to: Child theme style.css code not applying -but quick-css does #539039

    Hi again,

    It’s not a caching issue as that has been done multiple times and I’ve also tried from other units as well.

    Also, what is wrong with this code?
    I want to use hyphens when the screen resolutions is below let say 1050px since my headers are a bit big/long for smaller screens.
    The goal is to transform the H1 headers primarly for tablets and shrink the size from 36.1 to approx. 24.

    @media only screen and (max-width: 1050px) {
     .template-page .entry-content-wrapper h1 { 
    font-size: 24px !important;
      	word-break: break-all;
      	-webkit-hyphens: auto !important;
    	-moz-hyphens: auto !important;
      	-ms-hyphens: auto !important;
      	hyphens: auto !important;
    
     }
    }

    If I use the code below, it works fine, but it doesn’t take the screen resolutions in mind (obviously)

    h1 { 
    font-size: 24px !important;
    font-size: 24px !important;
      	word-break: break-all;
      	-webkit-hyphens: auto !important;
    	-moz-hyphens: auto !important;
      	-ms-hyphens: auto !important;
      	hyphens: auto !important;
    }
    in reply to: Child theme style.css code not applying -but quick-css does #536413

    Hi Eliott,

    I use the enfold theme, pretty much out of the box.
    Nothing in quick-css, I’ve put everything in the style.css in my child theme instead to have it all gathered in one place!

    My style.css looks like this at the moment.. I’m aware it could be more structured but that will be done when all coding is finished.

    
    */ ÄNDRA TREDJEMENYN */
    #top .av-main-nav ul ul {
      	left: 207px !important;
        box-shadow: 1px 1px 1px 1px rgba(0, 0, 0, 0.6) !important;
        border-left: 1px solid rgba(0, 0, 0, 0.8)!important;
        border-top: 1px solid rgba(0, 0, 0, 0.9)!important;
    }
    
    */ MODIFIERA FONTER */
    #top #wrap_all .main_color h3 {
        margin-bottom: 3px !important;
        margin-top: 25px !important;
    }
    
    p { margin-top: 0px !important; }
    
    .active_tc.toggle_wrap {line-height:1.3em !important }
    
    .toggle_icon {
      width:15px !important;
      height:15px !important;
      top:15px !important; 
      }
    
    */ Dela Blogginlägg */
    .avia-related-tooltip {
      width:200px !important;
      box-shadow: 0px 1px 5px 0px rgba(0, 0, 0, 0.1) !important;
    }
    
    */ BLOGG-LAYOUT */
    .widgettitle { font-weight:400 !important }
    .template-blog .post_delimiter { border-bottom: 1px dotted #E1E1E1 !important }
    
    #top .av-main-nav ul a {
      text-transform:uppercase !important;
      line-height:2em !important; 
    }
    
    #top #header .av-main-nav > li > a {
      font-size: 14.1px !important;
      font-weight:normal !important;
      }
    
    #top #header .av-main-nav > li > a:hover {
      font-size: 14.1px !important;
      font-weight:normal !important;
      color:#00A9E0 !important;
      }
    
    #top .av-subnav-menu  { 
      color: #222222 !important; 
      font-size:14.1px !important;
      font-weight:normal !important;
      line-height: 2em !important;
      text-transform: uppercase !important;
    }
      
    .av-main-nav > li > ul {
     box-shadow:0px 1px 1px 1px rgba(0, 0, 0, 0.5);
     }
    
    #top .av-submenu-container { z-index: 99!important; }
    .main_menu {text-transform:uppercase;}
    
    .flex_column .widget .widgettitle, .content .widget .widgettitle {
      margin-top: 0.85em;
    	padding-bottom: 8px !important;
      margin-bottom: 18px !important;
      	border-bottom: 1px solid rgba(255,255,255,0.6);
      }
    
    .footer_color div { line-height: 1.4 }
      
    #top .news-content { padding:0px 3px 10px 0px !important }
    
    .main_color td,
    .main_color tr, 
    .main_color th,
    .main_color td{
      border:none !important;
      font-size:15.1px;
      margin: 0px;
    	padding: 0px 0px 4px;
      }
    
    .avia_textblock {
        font-weight: 300 !important;
        line-height: 1.5em !important;
        font-size: 15.1px !important;
      }
    
    p {
      font-weight:300;
      line-height: 1.5em (26.4px);
      vertical-align: baseline;
      letter-spacing: normal;
      word-spacing: 0px;
      }
    
    */ MOBILMENY- STYLING */
    #mobile-advanced li > a::before, 
    .html_header_mobile_behavior #mobile-advanced span > a::before, 
    #mobile-advanced .mega_menu_title::before {
        content:"";}
    
    .av-special-heading .av-special-heading-tag {
      font-size:30px;
      padding-bottom:30px !important;
      }
        
    #header_main, #header {
    border-bottom-color: #FFFFFF !important;
    z-index:9999 !important;
    box-shadow: 0px 2px 5px 0px rgba(0, 0, 0, 0.6) !important;
     }
    
    .avia-layerslider {
        border-top-style: solid;
        border-top-width: 1px;
        overflow: hidden;
        z-index: 999 !important;
        box-shadow: 3px 5px 7px rgba(0, 0, 0, 0.8) !important;
      }
    
    @media only screen and (max-width: 768px) 
    { .logo a { overflow:visible!important; }}
    
    /* BLOGGPOSTRUBRIK */
    #top .fullsize .template-blog .post-title{
    text-align: left !important;
    max-width: 100%;
    }
    
    .toggle_icon {
    border: 0px !important
    }
    
    /* DÖLJ ÖVERLAY*/
    .image-overlay {
     visibility: hidden; 
    }
    
    /* ------- ACCORDION BÖRJAR ------- */
    /* MENYNS LAYOUT */
    .main_color .toggler {
    background: #c4e1f2 !important;
    color: #404040 !important;
    border: none !important;
    }
    
    /* VID HOOVRING AV MENY */
    .main_color .toggler:hover { 
    background: #ebf1f4 !important;
    color: #404040 !important;
    border-color: #EFEFEF !important; 
    border: px;
     }
    
    /* INNEHÅLLET - CONTENT */
    .main_color .toggle_content {
    background-color: #FFFFFF !important;
    border-color: #EFEFEF !important;
    }
    
    /* BLOGG-POST-BREDD */
    #top .fullsize .template-blog .post .entry-content-wrapper > *, #top .fullsize .template-blog .post .entry-content-wrapper { max-width: 100%; }
    
    @media only screen and (min-width: 768px) {
    div.comment-entry.post-entry {
        width: 80%;
        margin: 0 auto;
    }}
    
    /* TA BORT BLOGG-IKONEN */
    .single .blog-meta { display: none!important; }
    .rounded-container .iconfont, .small-preview .iconfont { display: none; }
    .template-blog .blog-meta, .multi-big .post_author_timeline, .single-small .post_author_timeline { display: none; }
    
    /* Horisontell kantlinje på expandera-ikonen */
    .toggle_icon, .toggle_icon .hor_icon { 
    border-color: #9B9B9B !important; }
    
    /* Vertikal kantlinje på expandera-ikonen */
    .toggle_icon .vert_icon { 
    border-color: #9B9B9B !important; }
    
    /* Phone info */
    .phone-info a { color: #039ed2 !important; }
    .phone-info a:hover { color: #039ed2 !important; }
    
    #footer .widget a { color: #FFF !important; }
    #footer .widget hover { color: #039ed2 !important; }
    
    /* Förändra miljön för submenyn */
    
    #header .avia_mega_div .units {
    border-right-style:none; 
    }
    
    #top #header .mega_menu_title a {
    font-size:15px;
    text-transform:uppercase;
    margin-bottom:
    }
    
    #top #header .avia_mega_div > .sub-menu {
    background-color:#FFF;
    text-transform:uppercase;
    }
    
    #top #header .avia_mega_div > .sub-menu a:hover { background-color:#FFF; }
    #top #header .avia_mega_div > .sub-menu > li > ul { margin-left:10px; }
    #top #header .avia_mega_div > .sub-menu > li > ul > li a { padding: 0; }
    
    /* Förändra mobilmenyn */
    #mobile-advanced, #mobile-advanced a, #mobile-advanced .mega_menu_title {
    background-color:#FFF;
    border-color:#F5F5F5;
    }
    
    #mobile-advanced li > a:hover, .html_header_mobile_behavior #mobile-advanced span:hover, .html_header_mobile_behavior #mobile-advanced span:hover a {
    background-color:#00A9E0
    }
    
    #advanced_menu_toggle:hover, .avia_desktop #advanced_menu_hide:hover {
    background-color:#00A9E0;
    border-color:#00A9E0;
    color:#FFF;
    }
    
    #advanced_menu_toggle, #advanced_menu_hide { border:none }
    #mobile-advanced > li:first-child > a:first-child { border:none }
    
    .avia_desktop #advanced_menu_toggle:hover, .avia_desktop #advanced_menu_hide:hover { 
    background-color:#00A9E0;
    border-color:#00A9E0; }
    
    #mobile-advanced { 
    padding:64px 0px;
    top:63px;
    }
    
    #advanced_menu_hide {
    top:99px;
    right: 30px;
    }
    
    /* Ta bort border på social widget */
    #top #wrap_all .social_bookmarks, #top #wrap_all .social_bookmarks a, #top #wrap_all .social_bookmarks li {border:none; }
    
    /* Webshopsikon */
    #top #wrap_all .av-social-link-Webshop:hover a{color:#fff; background-color:#00A9E0; }
    
    .responsive #header_meta .social_bookmarks li { border-width:0px; }
    .responsive #top #header_meta .social_bookmarks li:last-child {border-width:0px; }
    
    .header_bg { opacity:1; }
    
    #header .twelve.units { 
    width: 800px !important;
    box-shadow:0px 1px 3px 0px #333; 
    }
    
    .header-scrolled .logo img {
    padding-top: 3px;
    padding-bottom: 3px;
    }
    .logo img {
    padding-top: 3px;
    padding-bottom: 3px;
    }
    
    .main_color .special-heading-inner-border { border:none }
    body .av-special-heading .av-special-heading-tag { font-weight:300 }
    
    #top select, #top .avia_ajax_form .select, #top .entry-content-wrapper select 
    {
    	padding:10px 10px;
    	box-shadow:inset 1px 1px 5px rgba(0, 0, 0, .05);
    	background:#FFFFFF;
    	border:#EEE 1px solid;
    	color:#999;
    	font-size:13px;
      	width:100%;
      	margin-right: 20px;
      }
      
    #top input[type="text"], 
    #top input[type="email"],
    #top input[type="password"],
    #top input[type="tel"],
    textarea {
    	padding:10px 10px;
    	box-shadow:inset 1px 1px 5px rgba(0, 0, 0, .05);
    	background:#FFFFFF;
    	border:#EEE 1px solid;
    	color:#999;
    	font-size:13px;
      	width:100%;
      	margin-right: 20px;
    }
    
    @media only screen and (max-width: 767px) {
    	.responsive #top #header {
             position: fixed !important; }
    }
    
    @media only screen and (max-width: 768px) {
    .logo, .logo a, .logo img { max-height: 70px!important; }}
    
    @media only screen and (max-width: 767px) {
    	.responsive #top #main { margin-top:135px }
    }
    
    .menu li > a:after,
    . {
        color: #000;
        content: ' ▾';
    }
    
    .menu li > a:only-child:after {
        content: '';
    }
    
    #mobile-advanced ul a, #mobile-advanced .mega_menu_title {
    text-transform:uppercase;
    color:#5bc2e7; 
    }
    
    #mobile-advanced li > a::before, 
    .html_header_mobile_behavior 
    #mobile-advanced span > a::before, 
    #mobile-advanced .mega_menu_title::before { content:none;}
    
    */ LAYERSLIDER SHADOW */
    .avia-layerslider {
      box-shadow: 5px 8px 5px rgba(0, 0, 0, 0.3) !important;
      position: relative !important;
      z-index: 9999 !important;
    }
    
    .main_color strong { color:inherit !important }
    • This reply was modified 8 years, 9 months ago by Sunique.
    in reply to: How to add Roboto font #523307

    Now when I look at the page, it’s not the font being rendered.
    If I choose Open Sans as my body font, thats both chosen and rendered, but choosing Roboto renders Helvetica.. :/

    Please advise!

    • This reply was modified 8 years, 10 months ago by Sunique.
    in reply to: How to add Roboto font #523306

    I would also like to use Roboto as my body font, but there’s no option for that in the droplist, how can I fix it? :/

    in reply to: Unstick topbar -not working #519949

    Andy,

    I hope that’s something that could show up in future releases as a fully responsive site should work the same way in many areas regardless of the users device.
    I’ve sticked the menu in responsive mode now, but it includes the topbar. Looking into the page’s html and css it seems that the topbar doesn’t have a ready function to style it below @767 pixels… YET! :)
    Thanks for your reply. If you leave this thread open for 10days it will give me space to post a solutions for other enfold-users. :)

    in reply to: Enfold builder not working properly #519925

    Hi again, sorry for a late reply.

    That page “OM-OSS” (meaning “about us” in swedish) only contains a header some text and one picure
    ( a part from the menu and footer). What’s loading?

    When it comes to the CSS-files and Open Sans font, it should be used everywhere but I’ll take a look at the files.

    Gtmetrix.com wants me to combine the CSS-files (22 files) into (1) one css-file instead to speed up the page (which i think is WAY TO SLOW). Do I need to re-do the theme files then?
    GTmetrix.com also reflex over the a lot of different javascript files that also should be combined into fewer ones.??

    Anything else u see that makes our page load so slow.

    in reply to: Enfold builder not working properly #517531

    Just deleted the old enfold-theme (enfold2) and yes, u may deactivate plugins as you go.. :)

    in reply to: Enfold builder not working properly #517513

    Sure!

    in reply to: Enfold builder not working properly #517477

    Hey Yigit,

    I just update like 2 days ago. It’s been like this since we purchased the page incl. the theme from our previous webdesigner (1½ year ago)
    We now run it by our self, I just purchased a license myself, but the problem is still there.

    I run version 3.3.2 and everything is flushed.
    I’ve also reinstalled a new version of enfold, naming the old theme one to enfold2 (the old designer edited the original files…).
    Is there any plugin known plugin that could create this error?

Viewing 30 posts - 1 through 30 (of 31 total)