Forum Replies Created
My guess is that this is an issue with the image resizing.
What happens if you remove the width/height settings from the list options?
This is a great idea. We’ll look at implementing it in our block rebuild 🙂
I agree, this would be much better than the current implementation.
Also, it’s possible to simply add your own masonry configuration and keep the WPSP setting turned off – that way you have full control over the setup, you just need to add the correct selectors to the configuration 🙂
Sorry for missing this!
This is fixed in 1.2.0, which is currently a development version: https://wpshowposts.com/wp-show-posts-1-2-0/
We’ll be releasing it soon.
Thanks!April 15, 2021 at 9:11 am in reply to: Sticky posts: issue + how-to style as featured post #29279
Sticky posts in general have issues whenever you add any sort of category/term. This is why they don’t work by default on archive pages: https://wordpress.stackexchange.com/questions/117279/sticky-posts-not-sticking-to-top-of-category-archive
Not sure what the best solution would be here, unfortunately. The solution at the URL I shared wouldn’t really work in this specific scenario.
I just did some looking around on how to target specific posts to order them, but couldn’t come up with anything. The order and orderby params in the WP Query aren’t great, unfortunately.
We don’t have any bulk actions/ability to copy the list. All of the Pro features can be found while editing the post lists themselves.
Let us know if there’s any other options you’re having trouble finding 🙂
This is a bbPress issue we’ve been battling with. I’ve just tried something else – let me know if it continues to happen.
How did you set up the featured post? Any chance you can link us to the page?
This kind of thing is notoriously difficult to deal with in WordPress. Usually it means using the
pre_get_postsfilter to change how many posts per page display on those paginated pages.
No problem 🙂
Definitely strange, especially as it isn’t happening on your other sites.
I wonder where the search engines are even finding those links – they aren’t directly accessible from the plugin. It’s the AJAX action that’s initiated once the heart is clicked.
One last thing that comes to mind – we could try adding
rel="noindex nofollow"to the link. It would involve manually changing the plugin file, but I’m happy to provide instructions on doing that if you’d like to give it a try.
Let me know 🙂
“True random” is very difficult to achieve in programming.
The orderby rand option works quite well, but not when it comes to pagination. That’s when you need to implement a “seed”, which WPSP doesn’t do: https://wordpress.stackexchange.com/questions/31647/is-it-possible-to-paginate-posts-correctly-that-are-random-ordered
While it’s possible with some filters, it’s not something I personally have a ton of experience with, unfortunately.
Masonry will display your posts in a waterfall/stacked kind of layout where no space is “wasted”. You can see it in action here: https://masonry.desandro.com/
A “featured post” simply displays the post as a wider width than the other posts when displaying your posts in columns.
Hope this helps!
Strange – Google should be respecting your robots.txt.
If it’s causing a big issue like this, the safest thing you can do is turn off the “Like” option in your lists – that will prevent it right at the root. Not ideal, as it’s a cool feature, but it may be a good solution until Google clears the indexed URLs.
Adding the following should prevent these links from being followed/indexed:
Have you requested that the URLs be removed? Are you sure they’re continuing to get indexed since adding that line to your robots.txt?