IT Tickets issueshttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues2024-02-08T22:45:44+01:00https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/98Update Nextcloud2024-02-08T22:45:44+01:00Andre LehmannUpdate NextcloudAndre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/97Wikibase CirrusSearch/ElasticSearch2021-09-15T18:47:11+02:00Martin HäuerWikibase CirrusSearch/ElasticSearchI received the following per eMail:
---
Adam H. and I talked on Monday and checked out the backend on the OSE-Germany instance - There seems to be data available but as far as we saw there were some issues with CirrusSearch/ElasticSear...I received the following per eMail:
---
Adam H. and I talked on Monday and checked out the backend on the OSE-Germany instance - There seems to be data available but as far as we saw there were some issues with CirrusSearch/ElasticSearch - could you check?
**Given this query:**\
`https://losh.ose-germany.de/w/api.php?action=query&list=search&srsearch=*&format=json&srnamespace=120&srlimit=10&sroffset=0&origin=*`
**We receive a generic error:**\
`{"error":{"code":"cirrussearch-backend-error","info":"We could not complete your search due to a temporary problem. Please try again later.","*":"See https://losh.ose-germany.de/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."}}`
---
I remember a discussion about elastic search back in the day when we set up the Wikibase instance, but can't right remember whether or not we decided to install elastic search.\
Our setup document [1] doesn't say much about it.
@aisberg any ideas? I also pinged Tobias & Lucas from WMDE, maybe they can help to delimit the error
---
[1] https://md.opensourceecology.de/y0vfkyLPSFGGK_sezQTCBA#There-is-an-Elasticsearch-DB-in-the-setup-Is-this-part-of-the-query-servicehttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/96Install Wikibase Reconcile API2021-08-24T09:56:03+02:00Martin HäuerInstall Wikibase Reconcile API### Problem to solve
The crawler for LOSH relies on a new, enhanced Wikibase API. It won't work with the original one. Hence, as part of the job from TU Berlin, we'll need to host the API in order to make our system work.
### Intended ...### Problem to solve
The crawler for LOSH relies on a new, enhanced Wikibase API. It won't work with the original one. Hence, as part of the job from TU Berlin, we'll need to host the API in order to make our system work.
### Intended users
Crawler connects via this API to Wikibase and uploads its data. Of course, this can be done by any entitled entity then, not only the crawler, but for now, the crawler will be the only entity using this API.
### Documentation
https://github.com/wmde/WikibaseReconcileEdit#wikibasereconcileeditAndre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/95Wiki-Profile mit frei beschreibbaren Fähigkeiten2021-07-15T10:29:13+02:00Andreas PlankWiki-Profile mit frei beschreibbaren Fähigkeitenhttps://wiki.opensourceecology.de/Vorlage:Profil_Info um frei beschreibbaren Fähigkeiten erweitern, die dennoch kategorisierbar sind in Stufen 1,…,5 und auch semantisch suchbar sein sollten.
~"platform/wiki"
~"kind/enhancement"https://wiki.opensourceecology.de/Vorlage:Profil_Info um frei beschreibbaren Fähigkeiten erweitern, die dennoch kategorisierbar sind in Stufen 1,…,5 und auch semantisch suchbar sein sollten.
~"platform/wiki"
~"kind/enhancement"Andreas PlankAndreas Plankhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/94Sprache der Willkommensseite möglichst in Muttersprache (Deutsch, English, Fr...2021-07-12T23:21:54+02:00Andreas PlankSprache der Willkommensseite möglichst in Muttersprache (Deutsch, English, Français, …)Bedenkt bitte die Seitentitel und URL, fände es gut, wenn wir die (möglichst) in Muttersprache halten können:
Englisch:
- URL welcome, title: Welcome
Deutsch:
- URL willkommen, Titel: Willkommen
Danke ;-)
---
**EDIT**
- Es geht um...Bedenkt bitte die Seitentitel und URL, fände es gut, wenn wir die (möglichst) in Muttersprache halten können:
Englisch:
- URL welcome, title: Welcome
Deutsch:
- URL willkommen, Titel: Willkommen
Danke ;-)
---
**EDIT**
- Es geht um https://gitlab.opensourceecology.de/verein/welcome
- Titel und URL sollen umbenannt werden in 'Willkommen'Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/93Cannot add group 'Vorstand' to IT Documnetation2021-05-24T15:15:08+02:00Andre LehmannCannot add group 'Vorstand' to IT Documnetation<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating ...<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Summary
<!-- Summarize the bug encountered concisely. -->
Gitlab returns 404 when adding group `Vorstand` to IT Documentation. Adding other groups seems to be fine.
### Current Behavior
<!--- Describe what actually happens. -->
### Expected Behavior
<!-- Describe what you should see instead. -->
### Steps to Reproduce
<!--- Describe how one can reproduce the issue. -->
1. Step 1
2. Step 2
3. Step 3
### Context/Logs
<!--- Provide context that might help us to come up with a solution. If you have
relevant logs use Markdown code blocks (```) to format them. -->
### Your Environment
<!--- Include as many relevant details about the environment you experienced the
bug in -->
- Version used:
- Browser Name and version:
- Operating System and version (desktop or mobile):
### Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug -->https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/92Externe Services wie GitLab.com als Authentifizierung ermöglichen2021-05-20T20:42:06+02:00Timm Willetimm.wille@ose-germany.deExterne Services wie GitLab.com als Authentifizierung ermöglichenhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/88Rename OHO → LOSH2021-08-31T16:02:13+02:00Martin HäuerRename OHO → LOSHIn some places of the LOSH cosmos we still have (faulty) references to OHO. Those should be changed/renamed to avoid confusion.
- [x] File/Dir Structure
- [x] Instances in Configuration files
- [x] HTML title of https://losh.ose-germany...In some places of the LOSH cosmos we still have (faulty) references to OHO. Those should be changed/renamed to avoid confusion.
- [x] File/Dir Structure
- [x] Instances in Configuration files
- [x] HTML title of https://losh.ose-germany.de/ (also has the OHO Logo)
- → rename to LOSH; we don't have a logo currently
- [x] Database instances
- [x] Mail address(es)https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/87Replace Favicon of the Blog2021-03-29T16:14:42+02:00Andre LehmannReplace Favicon of the Blog<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, ...<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
The current favicon used for the OSEG Blog (blog.opensourceecology.de) is an older one, which doesn't comply with the current [Favicons line-up](https://gitlab.opensourceecology.de/verein/server/favicons). We should consider to replace it with the new green version in PNG format. The PNG files are smaller and might provide a better resolution for high dpi devices.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- any
### Proposal
<!-- How are we going to solve the problem? -->
The relevant contents of the [green favicon directory](https://gitlab.opensourceecology.de/verein/server/favicons/-/tree/master/generated-favicons/green) can be included in the OSEG Wordpress theme (`/wp-content/themes/underscores_oseg/favicon`). The paths in the file `site.webmanifest` need to be adapted to the theme path, then the only thing left to do is to include the following HTML code in the header:
```html
<link rel="apple-touch-icon" sizes="180x180" href="/wp-content/themes/underscores_oseg/favicon/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/wp-content/themes/underscores_oseg/favicon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/wp-content/themes/underscores_oseg/favicon/favicon-16x16.png">
<link rel="manifest" href="/wp-content/themes/underscores_oseg/favicon/site.webmanifest">
<meta name="msapplication-TileColor" content="#75b62f">
<meta name="theme-color" content="#75b62f">
```
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->Bastian Menningenbastian.menningen@ose-germany.deBastian Menningenbastian.menningen@ose-germany.dehttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/86Static web hosting for user generated content2021-03-29T10:11:47+02:00Andre LehmannStatic web hosting for user generated content<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, ...<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
We want to offer simple static web hosting for pages DIN-SPEC and other projects. For now the access can be a simple SFTP account.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- some members of the association
### Proposal
<!-- How are we going to solve the problem? -->
Provide a Nginx webserver, a domain pages.opensourceecology.de and a SFTP access.
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
### Other links/references
<!-- E.g. related issues/MRs -->https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/84Hosting Frontend LOSH (wikibase)2021-09-29T18:14:13+02:00Martin HäuerHosting Frontend LOSH (wikibase)Wikibase bietet (entgegen der Erwartungen der TUB) leider keine sinnvolle Möglichkeiten zur Datenvisualisierung. Insofern muss noch ein Frontend entwickelt und gehostet werden. Entwicklung wird keinesfalls bei OSEG landen (wahrscheinlich...Wikibase bietet (entgegen der Erwartungen der TUB) leider keine sinnvolle Möglichkeiten zur Datenvisualisierung. Insofern muss noch ein Frontend entwickelt und gehostet werden. Entwicklung wird keinesfalls bei OSEG landen (wahrscheinlich bei WMDE). Hosting kann bei OSEG landen, wenn wir das wollen.
Das Frontend wird einigermaßen simpel sein – ähnlich der [OKH-Seite](search.openknowhow.com), aber mit Projektseiten zur Anzeige der Metadaten, Filterfunktionen und ein paar Knöpfen mehr ('I built this', 'file an issue', 'report faulty data' etc.); konkret ist der Funktionsumfang noch nicht.
Pro Hosting:
- Front- & Backend aus einer Hand (Wikibase läuft ja schon bei uns)
- passt super ins Portfolio (neben dem Conformity Assessment Body)
- Suchmaschine/Register lockt ggf. Leute zu OSEG oder dient als Referenz
Con Hosting:
- zusätzliche Plattform mit allen damit verbundenen Aufwänden & Risiken
- zusätzliche Lieferfrist: Frontend müsste bis Anfang August eingebunden sein (Entwicklung durch anderen Partner steht noch aus und hat noch nicht begonnen)
- (mehr fällt mir gerade nicht ein)
---
1. Wie sieht das Meinungsbild bei Euch in der IT dazu aus? (@aisberg @alexander @bmen)
2. Was wären die Voraussetzungen/Anforderungen von unserer Seite, damit ein Hosting denkbar wäre?
3. Sonstige Wünsche?
Das Hosting könnte in den Vertrag aufgenommen werden oder unter der Hand laufen. Letzteres ist natürlich für OSEG einfacher, weil unverbindlicher. Weiß allerdings noch nicht, ob ich das durchgesetzt bekäme. Zwar bezogen sich alle Verhandlungen bisher ausschließlich auf Wikibase, aber damals war auch noch nicht klar, dass Wikibase keine Datenvisualisierung bietet. Das hat uns WMDE erst im Januar auf Nachfrage erzählt.
---
Edit: Repo des Frontends: https://github.com/wmde/LOSH-Frontend/https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/83Domainwechsel Wikibase2021-09-01T12:20:20+02:00Martin HäuerDomainwechsel WikibaseMit der Ausgliederung von OHO (#56 #57) geht uns auch die Subdomain `wikibase.oho.wiki` verloren.
Das Projekt um Wikibase (LOSH) wird künftig 2 (Sub)Domains benötigen:
- backend (Wikibase) → vorgeschlagene Subdomain: `wikibase.ose-germ...Mit der Ausgliederung von OHO (#56 #57) geht uns auch die Subdomain `wikibase.oho.wiki` verloren.
Das Projekt um Wikibase (LOSH) wird künftig 2 (Sub)Domains benötigen:
- backend (Wikibase) → vorgeschlagene Subdomain: `wikibase.ose-germany.de`
- frontend (voraussichtl. v. WMDE entwickelt, vermutlich Mediawiki-basiert)
Da die Wikibase-Instanz für das Projekt erreichbar bleiben sollte, wäre es gut, wenn wir die Subdomain vor der OHO-Domainübergabe umschalten.
Sofern wir das Frontend hosten möchten (#84), würde ich `losh.ose-germany.de` dafür reservieren wollen.Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/82MediaWiki SMW ask query results in fatal error page2021-04-05T15:53:56+02:00Andreas PlankMediaWiki SMW ask query results in fatal error page<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating ...<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Summary
Semantic MediaWiki (SMW) `#ask` query results in an (fatal) error page.
### Current Behaviour
Clicking an Special:Ask query link brings up an error message
### Expected Behaviour
Execute the SMW `#ask` query and display the results according to the query form.
### Steps to Reproduce
<!--- Describe how one can reproduce the issue. -->
1. run https://wiki.opensourceecology.de/Spezial:Abfrage_ausf%C3%BChren/Stichwort_nachschlagen?Stichwort_nachschlagen%5BStichwort%5D=Energy&_run=true
2. result may be something like
[c92e76807d30301a515456f3] 2021-03-07 10:30:44: Fataler Ausnahmefehler des Typs „RuntimeException“
### Context/Logs
Activating debug and logging shows:
```
[01dc59e81ceaa1ef5bae0223] /Spezial:Abfrage_ausf%C3%BChren/Stichwort_nachschlagen?Stichwort_nachschlagen%5BStichwort%5D=Energy&_run=true RuntimeException from line 291 of /container/www/extensions/SemanticMediaWiki/src/MediaWiki/Connection/Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?
Query: SELECT COUNT(DISTINCT t0.smw_id) AS count FROM `mw_smw_object_ids` AS t0 INNER JOIN `mw_smw_ft_search` AS t1 ON t0.smw_id=t1.s_id WHERE (((MATCH(t1.o_text) AGAINST ('*energy*' IN BOOLEAN MODE) AND t1.p_id=1891) OR (t1.o_hash='energy') OR (MATCH(t1.o_text) AGAINST ('energy*' IN BOOLEAN MODE) AND t1.p_id=1891) OR (MATCH(t1.o_text) AGAINST ('*energy' IN BOOLEAN MODE) AND t1.p_id=1891))) AND t0.smw_iw!=':smw' AND t0.smw_iw!=':smw-delete' AND t0.smw_iw!=':smw-redi' LIMIT 10001
Function: SMW\SQLStore\QueryEngine\QueryEngine::getCountQueryResult
Error: 1054 Unknown column 't1.o_hash' in 'where clause' (mariadb)
#0 /container/www/includes/libs/rdbms/database/Database.php(1427): Wikimedia\Rdbms\Database->makeQueryException('Unknown column ...', 1054, 'SELECT COUNT(D...', 'SMW\\SQLStore\\Qu...')
#1 /container/www/includes/libs/rdbms/database/Database.php(1200): Wikimedia\Rdbms\Database->reportQueryError('Unknown column ...', 1054, 'SELECT COUNT(D...', 'SMW\\SQLStore\\Qu...', false)
#2 /container/www/includes/libs/rdbms/database/Database.php(1653): Wikimedia\Rdbms\Database->query('SELECT COUNT(D...', 'SMW\\SQLStore\\Qu...')
#3 [internal function]: Wikimedia\Rdbms\Database->select('`mw_smw_object_...', 'COUNT(DISTINCT ...', '(((MATCH(t1.o_t...', 'SMW\\SQLStore\\Qu...', Array, Array)
#4 /container/www/includes/libs/rdbms/database/DBConnRef.php(49): call_user_func_array(Array, Array)
#5 /container/www/includes/libs/rdbms/database/DBConnRef.php(254): Wikimedia\Rdbms\DBConnRef->__call('select', Array)
#6 /container/www/extensions/SemanticMediaWiki/src/MediaWiki/Connection/Database.php(283): Wikimedia\Rdbms\DBConnRef->select('`mw_smw_object_...', 'COUNT(DISTINCT ...', '(((MATCH(t1.o_t...', 'SMW\\SQLStore\\Qu...', Array, Array)
#7 /container/www/extensions/SemanticMediaWiki/src/SQLStore/QueryEngine/QueryEngine.php(345): SMW\MediaWiki\Connection\Database->select('`mw_smw_object_...', 'COUNT(DISTINCT ...', '(((MATCH(t1.o_t...', 'SMW\\SQLStore\\Qu...', Array)
#8 /container/www/extensions/SemanticMediaWiki/src/SQLStore/QueryEngine/QueryEngine.php(221): SMW\SQLStore\QueryEngine\QueryEngine->getCountQueryResult(Object(SMWQuery), 0)
#9 /container/www/extensions/SemanticMediaWiki/src/SQLStore/SQLStore.php(374): SMW\SQLStore\QueryEngine\QueryEngine->getQueryResult(Object(SMWQuery))
#10 /container/www/extensions/SemanticMediaWiki/src/SQLStore/SQLStore.php(362): SMW\SQLStore\SQLStore->fetchQueryResult(Object(SMWQuery))
#11 /container/www/extensions/SemanticMediaWiki/includes/query/SMW_QueryProcessor.php(338): SMW\SQLStore\SQLStore->getQueryResult(Object(SMWQuery))
#12 /container/www/extensions/SemanticMediaWiki/src/ParserFunctions/AskParserFunction.php(361): SMWQueryProcessor::getResultFromQuery(Object(SMWQuery), Array, 2, 1001)
#13 /container/www/extensions/SemanticMediaWiki/src/ParserFunctions/AskParserFunction.php(196): SMW\ParserFunctions\AskParserFunction->doFetchResultsFromFunctionParameters(Array, Array)
#14 /container/www/extensions/SemanticMediaWiki/src/ParserFunctionFactory.php(402): SMW\ParserFunctions\AskParserFunction->parse(Array)
#15 /container/www/includes/parser/Parser.php(3426): SMW\ParserFunctionFactory->SMW\{closure}(Object(Parser), '[[Stichwort in ...', 'mainlabel=Seite', '?Suchstichwort=...', 'limit=1000', 'format=count', 'outro= Erge...')
#16 /container/www/includes/parser/Parser.php(3127): Parser->callParserFunction(Object(PPTemplateFrame_DOM), 'ask', Array)
#17 /container/www/includes/parser/Preprocessor_DOM.php(1277): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
#18 /container/www/includes/parser/Parser.php(3305): PPFrame_DOM->expand(Object(DOMElement))
#19 /container/www/includes/parser/Preprocessor_DOM.php(1277): Parser->braceSubstitution(Array, Object(PPFrame_DOM))
#20 /container/www/includes/parser/Parser.php(2942): PPFrame_DOM->expand(Object(DOMElement), 0)
#21 /container/www/includes/parser/Parser.php(1293): Parser->replaceVariables('{{Stichwort nac...')
#22 /container/www/includes/parser/Parser.php(443): Parser->internalParse('{{Stichwort nac...')
#23 /container/www/extensions/PageForms/specials/PF_RunQuery.php(98): Parser->parse('{{Stichwort nac...', Object(Title), Object(ParserOptions), true, false)
#24 /container/www/extensions/PageForms/specials/PF_RunQuery.php(26): PFRunQuery->printPage('Stichwort nachs...', false)
#25 /container/www/includes/specialpage/SpecialPage.php(522): PFRunQuery->execute('Stichwort_nachs...')
#26 /container/www/includes/specialpage/SpecialPageFactory.php(568): SpecialPage->run('Stichwort_nachs...')
#27 /container/www/includes/MediaWiki.php(288): SpecialPageFactory::executePath(Object(Title), Object(RequestContext))
#28 /container/www/includes/MediaWiki.php(861): MediaWiki->performRequest()
#29 /container/www/includes/MediaWiki.php(524): MediaWiki->main()
#30 /container/www/index.php(42): MediaWiki->run()
#31 {main}
Backtrace:
#0 /container/www/extensions/SemanticMediaWiki/src/SQLStore/QueryEngine/QueryEngine.php(345): SMW\MediaWiki\Connection\Database->select(string, string, string, string, array)
#1 /container/www/extensions/SemanticMediaWiki/src/SQLStore/QueryEngine/QueryEngine.php(221): SMW\SQLStore\QueryEngine\QueryEngine->getCountQueryResult(SMWQuery, integer)
#2 /container/www/extensions/SemanticMediaWiki/src/SQLStore/SQLStore.php(374): SMW\SQLStore\QueryEngine\QueryEngine->getQueryResult(SMWQuery)
#3 /container/www/extensions/SemanticMediaWiki/src/SQLStore/SQLStore.php(362): SMW\SQLStore\SQLStore->fetchQueryResult(SMWQuery)
#4 /container/www/extensions/SemanticMediaWiki/includes/query/SMW_QueryProcessor.php(338): SMW\SQLStore\SQLStore->getQueryResult(SMWQuery)
#5 /container/www/extensions/SemanticMediaWiki/src/ParserFunctions/AskParserFunction.php(361): SMWQueryProcessor::getResultFromQuery(SMWQuery, array, integer, integer)
#6 /container/www/extensions/SemanticMediaWiki/src/ParserFunctions/AskParserFunction.php(196): SMW\ParserFunctions\AskParserFunction->doFetchResultsFromFunctionParameters(array, array)
#7 /container/www/extensions/SemanticMediaWiki/src/ParserFunctionFactory.php(402): SMW\ParserFunctions\AskParserFunction->parse(array)
#8 /container/www/includes/parser/Parser.php(3426): SMW\ParserFunctionFactory->SMW\{closure}(Parser, string, string, string, string, string, string)
#9 /container/www/includes/parser/Parser.php(3127): Parser->callParserFunction(PPTemplateFrame_DOM, string, array)
#10 /container/www/includes/parser/Preprocessor_DOM.php(1277): Parser->braceSubstitution(array, PPTemplateFrame_DOM)
#11 /container/www/includes/parser/Parser.php(3305): PPFrame_DOM->expand(DOMElement)
#12 /container/www/includes/parser/Preprocessor_DOM.php(1277): Parser->braceSubstitution(array, PPFrame_DOM)
#13 /container/www/includes/parser/Parser.php(2942): PPFrame_DOM->expand(DOMElement, integer)
#14 /container/www/includes/parser/Parser.php(1293): Parser->replaceVariables(string)
#15 /container/www/includes/parser/Parser.php(443): Parser->internalParse(string)
#16 /container/www/extensions/PageForms/specials/PF_RunQuery.php(98): Parser->parse(string, Title, ParserOptions, boolean, boolean)
#17 /container/www/extensions/PageForms/specials/PF_RunQuery.php(26): PFRunQuery->printPage(string, boolean)
#18 /container/www/includes/specialpage/SpecialPage.php(522): PFRunQuery->execute(string)
#19 /container/www/includes/specialpage/SpecialPageFactory.php(568): SpecialPage->run(string)
#20 /container/www/includes/MediaWiki.php(288): SpecialPageFactory::executePath(Title, RequestContext)
#21 /container/www/includes/MediaWiki.php(861): MediaWiki->performRequest()
#22 /container/www/includes/MediaWiki.php(524): MediaWiki->main()
#23 /container/www/index.php(42): MediaWiki->run()
#24 {main}
```
### Environment
Version used:
| Software | Version |
|------------|-------------------|
| MediaWiki | 1.31.1 |
| PHP | 7.3.21 (fpm-fcgi) |
| MariaDB | 10.5.4-MariaDB |
| Extension | Version |
|---------------------------|--------------------------------------|
| Semantic Internal Objects | 0.8.2 (7b94fec) 21:50, 26. Jul. 2017 |
| Semantic Compound Queries | 2.1.0 (75e8b38) |
| Semantic MediaWiki | 3.1.5 (1a5a657) |
| Semantic Result Formats | 3.1.0 (aa0649f) |
- Browser Name and version: Firefox 78.7.0esr (64-Bit)
- Operating System and version (desktop or mobile): Linux
### Possible Solution
Suggested maintenance update from the debug report (_«Did you forget to run your application's database schema updater after upgrading?»_) did not resolve the error yet:
```bash
php maintenance/update.php --quick --conf ./LocalSettings.php
```https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/81Add a security.txt to all websites2021-03-16T16:07:09+01:00Andre LehmannAdd a security.txt to all websites[security.txt](https://securitytxt.org) is used to defined a security policies and enables people from the outside to contact us, in case they find critical security flaws in our infrastructure.[security.txt](https://securitytxt.org) is used to defined a security policies and enables people from the outside to contact us, in case they find critical security flaws in our infrastructure.https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/80Vorstand in Repo "Satzung" Maintainer machen und Mitglieder als Guest Gruppe ...2021-03-12T09:16:04+01:00Timm Willetimm.wille@ose-germany.deVorstand in Repo "Satzung" Maintainer machen und Mitglieder als Guest Gruppe hinzufügenWir müssen da mit dem @verein/vorstand noch einiges vorbereiten zur Versammlung und ggf. noch Hilfe von Mitgliedern einbeziehen, daher ist pingen nur sinvoll.
Scheinbar war das versehentlich noch falsch herum, Verwaltung sollte nur Dev...Wir müssen da mit dem @verein/vorstand noch einiges vorbereiten zur Versammlung und ggf. noch Hilfe von Mitgliedern einbeziehen, daher ist pingen nur sinvoll.
Scheinbar war das versehentlich noch falsch herum, Verwaltung sollte nur Dev sein und Vorstand Maintainer → habs in falscher Reihenfolge angepasst :DAndre LehmannAndre Lehmann2021-03-14https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/79E-Mail Vorlagen erstellen2021-03-06T20:18:13+01:00Andre LehmannE-Mail Vorlagen erstellen1. E-Mail Vorlagen (+ kurzer aussagekräftiger Betreff) in Deutsch und Englisch für:
- Einladung einen Account zu erstellen
- Auf welche Vereins-Plattformen die Personen dann Zugriff erhalten und welche Möglichkeiten ihnen dan...1. E-Mail Vorlagen (+ kurzer aussagekräftiger Betreff) in Deutsch und Englisch für:
- Einladung einen Account zu erstellen
- Auf welche Vereins-Plattformen die Personen dann Zugriff erhalten und welche Möglichkeiten ihnen dann offen stehen
- Ein Survey ist auszufüllen https://cloud.opensourceecology.de/apps/forms/xiEwEFzwkXdHBqXz
- Kurze Infos weshalb wir die Infos aus dem Survey benötigen: Einrichtung Account, Einordnung wer die Person
- Willkommen - Informationen zum Durchstarten
- Die nächsten Schritte, nachdem sie einen Account erhalten haben (Email verifizieren mit Link, den sie bekommen haben, einmal anmelden und Passwort ändern)
- Was können sie nun alles machen
- Wo finden sie weitere Informationen und Ansprechpartner
- Abschied bei Löschen des Accounts
2. Wo können diese abgelegt werden, sodass diese einfach abgerufen und angepasst werden können?
3. Welches Format sollen diese haben, also sollen die Nachrichten nur per Mail verschickt werden?
4. Soll eine Art Automatisierung für das Versenden der Mails eingerichtet werden?https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/77Import of repositories from Gitlab.com and Github.com2021-02-28T20:33:56+01:00Andre LehmannImport of repositories from Gitlab.com and Github.com<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating ...<!---
PLEASE READ THIS!
This is the template for describing a BUG (problem; unexpected behavior). If
your intention is to file a feature request or something else, please use the
appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Summary
<!-- Summarize the bug encountered concisely. -->
This Gitlab throws an error, when an import of a Gitlab.com repository is attempted (see https://gitlab.opensourceecology.de/verein/projekte/wh100/wirkunghoch100_osh_oer_module/-/issues/9).
### Context/Logs
<!--- Provide context that might help us to come up with a solution. If you have
relevant logs use Markdown code blocks (```) to format them. -->
![](https://gitlab.opensourceecology.de/verein/projekte/wh100/wirkunghoch100_osh_oer_module/uploads/a5dc2320cda3ed0416a1b82c348da7ac/image.png)
### Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug -->Maintenance Cycle 2021-02Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/76Wechseln von Branches via Gui2021-02-24T12:50:58+01:00Timm Willetimm.wille@ose-germany.deWechseln von Branches via Guihttps://gitlab.opensourceecology.de/verein/vorstand/finanzen/finanzenhttps://gitlab.opensourceecology.de/verein/vorstand/finanzen/finanzenMaintenance Cycle 2021-02https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/75Add filter Option to GitLab Mails2021-02-15T19:36:56+01:00Timm Willetimm.wille@ose-germany.deAdd filter Option to GitLab Mails<!---
PLEASE READ THIS!
This is the template for proposing an ENHANCEMENT (change to existing
functionality). If your intention is to report a bug or something else, please
use the appropriate template for that instead.
Before creatin...<!---
PLEASE READ THIS!
This is the template for proposing an ENHANCEMENT (change to existing
functionality). If your intention is to report a bug or something else, please
use the appropriate template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
Mails von gitlab.opensourceecology.de überschwemmen das Postfach (manche sind aber notwendig), sie lassen sich nicht sinnvoll filtern. noreply@opensourceecology.de ist an vielen Stellen verwendet und kann daher nicht als Filter genommen werden.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
Jeder mit Gitlab notifications
### Proposal
<!-- How are we going to solve the problem? -->
ein einfaches [GitLab] als Prefix würde schon helfen vor diesen Mails (zwischen Issues und anderen Events auf GitLab müssen wir nicht unterscheiden und zu den GitLab.com Issues lässt es sich leicht durch die Domain trennen).
Kann alternative auch gelöst werden indem eine gitlab@opensourceecology.de Adresse die noreply Adresse ersetzt.
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us
understand the problem better. -->
### Documentation
<!-- Add all known Documentation Requirements in this section -->
![image](/uploads/b181478a83f805b12b402af23e7e07c6/image.png)
### Other links/references
<!-- E.g. related issues/MRs -->
#28Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/74Wie genau sind die Labels zu verwenden?2021-02-15T15:19:53+01:00Timm Willetimm.wille@ose-germany.deWie genau sind die Labels zu verwenden?https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/blob/master/MAINTENANCE.md
Soll das beim Anlegen direkt zugewiesen werde oder ist das nur relevant für die Maintainer/Admins selbst?https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/blob/master/MAINTENANCE.md
Soll das beim Anlegen direkt zugewiesen werde oder ist das nur relevant für die Maintainer/Admins selbst?