Hi! Your access is limited. Please log in or contact us at info@agentive.org to create an account.

Known bugs

From agency
Jump to navigation Jump to search

Here is a page to exchange about bugs.

Bugs in queries

+

As seen with Thing 001085 - IQ200+ on the Assembly - Curiosity page, when a query encounters a "+" sign, it breaks.
Same with a + in a people's name, it doesnt show when creating a new people using the form.

Searching for a thing

For now, the search bar doesn't allow partial word search as explained here, meaning entering only the last digits of a thing won't show anything in the results.
The six digits have to be entered to find the page.
The best would be to modify the search so that it's allowed, maybe installing another search engine see documentation here.
Or use Elasticsearch?
See Help:CirrusSearch and Help:Searching.

Double redirects

Having double redirects is not recommended, see documentation on redirects, and the list of double redirects in this wiki.

Duplicates

Library document

There's a weird thing happening with Put on your Blue Genes, it appears twice in 1.0.. I thought it was because there is 2 copies of it, with a comment for each of them, but when I modified the copy comment section on another document having multiple copies, it didn't do the same thing.

Things

Other interesting categories to look at

Not bugs but needs some change

Access

We should have different accesses based on status of visitors, see Extension:AccessControl and Manual:Preventing access

Webdesign

We need to make a custom skin for the wiki.
See:

See also:

What is a document and what is a shelf

“Document” is too generic a term, maybe “Library document” also “Thing document” for documents in the boxes, etc. The same goes for the shelves, maybe use "Library shelf".

Edit: document is now Category:Library document, and shelf is now Category:Library shelf. The category for 'thing document' hasnt been created yet.

Things

Languages

  • Create the possibility to add language in the things form. For exemple "Basque" for the Thing 002115, or "lv" (Letvian language) for Thing 000885 - Daley Bicentennial Plaza
    • checkboxes, which are used to display the different languages, don't allow to add a new language ;
    • we should then change and maybe use the same display as in the library document form, which is an arraymap (see Template:Generic) ;
    • it makes totally sense that there is only one way to refer to a language ;
    • this would mean we have to modify each thing for which the language of the presentation and/or publication text is specified.

Publication/presentation text

  • confusion about this for people who don't know how to recognise these in the boxes
  • we should add a quick description of both, or maybe make a glossary?
    • a Glossary page has been made
    • we need to collectively decide how to describe each element

Agency/Agentur/Agency Computer/...

  • Agency has been known under different names, depending on the language of the context.
  • we should be able to link all spelling
  • a redirect doesn't seem right because it then makes a mess in the table (the different spelling doesn't show, only the main page)

Fixed!

Library document form

Issue

We have a new bug on the wiki 🦂
When editing a library document with the form, the loading spinner gets stuck.
This only happens for library documents, all other forms work fine.

Possible explanations?

It seems to be linked to JavaScript?
"JavaScript Timeout Issues: Page Forms often rely on JavaScript to load interactive elements. A common bug involves the loading spinner getting stuck, which can often be resolved by debugging with browser developer tools (F12) to identify conflicting scripts."
On the common problems' page for PageForm, it's said that it could be because of an extension or the skin.
When adding " &debug=true " to the url and looking at the console, it says TypeError: str.toLowerCase is not a function. (In 'str.toLowerCase()', 'str.toLowerCase' is undefined) Maybe it's because the form uses two templates? (Template:Generic and Template:Copy)

With some help, we went in debug mode on the page and identified field 8 as the problem, which is the field for publication_date. The date is considered a string, but it's a number.

Test

Changing the skin in LocalSettings didn't do anything.

documentation?

Solution for now

Since entering years in a form works in the Form:Assembly, in the Form:Library document we changed the input type from combobox to tokens, with a max values=1.
It's now working but it's a bit ugly?
We also wrote about it in the talk page for PageForms.

Assembly pages (FIXED!!)

Issue was : we need to add a form taking along location, inviting organisation, date, participants...

No hyperlink for dates (FIXED!!)

Issue was: "There is no possibility of making a research through dates."

Solution: the category category:Year was created.

Questions (FIXED!!)

Issue was :

It seems like, when adding a question that does not exist yet in the Form:Library document or in the Form:Assembly, creating the page for the new question by clicking on the red link does not work if there is an "?" in it (which is a big problem for a question ...).

The bug is as follow:

  • the question mark doesn't appear in the name of the new page you're creating ;
  • none of the text written after the question mark appears.

For example, when clicking on the red link question What if collective things become included within art practices? (fans), the following page appears : Create page What if collective things become included within art practices
So no question mark and the (fans) disappeared.
Also, in the "document" section of the page What if collective things become included within art practices, an error appeared, saying the query used to show all the documents where this question is referenced is not called in the right way. The strange thing is it's working for other questions, so it's not the query.

FIXED!!

We modified Template:List of questions so it shows the right link, see arguments of #formredlink https://workingwithmediawiki.com/book/chapter17.html#magicparlabel-5527

* [[{{{1|}}}|{{#formredlink:target={{urlencode: {{{1|}}}|WIKI}}|form=Questions|link text={{{1|}}}}}]]

Logo (FIXED!)

https://www.mediawiki.org/wiki/Manual:$wgLogos

Renaming users (FIXED!)

Issue was:

We should be able to rename users. For this we need to install the extension Renameuser. We then need to change Eva Gonzales-Sancho to Eva Gonzalez-Sancho (with a z).

Note: since we upgraded the wiki to version 1.43, the rename user extension is actually included so we had to delete the extension in LocalSettings.php.

Maximum number of pages displayed on a category page (FIXED!!)

Pages in MediaWiki can be organized into categories. A category page displays links to the pages assigned to that category. By default, a single category page displayes links to 200 articles, so if a category contains more than 200 articles, then they will be listed in the category 200 per page. There are next and previous buttons above and below the list with which users can browse through the articles associated with the category.

If you want to, you can change the maximum number of articles displayed per category page. To do that you have to add a line to the LocalSettings.php file of your MediaWiki. For example, if you put the following at the end of the file:

$wgCategoryPagingLimit = 100;

then each category page can list no more than 100 pages. Just replace the number with whatever number you wish, then save the change. This also affects the list of the subcategories, if the category has any. Note that this option doesn't affect the number of pages that you can put in a category. It simply controls the number of pages listed per category page.

See: https://www.mediawiki.org/wiki/Manual:$wgCategoryPagingLimit

FIXED! Specimen images

clarify that we only add specimen imgage and how that looks

FIXED!! Questions (again ... see below)

Description

For some questions, the list of documents referencing to the question doesn't show.
See:

But for others it works, for example:

Error showing

The error message says 'Error: operator for the virtual field 'Generic.things' must be 'HOLDS', 'HOLDS NOT', 'HOLDS LIKE' or 'HOLDS NOT LIKE'.'

Template

The same template is used for all of them.
Those five different queries were tried and work for some of the questions, but not for others:

query results for How can commons be included within art practices ?
{{#cargo_query:

tables=Generic
|fields=_pageName
|where=questions HOLDS '{{#replace:{{PAGENAME}}|'|\'}}'
|format=ul}}

{{#cargo_query:

tables=Generic,Questions
|join on=Generic.questions HOLDS Questions._pageName
|where=Generic.questions HOLDS '{{#replace:{{PAGENAME}}|'|\'}}'
|fields=Generic._pageName
|limit=5000
|format=ul}}

{{#cargo_query:

tables=Generic,Questions
|join on=Generic.questions HOLDS Questions._pageName
|where=questions HOLDS '{{PAGENAME}}'
|fields=Generic._pageName
|format=ul}}

{{#cargo_query:

tables=Generic,Questions
|join on=Generic.questions HOLDS Questions._pageName
|where=Generic.questions HOLDS '{{#titleparts:{{#replace:{{PAGENAME}}|'|\'}}}}'
|fields=Generic._pageName
|limit=5000
|format=ul}}

{{#cargo_query:

tables=Generic=G, Generic__questions=GQ
|join on=G._ID=GQ._rowID
|fields=G._pageName
|where=GQ._value="{{PAGENAME}}"
|format=ul}}
 see [cargo list type fields]

To complete documentation, this shows a list of the documents for which a question has been mentioned.

query results
{{#cargo_query:

tables=Generic,Questions
|join on=Generic.questions HOLDS Questions._pageName
|where=Generic.questions HOLDS Questions._pageName
|fields=Generic._pageName
|limit=5000
|format=ul}}

Possible explanation

Every question that leads to a bug have the words "things", "included", "become" and "practices".
"things" is a field in the table:Generic.
If we take out "things" from the query, it works: No results

The words "become", "included" and "practices" are not bringing an error.
This is the query for only the word "things" : No results

Since table:Generic also has a field named "assemblies", we tried it, and it also breaks the query: No results

Michael sent a bug report through cargo talk page.
One way to work around this could be to add prefixes to all field names.

Solution

A fellow wikienthusiast gave us a patch, that Michael forked on the public extension, see [here].

Footer

We need to mention our supports such as VGC etc. Seems like the easiest way is to edit the footer, see Manual:Footer.

Retrieved from "https://agentive.org/mw/index.php?title=Known_bugs&oldid=9292"