Custom Query (1173 matches)
Results (241 - 243 of 1173)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5612 | fixed | Atom feed shows bad web link | ||
| Description |
with mediagoblin 0.10, atom feed shows a base_url of 127.0.0.1:6543, which correspond to the main paste server. Server has a standard installation with main paste and nginx front, with advised configuration. Previous 0.9 installation was similar and atom feed showed the public web dns (without port as it is served on 80). surely missing a configuration there or maybe a tweak to add to nginx conf? thanks |
|||
| #5620 | fixed | Download link missing on 0.10 | ||
| Description |
Hello, since the new version, when displaying a video, under the label "download" there isn't the link to download the media anymore. It's still there on all the other media page generated before migration though. I've raise the priority to major because although mediagoblin can be viewed as a streaming website, this link is mandatory for iOS user where the video viewer is not compatible and it was their only mean to actually watch the video. thanks again! |
|||
| #5626 | fixed | Upgrade issue from 0.10 to 0.11 | ||
| Description |
following the upgrade guide (and the installation guide just in case), I've encounter the following issue during upgrade: 1) after launching this command: ./bootstrap.sh && VIRTUALENV_FLAGS='--system-site-packages' ./configure && make it fails during setup saying idna3.2 is installed (as one package require >2 and it picks the last available) but a later one require < 3 (this could be removed because python2 support has been dropped). workaround was: ./bin/pip uninstall idna ./bin/pip install idna==2.10 and relaunch the last step: ./bin/python setup.py develop --upgrade and continue the rest of the upgrade process: make 2) on the last upgrade process we have to upgrade the db: ./bin/gmg dbupdate this fails because jsonschema.compat is not found workaround: commenting the import from the following file mediagoblin/tools/metadata.py and now the gmg dbupdate works. YMMV but that's what happend for me on buster 10.10 on 5th july 2021. (date can be important due to external nodejs dependency) - and it is only reported now as the trac seemed to have been broken for a while (on my side at least). thanks again for this new release, works quite well so far! |
|||
