Hi,
Thanks for your screenshot, in my first test on my desktop (1536px) the images seemed ok, but when I simulated a laptop (1024px) the images were incorrect, like your screenshot, so it seems the results will depend on the user’s device.
Perhaps a different plugin will give a better result, or since your posts are recipes that your readers will want to save for a long time, maybe you can manually create a different print layout in a Word document and save as a PDF and link on your page, for example on allrecipes.com the web layout and the print layout are quite different, I know this would be a little more work but it might turn out to be an advantage in the long run.

Best regards,
Mike

Hi,
Sorry, I don’t understand, can you explain further?

Best regards,
Mike

Hi,
For #2, this layout hides the image on mobile, to show try this css:

@media only screen and (max-width: 767px){
.responsive #top.single-post .template-blog .blog-meta {
    display: block;
}
.responsive #top.single-post .template-blog .entry-content-wrapper.standard-content {
	float: left;
}
}

For #1 three of the four featured images are using portfolio sized images (495×400) so their rendered aspect ratio is 216×175 the one image that is square “the podcast” is using an imagine that is 400×400 so it’s rendered aspect ratio is 216×216.
So you could change your featured images to use the same size as you did with your one image “the podcast” or you could try this css if you don’t mind the aspect ratio being a little off:

#top.page-id-448 #main .slide-entry-wrap .wp-post-image {
	height: 216px;
    width: 216px;
}

Best regards,
Mike

Hi,
Thank you for the link to your site I see this css in your merged stylesheet:

.template-page .entry-content-wrapper h1,.template-page .entry-content-wrapper h2 {
    text-transform: uppercase;
    letter-spacing: 1px
}

Since your stylesheet is merged I can not tell where this is coming from but I believe that it is in your Enfold Theme Options ▸ General Styling ▸ Quick CSS field please check and remove it.
If you don’t find it then Please include an admin login in the Private Content area so we can take a look.

Best regards,
Mike

Hi,

@amyteslin you are probably using the “Block Editor” this feature was designed for the “Classic Editor” mode.
If you have any further questions please create a new thread and we will gladly try to help you since this is not your thread posting your login here will not be private and you will not see anything we write in the Private Content area. Thank you for using Enfold.

Best regards,
Mike

Hi,
Glad to hear that you have this sorted out, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hi,
This sounds like you have the css rule text-transform: uppercase; affecting the text, please link to a sample page so we can check.

Best regards,
Mike

Hi,
Thank you for the login, the issue was that the donorbox script was looking for a link with the class custom-dbox-popup, but adding this custom class to the menu option adds the class to the menu li tag and not the a (link) tag, so I added this script to find your menu item and add the class to the correct place, your button is working now, please check.

function my_donorbox_add_class(){
?> 
<script>
(function($) {
  $('#menu-item-6087.custom-dbox-popup a').addClass('custom-dbox-popup');
}(jQuery));
</script>
<?php
}
add_action('wp_footer', 'my_donorbox_add_class');

Best regards,
Mike

Hi,
Thank you for the screenshots, I understand better now but I still don’t this on my end, I checked with Chrome, Firefox, & Edge on Windows 10.

I also tested at different screen sizes 1024px-2500px and the only time I saw the ribbon move up was around 990px but your mobile menu was also activate so I don’t think this is what you are seeing.
If you are using Safari please review this article about clearing your browser cache, and note step 4 to Clear your History.

Best regards,
Mike

Hi,
Glad we were able to help, if you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike

Hey Igitt23,
Probably the easiest approach would be to use a plugin like Timed Content
or you could write a script using this as an example but you could spend a lot of time debugging something like this, a plugin would be better.

Best regards,
Mike

Hey Migchel,
Thank you for the link to your site I see that you are getting a 403 Forbidden Error for your footer-scripts, try disabling all plugins and Enfold Theme Options ▸ Performance ▸ JS & CSS file merging and compression and enable Enfold Theme Options ▸ Performance ▸ Delete old CSS and JS files this should clear the cache for the footer-script file. Then try clear your browser cache and if this doesn’t help then try clearing your server cache, if there is one, if not perhaps your server error log will point to the cause.

Best regards,
Mike

Hey schweg33,
I assume that by “magnifier” you mean the search icon, in which case your css doesn’t look correct, Please try this code in the General Styling ▸ Quick CSS field or in the WordPress ▸ Customize ▸ Additional CSS field:

@media only screen and (max-width: 767px) {
.responsive #top .av-main-nav #menu-item-search.menu-item-avia-special {
    display: none;
}
}

After applying the css, please clear your browser cache and check.
If this doesn’t help please include the url to the page in question so we can take a closer look.

Best regards,
Mike

Hey profumopuntoit,
Try installing the Widget Options plugin, then add multiple Enfold Latest News widgets to your footer. This widget allows you to choose which categories you want to display, then with the plugin you and choose which categories, taxonomies, pages, or posts to show them on.

so with this combination and multiple widgets they should not see the same content over many pages.

Best regards,
Mike

Hey lzevon,
Thank you for your patience and the links, but your best approach would be to convert your ALB posts to default posts, then the whole post would show in the archive pages. Please see the example link below.
You will still be able to use the same custom classes and style.
Is there a reason this would not work for you?

Best regards,
Mike