- Issue created by @bramvandenbulcke
- Status changed to Postponed: needs info
over 1 year ago 6:06am 23 October 2023 - π©πͺGermany Anybody Porta Westfalica
@bramvandenbulcke looks like you just have to confirm the given message, as you may have an older version in place that needs to be replaced?
- π§πͺBelgium bramvandenbulcke
The script didn't show an option to confirm. It ends with the error.
In the end all my scripts are in place and when I run composer update again, the error isn't shown anymore.
But it's possible others will encounter the issue and maybe there is some explanation for it.
- π©πͺGermany Anybody Porta Westfalica
[y]es, [n]o, [A]ll, [N]one, [r]ename: NULL
I guess then your script skips the question for some reaons.
But this is not this module's fault or something we can influence. Typical composer behavior for git assets that changed locally / differ from remote.
- πΊπΈUnited States fsayoub
@Anybody β or bramvandenbulcke β were you able to get around this? Having the same issue now.
- π©πͺGermany Anybody Porta Westfalica
@fsayoub for us it's working flawlessly since months. I guess this must be local reasons or composer version or configuration or something like that? Any feedback from the others?
- πΊπΈUnited States fsayoub
These are the current versions I have:
"bower-asset/photoswipe": "^5" "dimsemenov/photoswipe": "^5.4" "drupal/photoswipe": "^5.3" "npm-asset/photoswipe-dynamic-caption-plugin": "^1.2"
I get an error on the status report:
Local library folder found, but library seems to be corrupted, please require the photoswipe library correctly!
- πΊπΈUnited States chri5tia PDX
I was getting this error as well. Try enabling package list in composer first:
composer config repositories.asset-packagist composer https://asset-packagist.org
- π¬π§United Kingdom mattjones86 π¬π§ GMT+0
The problem is because they have two identically named files in their Github repo:
https://github.com/dimsemenov/PhotoSwipe/tree/master/.github
MacOS (and probably Windows) by default has a case insensitive filesystem, so gets very confused when both of these files are attempted to be unzipped to the same directory. Linux would not have any issues.
For me the package to still extract and install, but it does seem to ignore my
installer-paths
setting and dump in the vendor dir, giving the illusion it's not installed at all. Still debugging that.