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

    We’ve identified the problem with 4.9.x version and provide a fix in the 1.8.2 Can you make the update? It should be OK now.

    Please let me know.

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    It works. But what happened with the accordion block? My accordion block was invalid and had to convert it to HTML. And I can’t find the Accordion block when searching.

    Hi,

    When did you create your accordions? We’ve updated the whole block in the 1.8 version to fit latest Gutenberg evolution and add the possibility to load inner blocks in each accordion.

    Cheers,

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    Around a week or two ago.

    That’s it, we’ve updated the whole block in the 1.8 version to fit latest Gutenberg evolution and add the possibility to load inner blocks in each accordion.

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    You can’t just update the plugin with changes that break things. At least not without warning your users and/or giving them the ability to convert their current blocks to your new version.

    This is enough to give you a one star review.

    Hi,

    Note that if we had had the possibility to make an automatic block transformation (from old accordion to new one) we would have done it of course, but the Gutenberg HTML block control does not allow that.

    Could we anticipate that? Yes and no.
    We could have done the accordion block based on the actual model but at the time Gutenberg was still not recommended to be used in production website so we choose another option thinking that a migration would have been possible then.

    Giving such generous review won’t help Gutenberg growing and if there’s less free plugin developer the Gutenberg possibilities will be very limited. Feel free to do what you want with your review.

    Farewell.

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    You could and should have, at the very least, informed your users that the upgrade would break previous functionality.

    Take a look at this article and this one.

    As for the review, this review has absolutely nothing to do with Gutenberg in general. It is about how you handle people who use your plugin when you make changes that breaks functionality that people use.

    Don’t misunderstand me: I understand why you made the change you did: but we have the right to know before we upgrade that your new version will break functionality. You SHOULD at the very least have added it to the change-log.

    The fact is that the initial problem was fixed and the block we’ve rebuild does not break the website frontend but the admin edition part of this block, so it let you an opportunity to rebuild it easily with even more options in it (this is what all users have done, including us).

    As for the review, this review has absolutely nothing to do with Gutenberg in general.

    In fact it does if you consider the WordPress ecosystem.

    But hey, finally I wish you good luck in using Gutenberg in the future 🙂

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    The fact is that the initial problem was fixed and the block we’ve rebuild does not break the website front-end but the admin edition part of this block, so it let you an opportunity to rebuild it easily with even more options in it (this is what all users have done, including us).

    Yes, the new version doesn’t break the accordions in the front-end (which is the least thing that we can expect of you when you break features), you still broke it in the back-end. But you still should have informed your users that you broke it in the back-end so that your users had to re-create the accordions they created (which btw, can be a tedious process depending on how much they’ve used the old accordion block type).

    In fact it does if you consider the WordPress ecosystem.

    Haha. That statement is ridiculous. Does that mean that every negative review about a plugin will prevent WP from growing? Haha. Well, that would be unfortunate and if that actually were true; then WP would be long dead as negative plugin reviews are far from a new thing.

    Our goal with the WordPress.org repository is to have a good place for users to get plugins that fulfill their needs. The reviews are an extension of that, and should viewed as a way for users to educate other users on their experiences. Also a review is about an experience. If someone’s experience with your product is poor, that doesn’t make their review invalid. And to go back to that previous statement, the way you react to those poor experiences is going to impact your reputation, and that of your plugin, a heck of a lot more than that review.

    – From Make WordPress Plugins

    ——–

    Anyways, and on a “more” serious note: What I miss most from the old Accordion block was that you could group multiple accordions into one accordion (and by that style multiple in one go). Now you have to manually style/modify each and every accordion. Incredibly tedious and not user friendly at all.

    BUT: I do like the option to add blocks into the accordion. But it would be great and make a massive user-friendly/efficiency boost if you would add some form for “parent” accordion-block that we could use to style all the accordion blocks so that we wouldn’t have to manually do it on each accordion.

    If the purpose of separating each accordion into a single accordion block is to give the opportunity to style each of them; you can have the child-accordion block override the style from parent. That way we could do both. 🙂

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    It would be nice to be able to make it so that it is possible to click on the title to expand the accordions, not just the icon. Either as default or as an option in the block settings.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Hey,

    Refer to my review.

    Nope. See, that’s review extortion and that doesn’t work here. I’ve archived your review while you sort out your support issue.

    Feel free to leave a new review afterward you’ve sorted that out one way or the other.

    Thread Starter Marius Flugsrud

    (@tekniskblogghjelp)

    Nope. See, that’s review extortion and that doesn’t work here. I’ve archived your review while you sort out your support issue.

    Hey,

    The thread is pretty long, so what precisely do you refer to when you say “that’s review extortion”?

    And to explain my review: my low review doesn’t really have much to do with the support, it does, however have a lot about the way the plugin author(s) update(s) their plugin and how they inform their users about changes that break functionality (back-end and/or front-end).

    I added the following to the review for a few hours ago as I realised that the low rating needed a better explanation as to the cause of the low rating):
    “The reason I gave the plugin a one-star is because that they don’t let their users know when they break functionality in a new version. The plugin is nice when you forget that part. Just don’t expect consistency in whether or not your blocks will work or not. They may suddenly break them in a future version, without letting you know.”

    Would that still be considered review extortion? I’m not trying to argue or anything, just trying to understand. 🙂

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Plugin causes white screen on WP 4.8.9’ is closed to new replies.