Hello,
Each time I am doing upgrades, I breack my Piwigo (deployed on shared hosting managed services).
# Bug
Several picies of codes are doing calls where port 80 is forced in the URL even if we are in HTTPS (for example, authentication is brocken).
# Resolution
I can see on forums this is a recurent issues and a lot of people are facing this issue.
It seems the correction is already provided by the community:
https://fr.piwigo.org/forum/viewtopic.php?id=28052#p225699 (sorry, this forum is in French)
On my side, I confirm this correction is well working.
## Environment
- **Version**: 11.5.0
- **OS**: Linux webdb46.lwspanel.com 4.19.0-6-amd64 # 1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64
- **Web server**: Linux shared hosting
- **PHP**: 7.4.23
- **MySQL**: 5.5.5-10.3.25-MariaDB-0+deb10u1
- **ImageMagick**: 6.9.7-4
Thanks and best regards,
<!-- github-sync-id:1029217584 -->
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.
Hello,
Each time I am doing upgrades, I breack my Piwigo (deployed on shared hosting managed services).
Bug
Several picies of codes are doing calls where port 80 is forced in the URL even if we are in HTTPS (for example, authentication is brocken).
Resolution
I can see on forums this is a recurent issues and a lot of people are facing this issue.
It seems the correction is already provided by the community:
https://fr.piwigo.org/forum/viewtopic.php?id=28052#p225699 (sorry, this forum is in French)
On my side, I confirm this correction is well working.
Environment
Thanks and best regards,