Forum Replies Created

Viewing 15 replies - 1 through 15 (of 246 total)
  • I am not associated with the plugin author in anyway.

    I see injustice being done here and so must write against it.

    This review is baseless, it’s not a review, it’s misdirected aggression. If you have problems with the plugin then submit a support thread.

    I updated the plugin to the latest version and the issue you mentioned never occurred, it’s something else on your end that’s causing the issue.

    It’s your responsibility to keep backups of your data.

    Thread Starter j09

    (@j09)

    That worked like magic. Thank you very much!

    @madhavadasa

    1- Find the location of the header image in your child-theme.

    In you case it’s something like this:

    Image 1

    2- Either remove or comment out the current header. (make sure you have backups)

    3- Add your images. Both the logo for mobile and the text header for desktop.

    4- Add classes to the images to identify them.

    You want to end up with something like this:

    Image 2

    5- Add the following CSS code to your stylesheet:

    .big-header,
    .small-header {
      max-width: 100%;
      margin: 0 auto;
    }
    
    @media (max-width: 800px) {
      .big-header {
        display: none
      }
      .small-header {
        display: block
      }
    }
    
    @media (min-width: 800px) {
      .big-header {
        display: block
      }
      .small-header {
        display: none
      }
    }
    

    What this does is check for the screen size. If the screen size is bigger than 800px (your theme’s current cutoff point, it shows the small header. If the screen is bigger that 800px, it shows the large header.

    6- Check the results and modify according to your needs.

    Here’s a JsFiddle for reference

    Let me know if you need more help.

    Thread Starter j09

    (@j09)

    That worked flawlessly!

    Thank you very much.

    @madhavadasa

    There are three or four ways you can fix this. I will focus on the easiest methods below/

    1- Don’t use an image with text in it. This is a lot easier said than done, but the benefits are justifiable. There many reasons to opt for using CSS and html for any text element.

    2- Have both the logo and the header image on the page but use CSS to hide one of them depending on the screen size.

    Let me know which option sounds like what you want to do and I can expand further.

    @basilky

    Does the issue occur when you’re logged out?

    It could be that you’re serving cached pages to non-logged in users which explains why it’s faster when you use testing tools.

    Try logging out and see if the issue persists.

    Hello @lakelifestateofmind

    Yes, the <head> section should be in the header.php file.

    If you don’t see the header.php file in your child-theme that’s most likely due to the fact that you have no made any changes to it before.

    You may need to copy the header.php file from your theme and place the copied file in your child-theme’s directory.

    Once you do that you should be able to edit the header.php file in you child-theme to add the meta tag.

    Forum: Fixing WordPress
    In reply to: Real estate plugin

    @pdimaira

    You can try advanced classifieds and directory pro

    It allows you to create custom terms under a custom taxonomy – category – and then you can create custom fields – Unit has Square Footage, Electrical Power, Loading bays etc – and and link them to specific terms in the taxonomy.

    I think it serves your needs well.

    Good luck

    @sanjuchand

    You can access the site using the static IP.

    If you still cannot access the site using the new static IP, you should check to see if WordPress is pointed to that address in WP-config.php. You can do that using either SSH or FTP.

    Are you using the bitnami stack? Do you know how to use SSH?

    Also, you don’t need to add your new IP address in this post. it’s not needed

    @metropolisrob

    You’re most welcome. Glad you got it sorted.

    Hello @sanjuchand

    You need to set a static IP for your VM so that this issue does not occur again.

    Here’a very good guide on how to do that:
    Set static IP for GCP VM

    Once you go through that and you still have problems please post here.

    The code for your social icons is

    <div class="social-icons text-left">
    
      <a href="https://www.linkedin.com/in/metropolis-surveyors-llp-24a5934a/" target="_blank"><i class="fa fa-linkedin-square"></i></a>
    
       <a href="https://twitter.com/Metropolis_surv" target="_blank"><i class="fa fa-twitter-square"></i></a>
    
    </div>

    The classes fa fa-linkedin-square and fa-twitter-square indicate the use of FontAwesome.

    I don’t know how the icons are generated but just for testing you can use the following to create a link to facebook.

    <a href="YOUR_PAGE_LINK_GOES_HERE" target="_blank"><i class="fa fa-facebook-square"></i></a>

    and for Google+

    <a href="YOUR_PAGE_LINK_GOES_HERE" target="_blank"><i class="fa fa-google-plus-square"></i></a>

    And see of that is what you want to display.

    Thread Starter j09

    (@j09)

    That worked great. Thank you very much!

    @iromprey

    Your images are now “optimized” in the sense that they are compressed.

    As Alex noted, The fuzziness you refer too is caused by too much compression or by lossy compression.

    I have a different approach.

    Google’s complaint might be that your image dimensions are bigger than their display size.

    See this to understand what I mean

    While you have different srcset which should serve smaller image to smaller screens, the problem is that the display dimensions are always smaller than the file size served.

    The problematic images are only displayed as post thumbnails and not displayed inside the post.

    So here’s what I suggest.

    Deleted the fuzzy photos.

    Go back to your original non-fuzzy images and edit and resize them to around the maximum possible display width or around 300px then upload those again. optimize them and clear your cache and check google again.

    This can also be done programmaticly with WordPress media settings.

    @iromprey

    Noted.

    Your response headers…

    HTTP/1.1 200 OK => 
    Server => nginx/1.12.1
    Date => Wed, 06 Sep 2017 03:51:39 GMT
    Content-Type => text/html; charset=UTF-8
    Connection => close
    Vary => Accept-Encoding,Cookie
    Cache-Control => max-age=3, must-revalidate

    …indicate that you have already installed WP super cache. Am I correct? If so try flushing the cache before doing anything else and check with google one more time.

    If the same issue persists after your flush the cache,

    What I would do is take one of the problematic photos down and delete it from the media library, rename the file you have on your computer and upload it again via the media library uploader. This should allow it to be optimized by Ewww.

    Once that’s done, then I would set it s as the featured image one more time and check google. If the problem persists, then yes you will need the help of someone more competent.

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