Hi,
Sorry for the late reply and thank you for the login. I tested your temp site and compared it to your live site and I’m not seeing any errors, other than the pagination not working correctly.
I tried to recreate this on my localhost by adding a portfolio grid element to a portfolio item, such as your example, but the pagination worked correctly. Can you please post a link to a text copy of your .htaccess file, perhaps there is an odd rule there?

Best regards,
Mike

Hi,
Sorry for the late reply and thanks for the screenshot, I checked your check out page and found that the input fields are actually “iframes” from the “stripe” domain. So in this case you can not control the element because it is not your domain.
But the input fields already have the font size defined at 15px with this css:

.ElementsApp, .ElementsApp .InputElement {
    color: #31325F;
    font-size: 15px;
}

so I would think that this addresses the zoom effect for the element, but if not I found this article on styling the fields. You can try this css based on the information from the article:

#stripe-card-element,
#stripe-exp-element,
#stripe-cvc-element {
	font-size: 16px !important;
}

After applying the css, please clear your browser cache and check.

Best regards,
Mike

Hi,
Glad to hear, and thank you for your patience while we sorted this out. Unless there is anything else we can assist with on this issue, shall we close this then?

Best regards,
Mike

Hi,
The dev team has returned a fix for the full-width button in the Ajax Portfolio Preview text section: “The full-width element full-width button shortcode broke the layout because called outside shortcode tree and creating an extra section.” Full-width elements try to full-width for the screen not just the element, so typically placing a full-width element inside a page element will cause an issue. In this case, the dev team edited the full-width button and the portfolio element so this will work correctly.
This will be included in the next release. In the zip file in the Private Content area, you will find two files:
buttons_fullwidth.php & portfolio.php
via ftp, please save a fallback copy of your current files and replace these at these locations:
\wp-content\themes\enfold\config-templatebuilder\avia-shortcodes\buttons_fullwidth\buttons_fullwidth.php
\wp-content\themes\enfold\config-templatebuilder\avia-shortcodes\portfolio\portfolio.php
Then clear your browser cache and any cache plugin, and check.

Best regards,
Mike

Hi,
The patch should already be in this version, please include an admin login in the Private Content area so we can investigate.

Best regards,
Mike

Hi,
Thank you for the login, I see that the button “Edit Audio Player (Classic Editor)” is always pointing to the “post=1766” which is one of your Audio Players, it doesn’t seem to matter if it is a post or a page, and there are no errors in the browser console.
If I disable your plugin “Disable Gutenberg” and change the default editor at Enfold Theme Options > Select Your Editor the button changes text but not the wrong link.
So I don’t know why this plugin & Enfold are clashing, but unfortunately, there is not a lot we can for third-party plugins within the scope of our support.
But since the link never changes, I think we can replace the link with the correct edit link for pages and posts with this script and hopefully improve your workflow.
Try adding this code to the end of your functions.php file in Appearance > Editor:

function custom_script(){
  ?>
  <script>
(function($){
  $(window).load(function(){
  function get_current_page_id() {
    var page_body = $('body');

    var id = 0;

    if(page_body) {
        var classList = page_body.attr('class').split(/\s+/);

        $.each(classList, function(index, item) {
            if (item.indexOf('page-id') >= 0 || item.indexOf('postid-') >= 0) {
                var item_arr = item.split('-');
                id =  item_arr[item_arr.length -1];
                return false;
            }
        });
    }
    return id;
}
var id = get_current_page_id();
var theURL = '/wp-admin/post.php?post='+id+'&action=edit&classic-editor=1';
  $('#wp-admin-bar-edit a').mouseover(function() { 
            $(this).attr("href", theURL);
        });
  });
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'custom_script');

this will not change the text of the button, but it does change the link.
Please clear your browser cache and check.

Best regards,
Mike

Hi,
Sorry for the late reply, to load your edited /avia.js file via the child theme, first ensure that your file is at: /enfold-child/js/avia.js by creating a folder called “js” in your child theme directory.
Then add this code to the end of your child theme functions.php file in Appearance > Editor:

//Load child theme avia.js
function wp_change_aviajs() {
	wp_dequeue_script( 'avia-default', get_template_directory().'/js/avia.js', array('jquery'));
	wp_deregister_script(  'avia-default', get_template_directory().'/js/avia.js', array('jquery'));
	wp_enqueue_script( 'avia-default', get_stylesheet_directory_uri().'/js/avia.js', array('jquery'));
	
	}
	add_action( 'wp_enqueue_scripts', 'wp_change_aviajs', 100 );

Then clear your browser cache and any cache plugin, a couple of times and check.

Best regards,
Mike

Hi,
Sorry for the late reply and thanks for the login, I checked your test event and found the event had already expired, so I changed the start and end dates so it will show. I couldn’t find the setting with the block editor set so I enabled the Classic Editor.
Then I found your site giving this error: (failed)net::ERR_CONNECTION_RESET sometimes for your enfold stylesheet, and sometimes for your javascript files.
Please check your server error log to see why your site seems to rest the connection on most page reloads, this seems like a server misconfiguration.

Best regards,
Mike

Hey Blaise,
Sorry for the late reply, and thanks for the screenshots. So when the button in your toolbar says “Edit Audio Player (Classic Editor)” it links to the plugin settings, and this occurs if you “preview” a page?
Yet if you publish the page the button will say “Edit Page (Advanced Layout Builder)”, correct?
Can we login to your site to examine? Please include an admin login in the private content area so we can take a closer look.

Best regards,
Mike

Hi,
Sorry for the late reply, and thanks for the login, I checked your main menu sub-menus and found on hover the font size was much larger, but the sub-menus are not showing in a big box for me. Please see the screenshot in Private Content area.
If you would like to adjust the font size, please try this code in the General Styling > Quick CSS field or in the WordPress > Customize > Additional CSS field:

a:hover span.avia-menu-text {
	font-size: 12px !important;
}

Best regards,
Mike

Hi,
I would say that this should resolve the issue because the “aviaAsset_avia-head-scripts” row in the database is created when the file merging and compression is enabled, and it is removed when file merging and compression is disabled.
But in your Private Content area above the code that you pasted is much more than the one line that should be there, like this:

so I wonder if your field is being appended and not cleared. Can you search for “aviaAsset_avia-head-scripts” in your “phpMyAdmin” database tool while your file merging and compression is disabled and again when it is enabled to see if it is removed and then shows with just one line when it is enabled.

Best regards,
Mike

Hi,
Sorry for the late reply and glad to hear your host was able to import the demo. Typically this error seems to occur with “Managed WordPress” hosting accounts that have certain security settings. It doesn’t seem to be every “Managed WordPress” host, but typically these types of accounts are limited to the user for making changes to the server settings and many hosts will not change settings or advise which settings are used.
One solution that sometimes helps is checking the PHP settings on the server to see if the secure options are activated.
If “allow_url_fopen, “allow_url_include” and “register_globals” are “off”, try turning these “on”.
I suspect that your webhost temporarily made a change to your server settings before they imported the demo.
The dev team is working on a new importer, but right now we are unsure when this will be ready.
Since your demo is now imported shall we close this thread?

Best regards,
Mike

Hi,
Thank you for the feedback, this is a strange issue, so yes, I believe the two errors are due to the test not loading the CSS. I also believe that if you check your Google Webmaster account you will not be getting any errors for the same files from Google Bot, meaning that your site is indexing correctly, and as we know actual devices are loading the files.
I’m not sure why the test is not loading some of your css files, but I do see that you have a “mixed content” error which is not related to your css, but perhaps correcting it will help.
So this code tells the Browser or Google Bot, to try to get all files via HTTPS thus solving any “mixed content” errors.
Try adding this code to the end of your functions.php file in Appearance > Editor:

function add_custom_meta(){
  ?>
  <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
  <?php
  }
  add_action('wp_head', 'add_custom_meta', 1); 

If you prefer, we can add this for you if you include an admin login to your site in the Private Content area.

Best regards,
Mike

Hi,
@Justin thanks for sharing your solution, unfortunately, I was unable to reproduce an error in the console on my localhost, but I’m glad to hear that this helped with your issue.

Best regards,
Mike

Hi,
@Justin sorry for the late reply, I installed Yoast on my localhost and checked /avia_framework_post-sitemap.xml but I’m not seeing any errors in the browser console, but the sitemap also has zero entries. Perhaps after there are some entries the error will show for me? I also checked the homepage for the error but didn’t see it.
What version are you using 4.7.6.2 ?

As for indexing the builder, I would leave this option enabled so that Yoast doesn’t add noindex to the robots meta.

Best regards,
Mike