Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Hello @azzazza!

    The page builders of today are incredibly useful. You will be able to create all kinds of visual appealing pages that would normally require a significant amount of code. However, you are generally locked in once you start using one. Since there is currently no standard for page builders, it’s not possible to move from one to another without rebuilding your pages.

    Many themes use Visual Composer, Beaver Builder and other standalone plugins. Avada uses Fusion Builder. Divi uses the Divi Builder.

    So if you chose to use Divi and built out all of your pages, you wouldn’t really be able to change themes without creating your pages from scratch.

    So the biggest pro is that page builders save a lot of time that you would normally spend coding. The biggest con is that you’re basically locked in to use that page builder until you’re ready to build your website again.

    As far as SEO goes, this depends on how the page builder renders the elements. Most of them are pretty good and wouldn’t actively work against your SEO.

    I hope that helps!

    Hey Beven,

    When you log in to your site’s FTP, can you see the files from your WordPress installation in the public_html folder? I believe this notice would only appear if the files haven’t been uploaded/transferred correctly, or the DNS for the domain aren’t pointing to the correct server/path.

    Thanks!

    Ryan

    As all of the images are being returned at 404’s (file not found), it’s likely that either the files have been moved or deleted. As per the post above, if you’re familiar with FTP, jump in and have a look inside the /wp-content/uploads/ folder and see if those images are still located there. If you’re not familiar with FTP, it might be worth getting in touch with your host and see if they can give you a hand.

    While that shouldn’t happen after a core WordPress update, I would recommend regenerating your thumbnails using one of the popular plugins:

    https://www.ads-software.com/plugins/regenerate-thumbnails/
    https://www.ads-software.com/plugins/force-regenerate-thumbnails/

    It sounds like the reference to the media items is still there (in the database), so as long as the images have not been moved from the location that they were originally uploaded to, the plugins above might resolve the issue.

    Hmm, so you can login to the WordPress dashboard, but you’re not seeing the dashboard content?

    What happens when you visit this URL?

    https://www.thecookiesonline.com/wp-admin/themes.php

    You should see a grid of thumbnails representing each of the themes that you currently have uploaded to your server.

    Hey @geurtroos!

    If you are using the ‘Contact’ page template, the address is set in your Theme Options (where you took the screenshot). If you’re not using the ‘Contact’ page template, then the address will be set on the Google map shortcode itself.

    If you are using a lat/long address, make sure you use the correct syntax:

    latlng=52.2482681,-5.248533299999963

    And remove everything else from the address field. If you’re still having issues, I can only recommend heading over to the Avada support center and submitting a ticket so that a member of our team can take a look for you.

    Thanks!

    Ryan

    Hey @brandonstiles!

    Hmm, perhaps I (and others) don’t quite understand what the issue is (your screenshot doesn’t look like it attached either). When you say that all of your CSS files are being called on each of your pages, this would only be an issue if you had a different stylesheets for each of these pages. Based on the code you included, it looks like you are trying to load a stylesheet from inside the page template with this line:

    <link rel="stylesheet" href="<?php bloginfo('template_directory');?>/CSS/approach.css">

    While it’s technically possible to load an external stylesheet inside the body, it’s not recommended and your current implementation would not be valid (you can’t use the rel tag) markup.

    You should be using WordPress hooks and your functions.php file to achieve the functionality you’re after. You can use the is_page() and is_page_template() functions to load the correct file on the correct page. Here are some links that you may find useful:

    https://developer.www.ads-software.com/reference/functions/wp_enqueue_style/
    https://developer.www.ads-software.com/reference/functions/is_page/
    https://developer.www.ads-software.com/reference/functions/is_page_template/

    I hope that helps!

    Thanks!

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey @johnbriese!

    Not a problem, I’m glad to hear I could be of assistance!

    Good luck with your website,

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey @soyeon_chung!

    Yes, after making the changes/removing the code you added from your functions.php file, you will need to upload the new one and remove the old one from your theme directory. If that doesn’t resolve the error, perhaps something else is causing the problem.

    Do you have URL where I can see the issue?

    Thanks!

    Ryan Phillips

    (@ryanphillips)

    Hey @johnbriese!

    It looks like you have made the correct changes to your CSS file, however they are not being applied to your site. I can see that your site is using a minified version of your CSS file.

    At the moment, we’re making changes to the regular CSS file, not the minifed one. It’s a bit hard to tell how the minification is happening without logging into your site, however I assume both versions were included with the theme and it’s simply loading the minfied copy.

    In this situation, you will need to minify the CSS that you just sent over to me, using a tool such as:

    https://cssminifier.com/

    Then open the style.min.css in your theme folder and replace the entire contents with the newly minified CSS. As always, please take a backup of the current style.min.css before replacing it with the new one.

    I hope that helps!

    Thanks,

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey @johnbriese!

    There are a few too many brackets in your CSS. Can you please send over your original CSS before you made my changes? I’ll add my CSS in and leave comments so you know where the change was made.

    Thanks!

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey Triona,

    It’s great to hear you managed to resolve the issues with the URLs. Unfortunately the issue regarding JetPack is something that would require admin access to investigate.

    I would recommend getting in touch with Automattic via the JetPack support site:

    https://jetpack.me/contact-support/

    I hope you manage to find a solution for this one!

    Thanks,

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey @johnbriese!

    Not a problem, we all start somewhere!

    My CSS above will need to replace the existing CSS that you currently have. As your CSS is minified, I can’t give you a specific line number to look for. However, in your style.css file you will find this code:

    .embed-wrap {
        position: relative;
        margin-bottom: 25px;
        padding-bottom: 56.25%;
        padding-top: 30px;
        height: 0;
        overflow: hidden;
    }

    You will need to remove the padding-bottom and height attributes from this CSS, the rest of it can stay as it, like so:

    .embed-wrap {
        position: relative;
        margin-bottom: 25px;
        padding-top: 30px;
        overflow: hidden;
    }

    You will then need to find the styling for the iframe itself, which currently looks like this in your style.css file:

    .embed-wrap iframe, .embed-wrap object, .embed-wrap embed {
        position: absolute;
        top: 0;
        left: 0;
        width: 100%;
        max-width: 100%;
        height: 100%;
    }

    You will then need to change it to the following:

    .embed-wrap iframe, .embed-wrap object, .embed-wrap embed {
        position: relative;
        width: 100%;
        max-width: 100%;
    }

    That should do the trick!

    Let me know how that goes for you.

    Thanks!

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey @johnbriese!

    Thanks for the link!

    I can see that your iframe is positioned absolutely and styled in a way so that it will be 100% width of it’s parent container and it’s height will be 56.25% of that calculated width (Which is a common 16:9 aspect ratio). I would recommend making the following changes to your CSS (The lines I have commented out can be removed from your CSS file):

    .embed-wrap {
        position: relative;
        margin-bottom: 25px;
        /* padding-bottom: 56.25%; */
        padding-top: 30px;
        /* height: 0; */
        overflow: hidden;
    }

    By changing the position value on the .embed-wrap from ‘absolute’ to ‘relative’, we’re letting the parent element adjust to the size of it’s children, which in this case is the embedded iframe.

    .embed-wrap iframe, .embed-wrap object, .embed-wrap embed {
        position: relative;
        /* top: 0; */
        /* left: 0; */
        width: 100%;
        max-width: 100%;
        /* height: 100%; */
    }

    Again, by changing the position value on the .embed-wrap iframe from ‘absolute’ to ‘relative’, we’re allowing the width and height attributes on the tag to take effect.

    Can you give that a go for me?

    Thanks!

    Ryan

    Ryan Phillips

    (@ryanphillips)

    Hey Yulia!

    I agree with @innuvo, the images appear crisp and clear on my end. The images are being embedded as 900 x 600, but are being rendered at 760 x 507, so there’s no reason they should be blurry.

    https://prntscr.com/8y4dc4

    Did you manage to solve this one since posting this thread, or are you still seeing blurry images on your end?

    Thanks!

    Ryan

Viewing 15 replies - 1 through 15 (of 18 total)