Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi,

    great ??

    i actually solved my case by adding Sticky-kit into my theme files, which has this “stick to bottom on way down, stick to top on way up” functionality by default.

    https://github.com/leafo/sticky-kit

    It’s open source, you might find looking at the code useful in case you decide to work on this?

    – Julius

    Hi!

    My questions is kind of related. I think the basic design of how an element sticks should be improved.

    I’m making my sidebar (#secondary) sticky. On basically all screens its too long to fit vertically. As i set it as a sticky, I will only be able to see the top portion of my sidebar as the top part sticks to the top of page and never scrolls down.

    I can add a push-up element, i added the footer (#colophon) as one. But this means the user needs to scroll all the way to the bottom of the page before seeing the bottom part of the sidebar. It would be important to first scroll through the sidebar, then stick it to the view when reaching bottom of the sticky sidebar.

    The behaviour i mean is demonstrated in the Newspaper theme for example: https://demo.tagdiv.com/newspaper/td-post-what-do-i-need-to-make-it-in-business/
    (the widget scrolls to the bottom, then sticks after this. The reverse happens when user scrolls up, which is nice).

    I think this should be default design in all sticky widgets. Is it possible to implement this with e.g. modifying the CSS or adding som other code?

    • This reply was modified 7 years, 9 months ago by krut.
    • This reply was modified 7 years, 9 months ago by krut.

    Hi!

    I had the same error on a site i work with around a month ago. Here the site at some point turned unreachable, giving the http500 error. In Podcast post types posts and all other alternatives are unticked. After removing SSP the site went online again.

    Now, with the latest updates of the plugins, there seems to be no errors with SSP activated. Checking the ssp-functions.php -file shows that these lines

    if ( $include_podcast ) {
    $podcast_post_types[] = ‘podcast’;
    }

    have moved to around line 351-354 (v. 1.16.3)

    Is the error fixed, or do i need to add “$podcast_post_types = array();”
    inside the if statement? Sorry, i’m quite uncomfortable with php editing.

Viewing 3 replies - 1 through 3 (of 3 total)