Hey Frans,
Thank you for your patience, please include an admin login in the Private Content area so we can example why the image is not showing for you.

Best regards,
Mike

Hi,
Thank you for your patience, it looks like the plugin removes the page max-width in:
/wp-content/plugins/flux-checkout/assets/frontend/css/templates/modern/main.css
the plugin css also seems to override using a percentage so you must use a PX width, please try adding this css to your Enfold Theme Options ▸ General Styling ▸ Quick CSS field:

@media only screen and (max-width: 325px) { 
	.woocommerce-checkout .flux-checkout.flux-checkout--modern,.woocommerce-checkout .woocommerce {
		max-width: 320px;
	}
}
@media only screen and (min-width: 374px) and (max-width: 380px) { 
	.woocommerce-checkout .flux-checkout.flux-checkout--modern,.woocommerce-checkout .woocommerce {
		max-width: 375px;
	}
}
@media only screen and (min-width: 424px) and (max-width: 430px) { 
	.woocommerce-checkout .flux-checkout.flux-checkout--modern,.woocommerce-checkout .woocommerce {
		max-width: 425px;
	}
}
@media only screen and (min-width: 766px) and (max-width: 770px) { 
	.woocommerce-checkout .flux-checkout.flux-checkout--modern,.woocommerce-checkout .woocommerce {
		max-width: 768px;
	}
}
@media only screen and (min-width: 888px) and (max-width: 900px) { 
	.woocommerce-checkout .flux-checkout.flux-checkout--modern,.woocommerce-checkout .woocommerce {
		max-width: 890px;
	}
}

This seems to correct for all of the major mobile screen sizes on the checkout page, I don’t see what the conflict might be, but the checkout page doesn’t have this issue when the plugin is disabled.

Best regards,
Mike

Hey cuccarini,
Thank you for your patience, when I check your category pages the layout seems mostly the same, for example federscacchilazio.com/2024/06/ ▸

and federscacchilazio.com/notizie/ ▸

Then you write that the ideal solution would be to have a header selection for categories like this ▸

For this you can add a category Description

then it will show on the frontend

then with some css we can make the font larger like your example above, is this what you mean?

Best regards,
Mike

Hi,
I added this css to your Quick CSS:

#top #header .avia_mega_div .sub-menu .avia_mega_text_block a {
    text-decoration: none;
    font-size: 12px; 
}
#top #header .avia_mega_div .avia_mega_text_block .avia-bullet {
    margin-top: 10px;
    left: -8px;
}

please clear your browser cache and check.

Best regards,
Mike

Hi,
Thank you for your patience, I changed it to this and it seems to work now, please check:

function custom_redirect_after_login( $redirect, $user ) {
    // URL of your custom My Account page
    $custom_account_page_url = site_url( '/dashboard/' );

    // Check if the user is logging in from the specific login page
    if ( isset( $_SERVER['REQUEST_URI'] ) && strpos( $_SERVER['REQUEST_URI'], '/for-medlemmer/' ) !== false ) {
        return $custom_account_page_url;
    }

    return $redirect;
}
add_filter( 'woocommerce_login_redirect', 'custom_redirect_after_login', 10, 2 );

Best regards,
Mike

Hi,
I’m not seeing this on the check out page, please see the screenshots in the Private Content area of what I see.
Please note that iPhones can be hard to clear the cache, often you need to also clear the history to fully purge the cache, following these steps for Safari and note Step 4 where you will Clear the History.

Best regards,
Mike

Hi,
Thanks for the videos, I have asked the rest of the team if that can reproduce and have a idea for a solution, Thank you for your patience.

Best regards,
Mike

Hi,
I believe this would not be a good idea. If you want to try to copy and repair the shortcode in each page, you could try creating a new site with a fresh install on a temp domain and Enable the Avia Layout Builder Debugger on it and your lave site and then copy the debugger shortcode from the live site and paste it into a text editor like VScode or Notepad++ and then search and replace all of the HTML entities like these

and the paste it into the new site, this might work, but you will need to be very careful to not miss any as this would create unclosed tags and break the new page.
But when I view your site it looks like it is based on the health demo with your text added, so in considering the time it would take, it seems to me that it would be a faster and better process to create a new site with a fresh install on a temp domain, then import the health demo, and then copy the text from the frontend to the new site, not the backend because you don’t want to copy the errors over.
Also when you copy the text from the frontend ensure to first paste it into a text editor like VScode or Notepad++ and remove any HTML code before to paste it into the new site, otherwise you might copy unclosed HTML tags into your new site a break it.
This would be a safer method than copying the debugger shortcode if you don’t work with HTML a lot and can spot the errors.

Best regards,
Mike

Hi,
Ok please leave that disabled, and include a admin login so we can adjust the code and a client login so we can test.
Please note that I don’t think you can test with a admin login, it should be a client level login.

Best regards,
Mike

Hi,
Correct.

Best regards,
Mike

Hi,
MACOSX is not the correct font name, it is the name of the directory in the zip file, try deleting this and then extracting the font zip file on your computer and remove all directories including “MACOSX” and then rezip the font file.
Then when you upload it the correct name will show “Blakely”.

Best regards,
Mike

Hi,
It looks like you are adding the full URL with a leading backslash before it, try using only the page URL like this:

function custom_redirect_after_login( $redirect, $user ) {
    // Check if the user is logging in from the WooCommerce login form
    $requested_redirect_to = isset( $_REQUEST['redirect_to'] ) ? $_REQUEST['redirect_to'] : '';

    if ( empty( $requested_redirect_to ) && ( is_account_page() || is_page( 'for-medlemmer' ) ) ) {
        // URL of your custom My Account page
        $custom_account_page_url = site_url( '/dashboard/' );
        $redirect = $custom_account_page_url;
    }

    return $redirect;
}
add_filter( 'woocommerce_login_redirect', 'custom_redirect_after_login', 10, 2 );

Best regards,
Mike

Hi,
Often when a page is corrupt in this way, you can not correct it and save again, the error just returns, typically using the page Revisions will also not work, but perhaps if you go back far enough it might work, it might be worth a try. But please note to might not be able to recover if it breaks this page.
I would recommend creating a staging copy of your site first to test on.
I would draw your attention to the av_fullscreen shortcode in the beginning of the text elements, this is your full screen slider at the top of your page, but it shows in the text element below the slider:


and it also shows in the last text element on the page:


so this doesn’t match the frontend of your site, as you don’t have more than one full screen slider on your page, thus this page is corrupt and I don’t see a way to correct it,
this is why I recommend either recreating the page in a new blank page, or using your server backup. I know you said that you would have to go back years, but it sounds like you have not been able to update the page in years, so the backup should be the same as the last time you edited the page. In my guess.

Best regards,
Mike

Hi,
I don’t believe that there is a issue with backward compatibility, we would have also experienced this on our sites and seen other users post this, but I have seen shortcode in the text element become corrupt as in this screenshot:
https://img.savvyify.com/images/2024/07/21/Enfold_Support_6362.md.jpg
I also note that you seem to have put your ALB shortcodes in a text element, instead of adding the elements to the page, do you recall building your pages like this, it is unusual.
You could try rolling back to the older version, or restore your server backup to before you updated.

Best regards,
Mike

Hi,
When you write:

top:27%; is my live view in my smartphone good, but the view in the browser development is bad.

it sounds like you are referring to this custom css:

because it is the only one that is a percentage, but this one should not change your device vew because it has the max-width of 736px, which is smaller than your device.
This custom css should be the one that works on your device:

because it’s max-width is the same as your device, but I not sure if you are changing the top:16px; to top:27px; or 27%
If I’m correct about this, change this css to:

@media only screen and (max-width: 373px) {
    .inner-container {
        position: relative;
        top: 16px;
    }
}

so it stops working at 373px and then add this css for your device:

@media only screen and (min-width: 374px) and (max-width: 379px) {
    .inner-container {
        position: relative;
        top: your-value;
    }
}

and adjust the your-value to what looks good on your device.
This way other devices will still look correct, it get tricky when a single device doesn’t display correctly, but I think this will work for you.
When I check with my iPhone 7 which has a screen width of 320px, the logo looks just like it does in the browser development tool for the same width.

Best regards,
Mike