• Resolved pmabraham

    (@pmabraham)


    There was a bug that was fixed about a month ago where sticky posts where brought into the advanced post query EVEN if the category tag was not included. The bug is now back.

    The page in question is only for the category of “Prognostication” and is now bringing in sticky posts from other pages and categories.

    Can this please be fixed?

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter pmabraham

    (@pmabraham)

    This came out last year after an update and is now back. Looking for a fix that will last ;-)
    
    "Sergiu Radu (CreativeThemes)
    
    Dec 25, 2023, 09:30 GMT+2
    
    Hello Peter,
    
    Yes, you are right the issue was introduced in the last update but it was actually caused by WordPress sticky posts logic.
    
    We reworked a little bit how sticky posts are outputted in frontend because a lot of users requested for this feature but seems on some specific setups this was not working very well because of the WordPress logic.
    So, we had to add some more checks in order to prevent this weird behavior.
    
    I am glad everything works fine now.
    And like I already mentioned, there is no need to worry, we are here always and are ready to help with all problems.
    
    Wish you all the best and have a wonderful Holiday Season among your loved ones 🙂
    
    Let us know in case you will have any other questions.
    
    Kind regards,
    Sergiu."


    • This reply was modified 2 years ago by pmabraham.
    Eduard

    (@cteduard)

    Hello @pmabraham

    While there was indeed a change in the latest update regarding sticky posts, it was done for the better. The old change that was requested was actually incorrect as it went against WordPress’ built in conventions and some users actually reported this as a bug.

    For example, even WordPress’ default core implementation works exactly like this. Sticky posts are shown if a taxonomy query is included and there’s an option to disable this. Here’s a short video that demonstrates both the built in “Query Loop” block, as well as our “Advanced Posts” block – https://streamable.com/o0abcf. Notice the work identically.

    Maybe you could try deactivating sticky posts for your “Advanced Posts” blocks, as per the video above? That should solve the issue for you, letting you continue using taxonomy queries.

    Hope this clears things up!

    Thank you.

    Thread Starter pmabraham

    (@pmabraham)

    I am a PRO user, and this makes Blocky Pro unusable for my goals. This was fixed and now you are justifying a huge bug. Sad.

    Theme Author Creative Themes

    (@creativethemeshq)

    @pmabraham We had an internal discussion about this case and honestly the way the sticky posts behave now is correct, just like my colleague Eduard told you. Can you please explain why you think this is a bug? Just because something isn’t behaving in a way that you don’t expect it doesn’t mean that it’s also a fault. That is why we provide options everywhere — so you can adjust everything to your needs. Why can’t you just use the option to disable the sticky posts from the “Advanced Posts” block?

    We really don’t understand why you can’t use the option. Please explain your use case in more details, maybe we are all missing an important point in your use case here.

    Thank you and looking forward to hear back from you.

    Best,
    Andrei

    Thread Starter pmabraham

    (@pmabraham)

    The advance block on the page https://compassioncrossing.info/how-much-longer/ states to ONLY bring in posts that have the category of “Prognostication”

    The first two posts on that page ARE NOT in that category!

    The reason those two posts are sticky is because your own team stated that would be the best way to have the one post show up on https://compassioncrossing.info/end-of-life-nutrition/ as the first post and the other post show up on https://compassioncrossing.info/about-hospice/ as its first post.

    I am not a web designer, but I paid good money for Blocky Pro and your team fixed a bug that your team acknowledged as a bug the time it was fixed.

    It is one thing for a sticky post to show in the CATEGORY if the category is being pulled, it is completely WRONG for a sticky post to show when it IS NOT in the category.

    Theme Author Creative Themes

    (@creativethemeshq)

    @pmabraham yes, I totally understand you but things are not working like that. Just because you are pulling posts from a category (that is, you’re modifying the underlying taxonomy query) it doesn’t mean that sticky posts should be disabled too right away. Please understand, the Advanced Posts block covers a very wide range of use cases and automatically hiding the sticky posts just because you changed something in the query isn’t right.

    We have some customers that do need the sticky posts to appear at the top when they’re pulling some posts from a category. For them, the sticky posts are important posts that they want to have at the top.

    Can you see the contradiction here?

    Our job here is to make unopinionated tools that allow you to get your job done. And to solve this contradiction, we introduced this option that allows you to decide, on a block my block basis, whether to display sticky posts or not: https://share.cleanshot.com/fhzj9hpw

    Did you try to switch this option to “Exclude”? It’s 2 clicks away and your problem will be gone.

    Please try to put yourself in our position. I will repeat myself: just because something doesn’t behave the way you expect it too, it doesn’t mean it’s a bug. That’s why we have options for.

    I hope this helps.

    Thread Starter pmabraham

    (@pmabraham)

    “We have some customers that do need the sticky posts to appear at the top when they’re pulling some posts from a category. “

    Correct, IF the the stick IS part of the category. The first two posts ARE NOT part of the “Prognostication” category. Is there a reason why you believe ALL sticky posts should be pulled IF THEY ARE NOT a part of the category being pulled?

    I don’t want to exclude the category of the other posts because there is a potential that a nutrition post will be part of “Prognostication” and an about hospice post will be part of the “Prognostication” category.

    I did programming for 30 years before becoming a hospice nurse taking care of the terminally ill. It is not good programming when you have to put virtual band aides on various areas just because a developer refuses to understand the damage caused by broad based changes.

    IF the sticky posts shown on the “How Much Longer Page” were of the category “Prognostication,” your answer would be perfect! You would be correct! However, none of those sticky posts are part of the “Prognostication” category and what is why your answers, from my perspective are incorrect and wrong. This is a bug because I ONLY asked for posts from the “Prognostication” category . I didn’t ask for any other posts from any other category to be pulled. I should not have to exclude what should not already be present because the first two posts are NOT part of the “Prognostication” category!

    Theme Author Creative Themes

    (@creativethemeshq)

    Correct, IF the the stick IS part of the category. The first two posts ARE NOT part of the “Prognostication” category. Is there a reason why you believe ALL sticky posts should be pulled IF THEY ARE NOT a part of the category being pulled?

    Not correct. Sticky posts are just sticky. Not sticky per category. And yes — some people do need that, like I said already.

    I don’t want to exclude the category of the other posts because there is a potential that a nutrition post will be part of “Prognostication” and an about hospice post will be part of the “Prognostication” category.

    You don’t have to exclude the category, you have to exclude the sticky posts from your block. Did you try to do it?

    This is a bug because I ONLY asked for posts from the “Prognostication” category . I didn’t ask for any other posts from any other category to be pulled. I should not have to exclude what should not already be present because the first two posts are NOT part of the “Prognostication” category!

    Again, this is not correct. Sticky posts are not being passed through the query and no filtering is performed on them. Sticky posts are just prepended at the beginning of the 1st page and nothing more. For that reasons, this is not a bug.

    Really, we complicate things more than we should. Why can’t you change the mentioned option? Again, did you try it?

    Also, again, the “Query Loop” block from the core WP works exactly the same way, just like Eduard showed you. You have the option to control whether to show or not the sticky posts and their display isn’t affected by pulling or not posts from a category.

    Thread Starter pmabraham

    (@pmabraham)

    The caveat of excluding sticky posts when I ONLY want the category posts then gets the question of what happens when a sticky post is a part of the category and all I want are the sticky posts for that category only.

    Theme Author Creative Themes

    (@creativethemeshq)

    The caveat of excluding sticky posts when I ONLY want the category posts then gets the question of what happens when a sticky post is a part of the category and all I want are the sticky posts for that category only.

    This is not how sticky posts work and for this case you should not even use the sticky posts feature. Such a use case can only be implemented with custom code. If you need it, we can give you an example on how to do it.

    There is such thing as “sticky posts only from the current category”. Sticky posts are global.

    Thread Starter pmabraham

    (@pmabraham)

    The reason those two posts are sticky is because your own team stated that would be the best way to have the one post show up on https://compassioncrossing.info/end-of-life-nutrition/ as the first post and the other post show up on https://compassioncrossing.info/about-hospice/ as its first post.

    Thread Starter pmabraham

    (@pmabraham)

    I’m willing to learn if you want to share with me code, but I am leaving shortly to see patients (I work as a local traveling visiting hospice nurse).

    Thank you.

    Theme Author Creative Themes

    (@creativethemeshq)

    The reason those two posts are sticky is because your own team stated that would be the best way to have the one post show up on https://compassioncrossing.info/end-of-life-nutrition/ as the first post and the other post show up on https://compassioncrossing.info/about-hospice/ as its first post.

    I know that already 🙂 And I showed how you can deal with this — by using the option. Please, let’s not keep going circles. Just use the option to disable the sticky posts from the block and let’s move on.

    Theme Author Creative Themes

    (@creativethemeshq)

    Please make a separate support request about the special use case that you mentioned and I will give you a detailed write up on how to do it. But it is outside the scope of the current discussion.

    I hope the current matter is settled now.

    Good luck with your work, have a great day ahead.

    Best,
    Andrei

    Thread Starter pmabraham

    (@pmabraham)

    Acknowledged and thank you.

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

The topic ‘Bug in Advanced Posts is back’ is closed to new replies.