Man, thanks for the work on the update. However, I would like to express how annoying it is to lose a complete installation. I would appreciate a bit of more warning in such "YOU MUST UPDATE OR WE ARE GOING TO DIE" emails.
Finally, you tell me AFTER the update that you killed 90% of the plugins, probably due incompatibility. Man, I would have liked it to decide on my own if I want to update now where most of the plugins do not work anymore.
Writing software means not only writing cool code and nifty features, it means as well thinking about the responsibility.
Best Regards
Peter
Man, thanks for the work on the update. However, I would like to express how annoying it is to lose a complete installation. I would appreciate a bit of more warning in such "YOU MUST UPDATE OR WE ARE GOING TO DIE" emails.
Finally, you tell me AFTER the update that you killed 90% of the plugins, probably due incompatibility. Man, I would have liked it to decide on my own if I want to update now where most of the plugins do not work anymore.
Writing software means not only writing cool code and nifty features, it means as well thinking about the responsibility.
Best Regards
Peter
<!-- github-sync-id:517802269 -->
I'm sorry for your bad experience. You don't give much details and your post sound much more like a rant. Maybe the forum https://piwigo.org/forum would have been a better place for this discussion.
For now, I simply close this issue because I don't know how to "fix" it :-/
I'm sorry for your bad experience. You don't give much details and your post sound much more like a rant. Maybe the forum https://piwigo.org/forum would have been a better place for this discussion.
For now, I simply close this issue because I don't know how to "fix" it :-/
<!-- github-comment-id:583491814 -->
May I ask where exactly this was a rant? I really appreciate your efforts to provide Piwigo. I like it very much, wrote extensions for it, run my website for years using it.
Bit If you cannot handle simple requests for more usability on major updates, I guess you should ask someone else to maintain the software, or at least to run the issue tracker for you.
How to fix it? Hm, maybe a check for incompatible installed extensions would be cool, or a warning. But leaving the user alone after an update with a broken installation where he has to fix it himself on source code level is not my understanding of maintaining software and handling the responsibility that comes with it.
BR
Peter
May I ask where exactly this was a rant? I really appreciate your efforts to provide Piwigo. I like it very much, wrote extensions for it, run my website for years using it.
Bit If you cannot handle simple requests for more usability on major updates, I guess you should ask someone else to maintain the software, or at least to run the issue tracker for you.
How to fix it? Hm, maybe a check for incompatible installed extensions would be cool, or a warning. But leaving the user alone after an update with a broken installation where he has to fix it himself on source code level is not my understanding of maintaining software and handling the responsibility that comes with it.
BR
Peter
<!-- github-comment-id:583510045 -->
OK Peter, please open a discussion on https://piwigo.org/forum because I don't want to discuss this matter on Github, this is not the appropriate place in my opinion.
OK Peter, please open a discussion on https://piwigo.org/forum because I don't want to discuss this matter on Github, this is not the appropriate place in my opinion.
<!-- github-comment-id:583538856 -->
I've just checked and it is not
Le mer. 8 avr. 2020 à 09:56, Nicksxs <notifications@github.com> a écrit :
> @plegall <https://github.com/plegall> why the install script and doc site
> is all 403 forbidden
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Piwigo/Piwigo/issues/1115#issuecomment-610810172>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAFT5DPI4RGBRM6I64AAWFDRLQU2DANCNFSM4JJDIPAQ>
> .
>
<!-- github-comment-id:610813487 -->

so it comes from your side ...
<!-- github-comment-id:610830170 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Man, thanks for the work on the update. However, I would like to express how annoying it is to lose a complete installation. I would appreciate a bit of more warning in such "YOU MUST UPDATE OR WE ARE GOING TO DIE" emails.
Finally, you tell me AFTER the update that you killed 90% of the plugins, probably due incompatibility. Man, I would have liked it to decide on my own if I want to update now where most of the plugins do not work anymore.
Writing software means not only writing cool code and nifty features, it means as well thinking about the responsibility.
Best Regards
Peter
I'm sorry for your bad experience. You don't give much details and your post sound much more like a rant. Maybe the forum https://piwigo.org/forum would have been a better place for this discussion.
For now, I simply close this issue because I don't know how to "fix" it :-/
May I ask where exactly this was a rant? I really appreciate your efforts to provide Piwigo. I like it very much, wrote extensions for it, run my website for years using it.
Bit If you cannot handle simple requests for more usability on major updates, I guess you should ask someone else to maintain the software, or at least to run the issue tracker for you.
How to fix it? Hm, maybe a check for incompatible installed extensions would be cool, or a warning. But leaving the user alone after an update with a broken installation where he has to fix it himself on source code level is not my understanding of maintaining software and handling the responsibility that comes with it.
BR
Peter
OK Peter, please open a discussion on https://piwigo.org/forum because I don't want to discuss this matter on Github, this is not the appropriate place in my opinion.
@plegall why the install script and doc site is all 403 forbidden
I've just checked and it is not
Le mer. 8 avr. 2020 à 09:56, Nicksxs notifications@github.com a écrit :
@flop25

so it comes from your side ...
please use another thread after checking on your side