Forum Replies Created

Viewing 15 replies - 61 through 75 (of 1,766 total)
  • Plugin Author Creative Themes

    (@creativethemeshq)

    Hi @martinkst, this is a friendly reminder 🙂

    Please get back to us with more details so we could be able to understand your problem and provide a solution.

    Have a good day!

    Plugin Author Creative Themes

    (@creativethemeshq)

    @martinkst please let us know what WP CLI commands you are trying to execute and what error you are getting and we will make sure to check everything and provide relevant fixes where needed.

    Theme Author Creative Themes

    (@creativethemeshq)

    Hello,

    No, this code is not associated in any way with Blocksy. We never would allow such a code to make it into our theme or plugin.

    Please conduct a thorough audit on your website, it seems like it is deeply infected with some malware that keeps re-adding the malicious code even after you clean up the relevant file. I would suggest getting in touch with Patchstack, I’m sure they will be able to help you in no time.

    I hope you manage to get this resolved in a timely fashion.

    Best,
    Andrei

    Theme Author Creative Themes

    (@creativethemeshq)

    @zerhida thanks a lot for the words! We really appreciate it!

    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

    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)

    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.

    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.

    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.

    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

    Theme Author Creative Themes

    (@creativethemeshq)

    Hi @mariuslt,

    Thank you vey much for your kind words, this means a lot for us 🙂

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hello @jgarma,

    Sorry about this question but about what website are you exactly referring?

    Plugin Author Creative Themes

    (@creativethemeshq)

    We pushed out yesterday a new update with the fix for the WP CLI check and also some better readme annotations for the available commands.
    In the next one we’ll be aiming for pushing the combined command for installing a starter site.

    We’ll be reaching out to you for give you a way to beta test what we’re building.

    Thanks again for bringing this up!

    Plugin Author Creative Themes

    (@creativethemeshq)

    Yes, that’s the order of the steps pretty much!

    Seems like the WP_CLI::runcommand() is exactly what we need to compose this — it runs the separate commands in sub-processes, which is exactly what we’re looking for (hopefully this is cross-platform too).

    Will try to play with it and hopefully we’ll release a combined command too. Watch out for our changelog please, we’ll make sure to reference it there as soon as it’s ready. With or without the combined command, the update from this week will have the above described fix for the theme check.

    Thanks again for your feedback!

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hi Kyle,

    Appreciate your input!

    Sure thing, we will get this fixed in the next update. It certainly wasn’t our intention to get the CLI commands to not get registered at all.

    At the moment, the main commands are the wp blocksy demo * commands, which allow you to install a starter site using the WP CLI. We will certainly add more instructions on how to use them.

    In a few words, you have to run them in a specific order (I know there’s no way you could have known that from our instructions) but we deliberately made it this way. We made it work like this because each next step in the process depends on the previous one being executed & its output being loaded in the current env (download & activate a plugin, for example). Doing that in one simple command is not so easy, unless we involve dispatching sub-processes so that with each step the WP gets booted anew.

    We will do our best to make it as explicit as possible.

    Are you trying to automate something?

    Thanks again!

    Kind regards,
    Andrei

Viewing 15 replies - 61 through 75 (of 1,766 total)