Forum Replies Created

Viewing 30 posts - 31 through 60 (of 84 total)
  • Author
    Posts
  • Hey Josue,

    Thank you for clearing things up!

    Re Enfold forms I’d like to suggest a feature similar to the Contact Form 7 feature described here: http://www.astralwebinc.com/contact-form-7-wp-how-to-add-event-tracking-on-new-universal-google-analytics/

    The described CF7 feature only triggers the tracking code when a form submissions is valid; pretty neat :) Perhaps such a feature could also work for Enfold buttons.

    Kind regards,

    Ralph

    in reply to: Please clear this up for em (GA Tracking) #398434

    Hey!

    @ people using the Google Analytics by Yoast plugin and @ people looking to test the event / goal tracking code:

    Please check the following post for some additional info: https://kriesi.at/support/topic/track-contact-form-conversions-with-google-analytics-goal/#post-398429

    Best,

    Ralph

    in reply to: Track contact form conversions with Google Analytics goal? #398429

    Hi Josue,

    Everything is tested and working :)

    @ people using the ‘Google Analytics by Yoast’ plugin:

    Initially GA didn’t track anything and thanks to Firebug I found out that ‘ga’ was not defined. I use the ‘Google Analytics by Yoast’ plugin to insert the GA Universal code and it defines ‘__gaTracker’ instead of the standard ‘ga’. So, in order to get the tracking code to work, I had to change it to:

    $('.avia_ajax_form .button').on('click', function() {
         __gaTracker('send', 'event', 'button', 'click', 'button-3');
    });

    A great GA goal tracking testing method:

    Also, a great way to test events and other type of GA goals, is to login to GA > Reporting tab > Real-Time > Events and Conversions. Make sure to not filter your own traffic and you’ll be able to see real-time, whether button clicks and form submissions are being tracked. For reference: https://support.google.com/analytics/answer/1008083?hl=en

    Hope this helps someone :)

    Thanks again,

    Ralph

    in reply to: Track contact form conversions with Google Analytics goal? #397479

    Thank you, Josue!

    I used this topic as a reference as well: https://kriesi.at/support/topic/please-clear-this-up-for-em-ga-tracking-2/

    Kind regards,

    Ralph

    No problem, @Josue!

    Also, please read my latest post. The UPDATE part will clear everything up :)

    Kind regards,

    Ralph

    in reply to: Header fonts rendered thicker when logged out? #364588

    Hey Elliott,

    To answer your questions: In the Enfold settings Open Sans is set as the theme’s header & body font. That is also all I did; set the font settings. I can confirm that I’ve made no manual changes relating to Enfold’s font settings (except for the function fixing the font weight issue). Also, I’m using a LAMP setup.

    However, you’re right about 400 & 600 being the default font weights, but that only seems to be the case when one is not logged in to WP. Once logged in, the id='open-sans-css' link tag line is added to the header, adding 300 to the available font weights. It seems the id='open-sans-css' line overrides the default:

    <link rel='stylesheet' id='avia-google-webfont' href='//fonts.googleapis.com/css?family=Open+Sans:400,600' type='text/css' media='all'/>

    which, as you can see, loads 400 & 600 (only when one is not logged in to WP).

    UPDATE (root of the problem found!):

    Instead of only searching through Enfold’s core code, I decided to code search through all of the WP files, based on the keyword “open-sans”. And I finally found out where the id='open-sans-css' link tag line is coming from! It’s added to WP’s header by wp-includes > script-loader.php. Just look for the following line in script-loader.php:

    $open_sans_font_url = "//fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,300,400,600&subset=$subsets";

    WP happens to use Open Sans for the Admin area and adds Open Sans (including 300) when logged in to WP.

    Possible solutions to prevent future Open Sans font weight confusion/issues: Either WP has to drop 300 or Enfold has to adapt to WP and add 400, 600 and 300 as default Open Sans font weights. Just my 2 cents though.

    Not sure whether this will lead to a core code fix, but it at least clears everything up :)

    Kind regards,

    Ralph

    @Tomzilla: Please read my post. It offers 2 function-based solutions to fix this issue:

    Solution #1 tells you step-by-step how to get @Josue’s function working (it works perfectly fine).
    Solution #2 is a function I wrote myself. It checks whether the line that disappears, after logging out of WP, is in the header. I mean the following line:

    <link rel=’stylesheet’ id=’open-sans-css’ href=’//fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400italic%2C600italic%2C300%2C400%2C600&subset=latin%2Clatin-ext&ver=4.0.1′ type=’text/css’ media=’all’ />

    If the above line is not in the header (e.g. when you’re logged out of WP), then the function will add this line to your site’s header. Making your site’s logged in and logged out versions look exactly the same. And it’s no longer required to add this line manually to the (child) theme’s header, which is how you currently fixed the issue.

    Here’s my post explaining everything in detail: https://kriesi.at/support/topic/header-fonts-rendered-thicker-when-logged-out/#post-363534

    Hope this helps!

    Best,

    Ralph

    in reply to: Header fonts rendered thicker when logged out? #363534

    Hey Elliott,

    The Root of the Problem

    Thanks for you help! It seems that, when one is logged out of WP, the following line disappears from the source (it actually adds support for a 300 font weight):

    <link rel='stylesheet' id='open-sans-css' href='//fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400italic%2C600italic%2C300%2C400%2C600&subset=latin%2Clatin-ext&ver=4.0.1' type='text/css' media='all' />

    I think this is something that needs to be fixed in Enfold’s core code (Enfold shouldn’t remove the above line for non-logged users) :) Because when this line disappears, the lowest supported Open Sans font weight is, as you mentioned, 400 (instead of 300). Seems more Enfold users have this issue and one user has added the line manually to header.php.

    Solution #1 of 2

    Fixes headers, but not text size issue of text between <em> tags:

    However, I re-read the topic I mentioned earlier and a solution is actually given by @Josue.

    Since you pointed out that Open Sans does not support a font weight of 100, I modified Josue’s function to reflect this (as Josue’s original function also calls the non-existent 100 font weight). Here’s the working result, calling all font weights supported by Open Sans:

    Please Note: after adding the function below to functions.php, Open Sans has to be re-saved as Enfold’s default font. Otherwise the function will not work! So please complete the following steps:

    1 – Add the following function to functions.php:

    function add_open_sans_full($fonts) {
    	$fonts['Open Sans'] = 'Open Sans:300,400,600,700,800';
    	return $fonts;
    }
    add_filter('avf_google_heading_font', 'add_open_sans_full');
    add_filter('avf_google_content_font', 'add_open_sans_full');

    2 – Go to WP Admin > Enfold Settings > General Styling > Fonts;
    3 – Select Open Sans in the 2 drop down menus (Heading Font & Defines the Font for your body text);
    4 – Save Enfold’s settings;
    5 – Reload your website in your browser.

    The font weights (e.g. 300) should now work for both logged in and non-logged in users.

    The Details re Solution #1/2 / Function #1/2

    The function does not add:

    <link rel='stylesheet' id='open-sans-css' href='//fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400italic%2C600italic%2C300%2C400%2C600&subset=latin%2Clatin-ext&ver=4.0.1' type='text/css' media='all' />

    Instead it expands:

    <!-- google webfont font replacement -->
    <link rel='stylesheet' id='avia-google-webfont' href='//fonts.googleapis.com/css?family=Open+Sans:400,600' type='text/css' media='all'/>

    To:

    <!-- google webfont font replacement -->
    <link rel='stylesheet' id='avia-google-webfont' href='//fonts.googleapis.com/css?family=Open+Sans:300,400,600,700,800' type='text/css' media='all'/>

    Solution #2 of 2

    Fixes headers & text size of text between <em> tags… so, logged in and logged out versions look exactly the same:

    I wrote a function which checks whether the following line is in the header (the line that disappears after logging out of WP):

    <link rel='stylesheet' id='open-sans-css' href='//fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400italic%2C600italic%2C300%2C400%2C600&subset=latin%2Clatin-ext&ver=4.0.1' type='text/css' media='all' />

    If the line is there, function does nothing. If the line is not there (e.g. when you’re logged out of WP), then the line is added.

    Simply add the following function to functions.php, upload functions.php to your server and reload website in your browser (no need to re-save Enfold settings):

    function add_open_sans_full() {
    	if (!wp_style_is('open-sans')) {
    		wp_enqueue_style('open-sans', '//fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400italic%2C600italic%2C300%2C400%2C600&subset=latin%2Clatin-ext&ver=' . get_bloginfo('version'), array(), null);
    	}
    }
    add_action('wp_enqueue_scripts', 'add_open_sans_full');

    Thanks @Elliott & @Josue!

    Kind regards,

    Ralph

    PS: I’ll change my CSS to reflect the lowest possible Open Sans font weight (300 instead of 100).

    in reply to: Header fonts rendered thicker when logged out? #362831
    This reply has been marked as private.

    Thank you, Yigit! Your CSS snippet fixed it!

    Best regards,

    Ralph

    in reply to: Upload new Social Icon #357539

    @yigit: No problem :) I’ve updated my answer with a link to your reply. Since it’s a bit unclear whether the Skype icon itself should be replaced by Github (as explained by my “how-to”) or whether Github should be added to Enfold’s “Social Profiles” settings (as explained by the post you link to).

    in reply to: Upload new Social Icon #357513

    Update: Please note that my “how-to” below, will force Enfold to replace the actual Skype icon itself with your custom Github icon. In case you’re looking to add Github to Enfold’s “Social Profiles” settings, then you might need a completely different and more complex approach / function.

    In case you’re actually looking to add Github to Enfold’s “Social Profiles” settings, then please see the link in Yigit’s reply.

    Hi Slade,

    I’m using that function to replace the pencil icon in post archives. If the complete function is in your functions.php already, all you have to do is this:

    Replace:

    $icons['standard'] = array( 'font' =>'entypo-fontello', 'icon' => 'ue915');

    With this:

    $icons['skype'] = array( 'font' =>'fontello', 'icon' => 'ue999');

    As you can see, standard needs to be replaced with skype. That will tell Enfold that the default Skype icon should be replaced with icon ue999.

    Optional: you might notice that entypo-fontello is changed into fontello, as this is the name of my custom icon collection. Since it’s unclear to me how you named your custom icon collection, you might need to use another value than fontello. To find out the correct value/font name to use:

    – Simply edit a page using the Advanced Layout Builder.
    – Open a Content Element that will show you the list of icons you can use (e.g. the Icon content element has this list).
    – You’ll notice that each font collection, in the icon list, has a short line of text above it, stating the collection’s name in a Font: entypo-fontello format.
    – Find the ue999 icon in the icon list and see under which font name it is placed. If it’s Font: fontello, then no further action is needed. If it’s Font: anothername then ensure your line looks like this:

    $icons['skype'] = array( 'font' =>'anothername', 'icon' => 'ue999');

    That should do the trick!

    Best,

    Ralph

    in reply to: wordpress update 4.0.1 disabled homepage slider #357503

    @lounge35: Point 2 (flush cached files) should cover any Cloudflare issues. Please see my reply on your Cloudflare post for more info on caching: https://kriesi.at/support/topic/layerslider-not-working-after-enfold-3-04-update/#post-357486

    in reply to: wordpress update 4.0.1 disabled homepage slider #357489

    1 – Make sure you update Enfold to v3.04 and do this update via WP admin (not via FTPing the v3.04 files).
    2 – In case you use some form of caching, flush all cached files.
    3 – Go to your slider homepage and hit CTRL+F5 (clears your browser cache)
    4 – Check whether the slider is working again.

    in reply to: LayerSlider not working after enfold 3.04 update #357486

    Rocket Loader caches files: https://support.cloudflare.com/hc/en-us/articles/200168256-What-are-CloudFlare-s-caching-levels-

    Whenever some form of caching is used, this cache always needs to be flushed after WP, theme and plugin updates. Otherwise the cache will keep serving the old files to browsers, instead of the new updated files. Flushing a cache will simply remove those old files and force the cache to cache/store the new files.

    Here’s how to flush/purge a Cloudflare cache: https://support.cloudflare.com/hc/en-us/articles/200169246-How-do-I-purge-my-cache-

    Hi,

    Does someone know what might be causing the logo to “scroll shrink” even on 767px and lower? Seems like a JS issue… the shrink function is never disabled for some reason.

    Best,

    Ralph

    Hi!

    I’m starting to see a pattern reading this topic and this one: https://kriesi.at/support/topic/all-forms-down-since-wordpress-auto-update-4-0-1/

    This is the pattern:

    – Manual uploading/updating does not work correctly (forms and maps not working).
    – Updating Enfold via WP admin makes everything work correctly (forms and maps work once again).

    Whatever the cause, if you’re having form and/or maps issues with v3.04:

    – Update Enfold via WP admin and not via a manual upload.
    Always flush server, WP and browser cache, in case you’re using some form of caching.

    Still not working? Try this:

    – Activate WP’s default theme or some other theme.
    – Delete Enfold completely from your server ( ! backup your custom code first ! ).
    – Upload an unmodified Enfold v3.04 file package (the one you download from ThemeForest).
    – Activate Enfold again.
    – Check whether forms and maps are working correctly now.

    Hope this helps!

    Ralph

    This reply has been marked as private.
    in reply to: All Forms down since – wordpress auto-update 4.0.1. #356696

    @smallpotato / Tung Do: That’s why I always unpack the latest files on my hard drive, upload them and then verify whether there are as many files on my server as there are on my hard drive. Since, as @Josue states, I can confirm that files are sometimes not FTPed.

    Filezilla is a great FTP program that doesn’t just skip files and not notify the user about the skipped files. It’s 100% free and you can get it here (for FTPing you’ll need the Client version): https://filezilla-project.org/

    Update: Since the topic is closed, here’s my reply to @smallpotato / Tung Do’s reply below:

    If you did several manual updates, it’s indeed a bit odd that FTP would always skip the file(s) needed to make forms and maps work. In my experience, when FTP silently skips files, it happens with completely random files… never the exact same files.

    If you’re absolutely sure that all files were uploaded during manual uploading, then I can only think of 2 other possible culprits:

    1 – Not sure whether your server and/or WP caches (theme) files. If yes, then the old theme files in the cache finally got flushed.
    2 – Something was wrong with the files you used for the manual uploading. Seems more people run into problems trying to manually upload/update to v3.04. And then it gets fixed doing a WP admin-based theme update (just like you did).

    • This reply was modified 10 years, 1 month ago by Ralph12.
    in reply to: All Forms down since – wordpress auto-update 4.0.1. #355948

    @jorgepelaez: Thanks for posting the debug! I do not see anything that might explain your issue.

    Just to check whether Enfold is causing it, you might want to switch to WP’s default theme. Then, via the default theme, send a test email using a Contact Form 7 form. If you receive this mail, Enfold is causing your mail issues. If you don’t receive it, it’s either your WP setup, a plugin or hosting-related:

    – To make sure your WP setup is okay: Go to Admin > Dashboard > Updates and click the ‘Re-install Now’ button. This has fixed things for me in the past.
    – To make sure it’s not a plugin; de-activate all plugins.
    – To make sure it’s not your webhost: Contact them about your issue.

    Here’s a script that you can use to test wp_mail: http://www.butlerblog.com/2012/09/23/testing-the-wp_mail-function/

    I also Googled on the CF7 error you mentioned and there are some fixes being mentioned. Perhaps one of them will fix your issue. Here’s the SERP »

    Update: I checked the CF7 site and it explains the errors here: http://contactform7.com/faq/after-submitting-the-form-i-get-an-error-message/

    I hope this helps.

    Best,

    Ralph

    in reply to: All Forms down since – wordpress auto-update 4.0.1. #355849

    @jorgepelaez: I think @Josue is right about the root of your problem (probably hosting-related). So it’s probably wise to contact your hosting company as well.

    Anyway, I found a detailed “how-to” explaining how to maximize WP’s debug output. It also explains how to block the debug output from being displayed on your site (good idea for live sites). Perhaps the resulting error log will give you a clue. You might want to post the output of the error log here.

    The “Debug On” part of this “how-to” is also useful for those with form and Google maps issues. Here’s the link: http://www.franceimage.com/en/tech-blog/my-wordpress-does-not-send-emails-anymore/

    In case you have access to your server’s error logs, don’t forget to check them as well.

    in reply to: All Forms down since – wordpress auto-update 4.0.1. #355738

    Update: since the form feature went down, I now learned it’s best to keep Enfold updated at all times. So, I decided to switch to a Child theme. That will probably lead to some extra work, but at least I won’t have to repeat that work after each Enfold update (which kept me from updating).

    Enfold forms are working fine again :)

    @ Those who are still having form issues:

    I looked at your websites and I can confirm your issues (no forms and maps). Perhaps this is of some use to you:

    1 – Try setting define('WP_DEBUG', false); to true in wp-config.php and then visit the troubled pages. If something is wrong you’ll get an output, which might help you solve the form and Google maps issues.
    2 – Go to Admin > Dashboard > Updates and click the ‘Re-install Now’ button. This has fixed things for me in the past.
    3 – Upload the lastest Enfold version manually.

    in reply to: All Forms down since – wordpress auto-update 4.0.1. #355496

    I can’t update, as that always seems to change lots of custom CSS (when core CSS gets updated). I’ll try to make my custom CSS more compatible with the core CSS.

    But in the meantime: how can I fix the form issue without full theme update?

    Thank you very much, Elliott! Your code suggestion got me in the right direction. It worked right away for the custom taxonomy-based archive, but not yet for the custom post type slug-based archive. To get that archive type working too, I added || is_post_type_archive('business_profile') to the check. This is the final code, that works for both archive types:

    function avia_replace_standard_icon() {
    	global $avia_config;
    	if (is_tax('business_category') || is_post_type_archive('business_profile')) {
    		$avia_config['font_icons']['standard'] = array('font' => 'fontello', 'icon' => 'ue803');
    	} else {
    		$avia_config['font_icons']['standard'] = array('font' => 'entypo-fontello', 'icon' => 'ue836');
    	}
    }
    add_action('pre_get_posts', 'avia_replace_standard_icon');

    Thanks again and regards,

    Ralph

    Hi Elliott,

    Thanks for your suggestion. I tried is_tax as well, but that doesn’t work either. Here’s the function (it uses a custom fontello icon, which works fine without any of the is_-based checks):

    function avia_replace_standard_icon($icons) {
    	if (is_tax('business_category')) {
    		$icons['business_profile'] = array('font' => 'fontello', 'icon' => 'ue803');
    	}
    	return $icons;
    }
    add_filter('avf_default_icons', 'avia_replace_standard_icon');

    I’m clueless as to why the above function doesn’t return true for a check. I’m in fact using another is_tax-based function, which does return true. Here’s the code of the working function (it renames the archive’s H1 title):

    function archive_suit_business_category($output) {
    	if (is_tax('business_category')) {
    		$term = get_term_by('slug', get_query_var('term'), get_query_var('taxonomy'));
    		$output = 'Business category: ' . $term->name;
    	}
    
    	return $output;
    }
    add_filter('avf_which_archive_output', 'archive_suit_business_category');

    Do you know why the same check works for the 2nd function, but not for the 1st?

    Best,

    Ralph

    in reply to: Function to remove archive sidebar only for custom taxonomy? #351793

    Hey!

    Ok, I did find a function, but it’s not specifically for Enfold (it’s for the Choices theme): https://kriesi.at/support/topic/portfolio-entries-archive-category-pages-full-page-with-no-sidebar/#post-282147

    Can someone please confirm whether I can use the Choices function for Enfold?

    Thank you,

    Ralph

    in reply to: How to hide the comment form itself? #348852

    Hi Elliott,

    The reason I need to mod the comments part, is because of a special kind of post. I actually ended up creating a custom post type for this, which is actually way better than sticking to the standard WP post type. And I gave this custom post type its own file based on the original comments.php file. So now I can edit both the single-costum_post.php file plus the relating comments file, without touching Enfold’s core files. So it has pretty much the same result as a child theme, which is great!

    Also, I noticed that when using a check resulting in comments_open() = false, the comment count is actually displayed when the comment count is greater than 0. So, in a comment count is greater than 0 situation, only the comment form will be hidden, while the comments and the comment count will be displayed. The reason I thought that not only the comment form was hidden but the comment count as well, is because I only tested in a zero comment situation. Had I tested a comments_open() function in a comment count is greater than 0 situation, only the comment form would have been hidden. I’m sorry for not figuring that out sooner!

    Conclusion: Solution 1 is definitely suitable for hiding the comment form itself. And then, as per your suggestion, the “Comments are closed” text could be hidden using some CSS.

    Thank you very much for your time and patience!

    Kind regards,

    Ralph

    in reply to: How to hide the comment form itself? #348103

    Hey Elliott!

    Thank you for your suggestion! The only problem with modding comments.php, is that it wouldn’t be update-proof. But it seems to be the only way to specifically target the comment form itself.

    I do have 2 solutions that can be made update-proof, by placing them in a custom functions file. But they seem to remove comment counts as well. But I’m going to share ’em anyway, as they might be of some use to someone else.

    Solution 1
    Can be used to close comments for certain posts:

    function close_comment_form( $open, $post_id ) {
        $post = get_post( $post_id );
        if( $post->post_type == 'post' ) {
            return false;
        }
        return $open;
    }
    add_filter( 'comments_open', 'close_comment_form', 10 , 2 );

    Solution 2
    Can be used to hide the comment form via display: none; on CSS selector #HIDEcommentform:

    function my_comment_form_defaults($defaults) {
        $defaults['id_form'] = 'HIDEcommentform';
        return $defaults;
    }
    add_filter('comment_form_defaults', 'my_comment_form_defaults');

    In case someone has a solution for specifically targeting the comment form itself, via an update-proof functions file, then I’d love to hear about it.

    Thanks again,

    Ralph

    in reply to: Tabular table column headings issue in v3.0.1 #333758
    This reply has been marked as private.
    in reply to: Tabular table column headings issue in v3.0.1 #333094

    Hey,

    I fixed it in the core code (enfold\config-templatebuilder\avia-shortcodes\table.php). On line 294 there’s this piece of code:

    td:nth-of-type(".($counter + 1).") Remove the “+ 1” and the table headings are correct again.

    Anyway, the problem is that this fix has to be re-done after each theme update. Which is why I’m wondering whether you perhaps know of a permanent fix?

    Also, why is the “+ 1” there since v3.0.1? All it does is misplace the headings.

    Thanks in advance,

    Ralph

Viewing 30 posts - 31 through 60 (of 84 total)