Dear Yurcee,
Thank you very much for your thoughtful and detailed response. I’m sure your writing will also be helpful to other Obsidian users reading this thread. I, too, would like to share my experiences with Obsidian and its plugins in the future. I believe such posts are extremely valuable for both developers and users alike.
However, the response you gave me, no matter how valuable its content, does not align with my motivation for opening this topic. I’m telling you that the 1.7.4 update has negatively impacted my app experience, but you want to place all the blame on plugins alone, which isn’t fair. If plugins and snippets that worked seamlessly in the previous version start causing issues in the next version, we can’t solely blame the plugin developers. In that case, Obsidian developers should ensure backward compatibility for these plugins to provide a good user experience and to prevent stability issues like those both you and I are facing. Don’t you agree?
You asked why I haven’t updated certain plugins. This is precisely why. I’m so tired of the risk of updates breaking things that I now try to keep updates to a minimum, reading the changelog carefully each time.
If any Obsidian developers are reading this, please review the negative effects that the changes in 1.7.4 have had on plugins and snippets, and take concrete steps toward backward compatibility in the next update. If there are incompatible plugins, it’s within your power to remove them from the active development list. Additionally, before releasing an update, sharing the beta version of the update with plugin developers first and waiting to release the full version until you’ve received confirmation from them that they’re ready could also be an option.
But as users, I don’t think we deserve to face these issues because of such factors. For instance, I spent a lot of time identifying that the issue was coming from version 1.7.4, which was not a pleasant experience.
Thank you…