Wait, you updated piwigo to the latest and got this error now? Or did you update your database, like to mysql8? I have seen the issue of not encapsulated keywords like rank, section, date, time and a few more, and there are other issues open about this, including a few pull requests to solve parts of the misery.
Wait, you updated piwigo to the latest and got this error now? Or did you update your database, like to mysql8? I have seen the issue of not encapsulated keywords like rank, section, date, time and a few more, and there are other issues open about this, including a few pull requests to solve parts of the misery.
<!-- github-comment-id:443552691 -->
Hello pstimpel. Yes I updated software for Piwigo yesterday 02/012/2018 . I didn't dump the database though. Should I have done that? That seemed drastic to me but perhaps that was my error. In the end as I couldn't have a site with no photos I had to install a fresh version of Piwigo in a different folder and upload photos again. Changing the code on the webpages. As I could not access the broken version of Piwigo I could not see which photos I had before to make sure it was the same. Incase others get this problem thought I should bring it to someones attention.
Hello pstimpel. Yes I updated software for Piwigo yesterday 02/012/2018 . I didn't dump the database though. Should I have done that? That seemed drastic to me but perhaps that was my error. In the end as I couldn't have a site with no photos I had to install a fresh version of Piwigo in a different folder and upload photos again. Changing the code on the webpages. As I could not access the broken version of Piwigo I could not see which photos I had before to make sure it was the same. Incase others get this problem thought I should bring it to someones attention.
<!-- github-comment-id:443642540 -->
Thank you for your response to this. If you know about the "Dump database " option when updating the software that would be great. Then I will know for future. Thank you again.
Thank you for your response to this. If you know about the "Dump database " option when updating the software that would be great. Then I will know for future. Thank you again.
<!-- github-comment-id:443651741 -->
I am just an user, as you are. However, I would dump my database before every update. I know, I am paranoid somehow
I am just an user, as you are. However, I would dump my database before every update. I know, I am paranoid somehow
<!-- github-comment-id:443677244 -->
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.
Just upgraded to latest version of Piwigo and get this error. can no longer access admin or even see images on site.
Wait, you updated piwigo to the latest and got this error now? Or did you update your database, like to mysql8? I have seen the issue of not encapsulated keywords like rank, section, date, time and a few more, and there are other issues open about this, including a few pull requests to solve parts of the misery.
Hello pstimpel. Yes I updated software for Piwigo yesterday 02/012/2018 . I didn't dump the database though. Should I have done that? That seemed drastic to me but perhaps that was my error. In the end as I couldn't have a site with no photos I had to install a fresh version of Piwigo in a different folder and upload photos again. Changing the code on the webpages. As I could not access the broken version of Piwigo I could not see which photos I had before to make sure it was the same. Incase others get this problem thought I should bring it to someones attention.
Wow, that sounds harsh. Hopefully the core devs will fix this soon - even it is a monster job.
Thank you for your response to this. If you know about the "Dump database " option when updating the software that would be great. Then I will know for future. Thank you again.
I am just an user, as you are. However, I would dump my database before every update. I know, I am paranoid somehow
Think you are right though and again thank you. In future I will dump the database.
fixed in #919 (even if we still find some problems, see #1060)