Forum Replies Created

Viewing 27 posts - 1 through 27 (of 27 total)
  • Author
    Posts
  • The conflict goes back a long way with how enfold does css. You use #top and not just a .avia_top_content class. There is some sort of precedence given to ids over classes. So only way I could fix this is to take all the ninja form css and prefix them with #top so for example:

    .nf-field-description {
    width: 100%;
    -ms-flex-order: 10;
    order: 10;
    }

    becomes:

    #top .nf-field-description {
    width: 100%;
    -ms-flex-order: 10;
    order: 10;
    }

    in reply to: Performance dynamic_avia #1239544

    Unfortunately, I can’t provide that yet as it’s not on the public side of the firewall.

    Is there any other information I can provide you?

    in reply to: Conditional Ava Elements #1232039

    What I did for now was to use the avf_in_shortcode_handler_prepare_content filter and using the Custom ID field and if you set id to be peernetCan it will hide the element.

    add_filter( ‘avf_in_shortcode_handler_prepare_content’, array( &$this,’enfold_shortcode_handler_prepare_content’), 10, 1 );

    public function enfold_shortcode_handler_prepare_content( &$args )
    {
    // from wp-content\themes\enfold\config-templatebuilder\avia-template-builder\php\shortcode-template.class.php line 1064
    //$args = array( $out, $this, $atts, $content, $shortcodename, $fake )

    $attrs = $args[2] ;
    if ( !empty( $attrs[‘id’] ) ) {
    if ( strpos($attrs[‘id’], “peernetCan”) === 0) {
    $args[0] = ” ;

    }

    }

    return $args;

    }

    I’m looking to have is common development field like custom id that can be used in a similar manner to determine if an element is to be included or excluded.

    For now I’ll go with this approach.

    in reply to: Conditional Ava Elements #1232027

    I did some thinking about conditional elements and I could really use them as well.

    My thought would be to add a filter field to enter a filter name into the developer settings on the advanced tab.

    Then when processing elements would fire the filter which would return a boolean value to true or false (meaning include or not include this element).

    By doing this, it’s completely independent of any usage and is general enough to included into the enfold base.

    Is this something you would consider adding?

    in reply to: Problem with Editors after Update to 4.7.4 #1214434

    I found fix in another article where it broke because of WordPress 5.4 and doing this change fixed the issue for me:

    Please try to replace this file: /enfold/config-gutenberg/css/avia_gutenberg.css , with the this: https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_7_4/config-gutenberg/avia_gutenberg.css

    in reply to: Problem with Editors after Update to 4.7.4 #1214386

    I’m having the same issue. It looks like the Advanced Editor is no longer loading in 4.7.4

    No Updates available. You are running the latest version! (4.7.4)
    Check Manually
    Your PHP version: 7.3.18

    You can close the topic.

    Thank you, that worked!

    Hi Rikard,

    You can go ahead an close the topic.

    Peernet

    Thank you so much Vinay! It’s working perfectly now.

    Unfortunately we can’t because the issue is on a UAT site that cannot be accessed from the outside.

    Hi Victoria,

    That’s correct. We’d like to stop using header transparency but we can’t seem to figure out how to turn it off.

    We did a mockup on our UAT site for our new website where we were able to achieve the white header. We then recorded all of our settings, re-loaded the UAT site from our live site, and started making the permanent changes but for some reason we can’t recreate the white header.

    I’ve provided links to screenshots of the mockup, the current UAT site, and our header settings below.

    Also if you use Lunametrics for GA tracking:

    https://github.com/lunametrics/youtube-google-analytics

    A LayerSlider with a video will hang forever in loading. Not a problem in the past.

    I like to track my views in Google Analytics now it’s broken.

    I figured it out, it was caused by a plugin called ‘Lazy Load’ which I used to optimize loading of images.

    Lazy Load
    Lazy load images to improve page load times. Uses jQuery.sonar to only load an image when it’s visible in the viewport.
    Version 0.6.1 | View details

    I disabled this plug-in and the image are now positioned correctly.

    in reply to: WordPress 4.7 #741985

    Sorry, but updating to 3.8.5 makes no difference. Preview changes is still wrong.

    in reply to: Codeblock unescaping escaped HTML #423475

    If I do go ahead an make improvements, how do I share the code changes back to you?

    in reply to: Codeblock unescaping escaped HTML #422468

    Yes, I did wrap the code in sperate blocks and can get it to partly work but then I lose my spans that highlight elements in the code block.

    The fact is the architecture of the component editors are wrong. If you had followed the technique the tinyMCE used it would have worked but the fact is this component does not.

    The tinyMCE encodes the data in htmlentities format from the server side so that escaped html is not interpreted by the browser when embedded in the textarea.

    The templatebuilder does not and this is where everything starts to break down.

    I as said: I started to fix this issue properly but ran into two issues when testing. The tab/editor protocol is different in some way from the textcode/codeblock to editor functionality so did not operate correctly. And on save, still was getting random lose of information on some elements but this in my lack of understanding the save process and probably could have figuire it out in another day.

    The fact remains, any escaped html will not remain intact because the browsers are transforming them back to unescaped format.

    I agree that you can use it if you stick to just plain HTML and do not do anything fancy. But I expected more.

    in reply to: Codeblock unescaping escaped HTML #421673

    I know that the issue is around the fact certain elements are not htmlentities when html stream is created for the advanced editor.

    I did get it to work somewhat correctly but there is no clear documentation about the config-templatebuilder library so it’s hard to get all the paths correct.

    So even though I could correctly get textblock and codeblock to work. When saving sometimes one or two of these entities would be encoded wrong leading to loss of information again.

    So basiclly, I can not use config-templatebuilder (Advanced Layout) tool. It’s just does not function properly.

    So I am no longer going to use this part of Enfold. Only editor that works properly is the Classic Editor!!!!!

    in reply to: Codeblock unescaping escaped HTML #421096

    I understand you are looking for us to give you live access but it is not environmental.

    I know it has to do with any escaped html in a codeblock or a textblock.

    I can see the issue in the debugger php and javascript debugger. I just do not sure which side is a fault yet.

    Basically, for codeblock the contents are interpreted somewhere along the way causing the escaped html to be lost (unescaped).

    You can do this yourself by simply entering the following code in a codeblock. I assume you have access to enfold theme (press update and you will see the error).

    <div style="margin-left: 15px; line-height: 15px; font-size: 12px; font-family: courier; background-color: #e2e2e2; padding-left: 5px;">
    <pre><code><?xml version="1.0" encoding="utf-8"?>
    <Profile Type="0"
             DisplayName="TIFF 200dpi Optimized Color"
             Description ="Word Printed 2-Up with Comments and Date Replacement.">
    
      <Settings>
    
        <span style="background-color: yellow;"><strong><!--Word Specific  options --></strong></span>
        <span style="background-color: yellow;"><strong><add Name="Microsoft.Word.Document.PrintOut.Item" Value="DocumentAndMarkup"/></strong></span>
        <span style="background-color: yellow;"><strong><add Name="Microsoft.Word.PageSetup.TwoPagesOnOne" Value="True"/></strong></span>
        <span style="background-color: yellow;"><strong><add Name="Microsoft.Word.ReplaceFieldDateWith" Value="***DATE***"/></strong></span>
    
        <!-- Output file options -->
        <add Name="Devmode settings;Resolution" Value="200"/>
        <add Name="Save;Output File Format" Value="TIFF Multipaged"/>
        <add Name="Save;Append" Value="0"/>
        <add Name="Save;Color reduction" Value="Optimal"/>
        <add Name="Save;Dithering method" Value="Halftone"/>
    
        <!-- TIFF Compression Options -->
        <add Name="TIFF File Format;BW compression" Value="Group4"/>
        <add Name="TIFF File Format;Color compression" Value="LZW RGB"/>
        <add Name="TIFF File Format;Indexed compression" Value="LZW"/>
        <add Name="TIFF File Format;Greyscale compression" Value="LZW"/>
        <add Name="JPEG File Format;Color compression" Value="Medium Quality"/>
        <add Name="JPEG File Format;Greyscale compression" Value="High Quality"/>
        <add Name="Image Options;Fax" Value="0"/>
    
      </Settings>
    </Profile></code></pre>
    </div>
    in reply to: Codeblock unescaping escaped HTML #420696

    Okay, I am wrong about the changing it to html()

    What really is going on is _aviaLayoutBuilderCleanData which contains the correct html content is being transformed incorrectly by val() and html().

    If you call val() then all escaped HTML is lost. It not the content of the _aviaLayoutBuilderCleanData element, it’s altered.
    if you call html() same thing as doing val() call and then doing EncodeElements $(“<div/>”).text(text).html().

    What you really want it the exact content held by the _aviaLayoutBuilderCleanData element.

    I tracked down this article which highlights the issue:
    http://stackoverflow.com/questions/16252931/getting-inner-html-without-escaping-or-decoding-anything-with-jquery

    So I can see now that the content of the _aviaLayoutBuilderCleanData element although if you view the source of the page had the right content when you call val() or html() you will never get the orginal html.

    The _aviaLayoutBuilderCleanData element needed to be in escaped format so if is raw data. You don’t want the browsers altering this information behind the scene which is what is happening now.

    I’ll continue working on this to see if I can come up with a proper fix.

    in reply to: Codeblock unescaping escaped HTML #420630

    This following code is wrong!!!!!

    /**
    * takes some text in shortcode format (eg: [avia_textblock]this is test[/avia_textblock]) and converts it to an editable element on
    * the AviaBuilder canvas. only executed at page load or when the editor is switched from default wordpress to avia builder
    */
    convertTextToInterface: function(text)
    {
    if(this.activeStatus.val() != “active”) return;

    this.body_container.addClass(‘avia-advanced-editor-enabled’);

    var obj = this, editor;

    if(typeof text == “undefined”)
    {
    text = this.secureContent.val(); //testdrive: val() to html()
    if(text.indexOf(‘[‘) === -1)
    {
    text = this.classic_textarea.val(); //testdrive: val() to html()
    if(this.tiny_active) text = window.switchEditors._wp_Nop(text);
    this.secureContent.val(text);
    }
    }

    // if(this.tiny_active) text = window.switchEditors._wp_Nop(text); // moved up 5 lines in order to fix this: https://github.com/AviaThemes/wp-themes/issues/573

    //sends the request. calls the the wp_ajax_avia_ajax_fetch_shortcode php function
    $.ajax({
    type: “POST”,
    url: ajaxurl,
    data:
    {
    action: ‘avia_ajax_text_to_interface’,
    text: text
    },
    success: function(response)
    {
    $(‘#content-tmce’).trigger(‘click’);
    obj.sendToAdvancedEditor(response);
    //obj.updateTextarea(); //dont update textarea on load, only when elements got edited
    obj.canvas.removeClass(‘preloading’);
    obj.do_history_snapshot();
    }
    });

    —————————–

    The line:
    text = this.secureContent.val(); //testdrive: val() to html()

    Should be:
    text = this.secureContent.html(); //testdrive: val() to html()

    I can see many val() to html() testdrive comments, but for sure this needs to be in html format for the POST operation.

    in reply to: Codeblock unescaping escaped HTML #420607

    If you are careful and just add a codeblock and paste in the escaped HTML and then do an update immediately
    then the displayed page is correct.

    On the edit page view the content of the div:

    <div id=”wp-content-editor-container” class=”wp-editor-container”><textarea class=”wp-editor-area” style=”height:
    300px” autocomplete=”off” cols=”40″ name=”content” id=”content”>

    Is correct with the escaped code block properly escaped twice as expected.

    The AJAX request back to load up the editor layout parts is wrong. On the post data the ‘content’ has been unescaped twice instead of once which leads to the issue.

    I just have not figured out where in the Javascript/HTML the post back is made to the text_to_interface function in the template-builder.class.php

    Hopefully, I will find out where soon so I can repair it.

    in reply to: Codeblock unescaping escaped HTML #420560

    I did figure out how to enable the post navigation by overriding avia_post_nav in my child theme and commenting out:

    //dont display if a fullscreen slider is available since they overlap
    // if((class_exists(‘avia_sc_layerslider’) && !empty(avia_sc_layerslider::$slide_count)) ||
    // class_exists(‘avia_sc_slider_full’) && !empty(avia_sc_slider_full::$slide_count) ) $settings[‘is_fullwidth’] = true;

    in reply to: Codeblock unescaping escaped HTML #420500

    The post navigation is lost when you add an Advanced LayerdSlider. I orginally thought it was just switching to Advanced Layout but you need to add the LayeredSlider and then there is no more post navigation.

    in reply to: Codeblock unescaping escaped HTML #420476

    Also, do not understand why a Code Block in advanced layout is doing anything to the HTML/CSS/Javascript. It should just be a raw dump of what is inside the element but it keeps parse it and not treat it as a RAW element.

    I need it to be RAW!!!!

    in reply to: Codeblock unescaping escaped HTML #420464

    I tested code block but it unescapes the html no matter what. So as soon as I switch to Advanced Layout to add the slider I am now in a position of not being able to create my pages/posts. It just unsable.

    Is there any way to keep the default editor and get the advanced slider in the header with switch to this special layout environment?

    Also, once I switch to Advanced Layout the post navigation is lost. Why did that happen?

    in reply to: Codeblock unescaping escaped HTML #420425

    Rikard,

    Sites internal but this is what I have figured out so far.

    I had to switch to Advanced Layout to add an Advanced LayerSlider so it was full width header but I would have preferred to just have an two Layout settings added just like you do for sidebar settings on each page/post. One for:

    LayeredSlider Heading
    LayeredSlider Footing

    Or even just some shortcode code you can add to the Heading and Footing that are full width, so we did not have to switch to Advanced Layout.

    Anyways: If you create a text code or code block with the following, after you update the escaped HTML is removed.

    1. Stop Watch Folder Service. (Start – Programs – PEERNET Document Conversion Service 2.0 – Watch Folder – Stop Watch Folder Service)
    2. Open Watch Folder configuration file. (Start – Programs – PEERNET Document Conversion Service 2.0 – Watch Folder – Configure Watch Folder Settings)
    3. Add the following lines:
      • <add Name=”Microsoft.Word.Document.PrintOut.Item” Value=”DocumentAndMarkup” />
      • <add Name=”Microsoft.Word.PageSetup.TwoPagesOnOne” Value=”True” />
      • <add Name=”Microsoft.Word.ReplaceFieldDateWith” Value=”***DATE***” />
      • For a complete list of settings and values, see Word Converter Options in the User Guide.

    What I found out this morning is If you put a space between the ‘<add’ and code it as ‘< add’ as shown below. Then in at least text block, the HTML remains escaped but why (did not test code block yet)?

    1. Stop Watch Folder Service. (Start – Programs – PEERNET Document Conversion Service 2.0 – Watch Folder – Stop Watch Folder Service)
    2. Open Watch Folder configuration file. (Start – Programs – PEERNET Document Conversion Service 2.0 – Watch Folder – Configure Watch Folder Settings)
    3. Add the following lines:
      • < add Name=”Microsoft.Word.Document.PrintOut.Item” Value=”DocumentAndMarkup” />
      • < add Name=”Microsoft.Word.PageSetup.TwoPagesOnOne” Value=”True” />
      • < add Name=”Microsoft.Word.ReplaceFieldDateWith” Value=”***DATE***” />
      • For a complete list of settings and values, see Word Converter Options in the User Guide.

    So it appears the < needs a space following it to keep it escaped. But why?????

Viewing 27 posts - 1 through 27 (of 27 total)