C3S Tracker: Issueshttps://redmine.c3s.cc/https://redmine.c3s.cc/favicon.ico2021-04-16T19:32:31ZC3S Tracker
Redmine collecting_society - Webfrontend #1105 (Neu): Upgrade 3rd party libshttps://redmine.c3s.cc/issues/11052021-04-16T19:32:31ZAlexander Blum
<ul>
<li>jQuery</li>
<li>Bootstrap</li>
<li>jQuery-Fileupload</li>
<li>Datatables</li>
</ul>
collecting_society - Konzept #1016 (Zurückgestellt): Replace incremented C3S IDs with UUIDs?https://redmine.c3s.cc/issues/10162020-11-06T17:16:16ZNico H
<p>Ist es clever, bei Artist, Files, Creations, Releases, etc. eine fortlaufende Nummer zu verwenden?</p>
<p>Dies könnte später ein Information leakage sein, wie viele Datensätze in der Datenbank sind.<br>
Oder falls eine Schwachstelle existiert, ließen sich so weitere IDs leicht raten. </p>
collecting_society - Webfrontend #1005 (Neu): If list view is empty, redirect to add viewhttps://redmine.c3s.cc/issues/10052020-09-24T18:13:06ZThomas Mielke
<p>instead of showing an empty list (e.g. locations) staight forward to the add viel (e.g. add location). </p>
collecting_society - Userfeedback #953 (Neu): Release: add track -- why is there a track input fi...https://redmine.c3s.cc/issues/9532019-12-28T19:37:22ZThomas Mielke
<p>... as tracks can be selected from a list.</p>
<p>function of the field needs to be obvous. (previously we named it working title -- as the title of the creation).</p>
collecting_society - Schnittstellen #951 (Neu): EchoPrint delete apihttps://redmine.c3s.cc/issues/9512019-12-19T21:42:59ZThomas Mielke
<p>we need an api to delete fingerprints from the EchoPrint server.</p>
<p>Currently the solr delete_query throws an exception, finding an illegal character 0xc8.</p>
<p>Tried to debug, but ptvsd has a bug too, preventing me to step through non-main threads. In ptvsd 5.0 the problem is solved, so I will wait for the release.</p>
collecting_society - Tests #950 (Neu): worker integration test can't delete web_userhttps://redmine.c3s.cc/issues/9502019-12-11T23:26:44ZThomas Mielke
<p>i.t.m. it is not possible to delete a web_user record rightaway. web_user ist too entangled with the tryton user, party, artist, etc. to have a record easyily deleted. the test currently generates random email addresses as a workaround for the email unique restraint.</p>
collecting_society - Konzept #945 (Neu): There exists a fixed set of contribuion roles wihtin DDE...https://redmine.c3s.cc/issues/9452019-12-01T19:11:45ZThomas Mielkecollecting_society - Webfrontend #937 (Zurückgestellt): JSON Web Tokenshttps://redmine.c3s.cc/issues/9372019-12-01T18:31:34ZAlexander Blum
<ul>
<li><a href="https://blog.logrocket.com/how-to-secure-a-rest-api-using-jwt-7efd83e71432/" class="external">JWT</a> (JSON Web Tokens)</li>
<li><a href="https://pyjwt.readthedocs.io/en/latest/" class="external">PyJWT</a> (Python implementation)</li>
<li>Found via <a href="https://www.privacyidea.org/about/features/" class="external">privacyIDEA</a>, a 2 Factor Authentication system, which is using JWT to communicate with other services using the 2FA feature of privacyIDEA.</li>
</ul>
collecting_society - Konzept #873 (Feedback): Fixed attributes of artists?https://redmine.c3s.cc/issues/8732019-03-20T10:33:11ZAlexander Blum
<ul>
<li>Should an artist be renameable or is it a new artist per definition?
<ul>
<li>References to this artist were commited by others, they should at least receive some notification or better something to actively acknowledge the renaming.</li>
</ul></li>
<li>Would it be ok, to have the group (yes/no) attribute of artists readonly after creation?
<ul>
<li>Changing this would have several consequences, which we could just circumvent by having this attribute read only.</li>
</ul></li>
</ul>
collecting_society - Datenbank #872 (Neu): Duplicate on deletionhttps://redmine.c3s.cc/issues/8722019-03-20T10:24:02ZAlexander Blum
<p>If an uncommited object is deleted before recommit, a duplicate needs to be created and all references should point to the duplicate instead.</p>
collecting_society - Webfrontend #871 (Neu): Add other track titles in add listshttps://redmine.c3s.cc/issues/8712019-03-20T10:20:33ZAlexander Blum
<p>Other track titles should be listed among the creation title (~"also known as").</p>
collecting_society - Konzept #867 (Neu): Autoclaim based on email?https://redmine.c3s.cc/issues/8672019-03-17T09:46:26ZAlexander Blum
<p>Do we want to have objects autoclaimed, if the email of an artist matches the email of the newly registered web user?</p>
<p>I suggest to not autoclaim, but to display those objects in a separate section of the claim interface.<br>
Maybe we should extend the <a href="https://redmine.c3s.cc/projects/repertoire/wiki/Workflows#Claim" class="external">workflow</a> by an "offered" state.</p>
collecting_society - Webfrontend #865 (Neu): Auto-redirect after successful uploadhttps://redmine.c3s.cc/issues/8652019-03-16T23:24:52ZThomas Mielke
<p>... also display processing stage on files overview.</p>
collecting_society - Webfrontend #864 (Vermeintlich Gelöst): bug in registration of frontend/back...https://redmine.c3s.cc/issues/8642019-03-16T23:03:39ZAlexander Blum
<p>verification of a changed email address only works after logging out, using the frontend ressource. This again seems to be an issue with missing ressouce permissions. I tried to replicate ProfileResource for verify_email without success. (Not even understanding why ProfileResource is in portal while the view is in repertoire.)</p>
<p><code>portal_1 | File "/usr/local/lib/python2.7/dist-packages/waitress/task.py", line 169, in service<br>
portal_1 | self.execute()<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/waitress/task.py", line 399, in execute<br>
portal_1 | app_iter = self.channel.server.application(env, start_response)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/router.py", line 270, in __call__<br>
portal_1 | response = self.execution_policy(environ, self)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/router.py", line 278, in default_execution_policy<br>
portal_1 | return request.invoke_exception_view(reraise=True)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/view.py", line 755, in invoke_exception_view<br>
portal_1 | reraise_(*exc_info)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/router.py", line 276, in default_execution_policy<br>
portal_1 | return router.invoke_request(request)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/router.py", line 249, in invoke_request<br>
portal_1 | response = handle_request(request)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/tweens.py", line 41, in excview_tween<br>
portal_1 | response = _error_handler(request, exc)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/tweens.py", line 16, in _error_handler<br>
portal_1 | reraise(*exc_info)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/tweens.py", line 39, in excview_tween<br>
portal_1 | response = handler(request)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/router.py", line 156, in handle_request<br>
portal_1 | view_name<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/view.py", line 642, in _call_view<br>
portal_1 | response = view_callable(context, request)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/viewderivers.py", line 301, in secured_view<br>
portal_1 | return view(context, request)<br>
portal_1 | File "/ado/src/collecting_society.portal/collecting_society_portal/models/base.py", line 197, in wrapper<br>
portal_1 | result = func(*args, **kwargs)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/viewderivers.py", line 410, in viewresult_to_response<br>
portal_1 | result = view(context, request)<br>
portal_1 | File "/usr/local/lib/python2.7/dist-packages/pyramid/viewderivers.py", line 138, in _class_view<br>
portal_1 | response = getattr(inst, attr)()<br>
portal_1 | File "/ado/src/collecting_society.portal.repertoire/collecting_society_portal_repertoire/views/backend.py", line 86, in verify_email<br>
portal_1 | web_user.save()<br>
portal_1 | File "/ado/src/trytond/trytond/model/modelstorage.py", line 1420, in save<br>
portal_1 | self.write([self], save_values)<br>
portal_1 | File "/ado/src/trytond/trytond/model/modelsql.py", line 801, in write<br>
portal_1 | where=red_sql))<br>
portal_1 | File "/ado/src/trytond/trytond/backend/postgresql/database.py", line 315, in execute<br>
portal_1 | return self.cursor.execute(sql, params)<br>
portal_1 | InternalError: cannot execute UPDATE in a read-only transaction<br>
</code></p>
collecting_society - Webfrontend #863 (Neu): Prevent multiclick on form controlshttps://redmine.c3s.cc/issues/8632019-03-16T22:05:04ZAlexander Blum
<p>If Next/Previous is clicked multiple times very fast, the form parts and controls are aggregated and displayed on one site.</p>