GD Output Location widget 'fixed' position error

This topic contains 14 replies, has 3 voices, and was last updated by  Alex Rollin 5 years, 1 month ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #475534

    John Overend
    Full Member
    Post count: 103

    We’re using V2 and are using fixed widgets to keep the right information in view on listing pages, with the map widget and location widget in the sidebar.

    However, although every other widget seems to work fine with a fixed position, the location widget moves out to the right as you scroll down the page.
    You can see this behaviour at http://www.carsuk.net/places/united-kingdom/kent/east-peckham/car-service-repair/rcv-land-rover-specialists/

    Also, on the same page, we’re using code to not show Jetpack related posts on the custom post type and have tried ‘place’ ‘gd_place’ and more but we can’t get it to work. What’s the correct CPT to enter?

    #475538

    Kor
    Moderator
    Post count: 16516

    Hi John,

    Thanks for your reply. Could you try inserting the custom CSS code below and see if it helps?

    .single-gd_place .geodir-output-location {
        display: block!important;  
    }
    #475542

    John Overend
    Full Member
    Post count: 103

    Thanks Kor – that worked!

    I appreciated Jetpack issues aren’t your problem, but are we using the right CPT name?

    #475550

    Kor
    Moderator
    Post count: 16516

    Hi John Overend,

    Thanks for your reply and I’m glad that helped. As for the Jetpack related CPT, sorry, I’m not sure how it works.

    Thanks!

    #475552

    John Overend
    Full Member
    Post count: 103

    Okay. I just wanted to know that we’re using the right CPT name to exclude GD CPTs from displaying Jetpack related posts.

    #475596

    Alex Rollin
    Moderator
    Post count: 27815

    The CPT name is listed in the add listing URL or on the post types settings page. On your site at that link it is gd_place, yes. See ss attached

    #475601

    John Overend
    Full Member
    Post count: 103

    Thanks Alex – above and beyond!

    Sadly, we’ve tried that and it doesn’t work. Jetppack isn’t your problem but, oddly, if we remove the related posts altogether it screws up the listings pages layout!

    #475607

    Alex Rollin
    Moderator
    Post count: 27815

    OhMy I see what you mean. Why are you using that, then? 😉

    #475617

    John Overend
    Full Member
    Post count: 103

    Do you mean the related posts? It drives traffic round the regular site, but we don’t want it on the listings pages.

    #475620

    Alex Rollin
    Moderator
    Post count: 27815
    #475623

    John Overend
    Full Member
    Post count: 103

    Yes, we tried the code to remove related posts altogether (and add them back in on normal posts in the template instead) after the code we found to remove it just on a CPT failed to work (hence asking earlier about the right name). But if we do add the code it does odd things to the listings layout.

    #477144

    John Overend
    Full Member
    Post count: 103

    After doing an internal link audit we’ve decided, for now at least, to remove the related posts from the site.

    Switching it off works fine on all normal posts, but it messes with the layout of listings by overlaying what should be after the listing across the middle of it. Any ideas?

    #477176

    Alex Rollin
    Moderator
    Post count: 27815

    What happens if you disable the sticky sidebar?

    #477186

    John Overend
    Full Member
    Post count: 103

    Good suggestion – but it made no difference!

    On the profile section everything below the actual listing content – including the footer – renders in the middle of the profile content, but works fine on other tabs.

    #477213

    Alex Rollin
    Moderator
    Post count: 27815

    This is an issue with your theme and JP integration, then. Try to contact the theme author for support.

Viewing 15 posts - 1 through 15 (of 15 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket