On a very few piwigo acccount we got reported that the activity page wasn't loading properly. After some investigations we found out that the detail column in the activity table was a varchar(255) and it was used to store some serialized php. The detail column is used to store the user agent and it happened that if the user agent was too long, the serialized php went over 255 characters and so the serialized php could not be unserialized and that caused some errors.
For Piwigo 12 we can do a quick fix but in Piwigo 13 we plan to move the user agent from the $details to a separate column in the activity table.
On a very few piwigo acccount we got reported that the activity page wasn't loading properly. After some investigations we found out that the detail column in the activity table was a varchar(255) and it was used to store some serialized php. The detail column is used to store the user agent and it happened that if the user agent was too long, the serialized php went over 255 characters and so the serialized php could not be unserialized and that caused some errors.
For Piwigo 12 we can do a quick fix but in Piwigo 13 we plan to move the user agent from the $details to a separate column in the activity table.
<!-- github-sync-id:1276877534 -->
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.
On a very few piwigo acccount we got reported that the activity page wasn't loading properly. After some investigations we found out that the detail column in the activity table was a varchar(255) and it was used to store some serialized php. The detail column is used to store the user agent and it happened that if the user agent was too long, the serialized php went over 255 characters and so the serialized php could not be unserialized and that caused some errors.
For Piwigo 12 we can do a quick fix but in Piwigo 13 we plan to move the user agent from the $details to a separate column in the activity table.