Page MenuHomePhabricator

Wikimini.org June 2025 bug reports
Open, Needs TriagePublic

Description

I had a quick look, and here are a few initial comments:

  1. The font size is very tiny. It was already too small before, and I was actually thinking of increasing it. Could we fix that, and maybe take the opportunity to use a font that’s more suitable for young readers? A good example would be Lexend (available on Google Fonts).

This is a styling issue, not linked to the upgrade. It could be fixed now or later, but more details are required: which font and which size?

  1. There's an error when clicking on images to enlarge them.

Fixed. See comment below, fixing Apache config is required on Wikimini during deployment.

  1. I’m unable to log in to fr.wikimaxi.org (an error message mentions a session hijacking issue).

Fixed. See comment below, was an issue only on wikimaxi.org, nothing to do on wikimini.org.

  1. There are also errors on the account creation page.

Fixed by Nicolas on 10 October 2025

Event Timeline

  1. There's an error when clicking on images to enlarge them.

Fixed. I added in Apache config a CORS header: modify /etc/apache2/my-includes/wikimini/include/wikimini-subdomain-shared-testing.conf and add in the /w/images section:

# Enable CORS on images from *.wikimaxi.org - needed for MultimediaViewer
# https://stackoverflow.com/questions/14003332/access-control-allow-origin-wildcard-subdomains-ports-and-protocols#answer-27990162
SetEnvIf Origin ^(https?://.+\.wikimaxi\.org)$ CORS_ALLOW_ORIGIN=$1
Header append Access-Control-Allow-Origin %{CORS_ALLOW_ORIGIN}e env=CORS_ALLOW_ORIGIN
Header merge Vary "Origin"

Obviously, for wikimini, don’t forget to replace wikimaxi by wikimini.

  1. I’m unable to log in to fr.wikimaxi.org (an error message mentions a session hijacking issue).

Fixed. I replaced in LocalSettings.php $wgCookieDomain = '*.wikimaxi.org'; (was *.wikimini.org)

Seb35 renamed this task from Wikimini.org June 2025 bug reports to Wikimini.org June 2025 bug reports.Oct 29 2025, 3:32 PM
Seb35 updated the task description. (Show Details)

I tested the visual editor, it works.

  1. There are also errors on the account creation page.

I’m not sure to understand: creating an account effectively did not work, but because of the same error as on login page (lost session). Now this session error is fixed, was it this precise error or is there another error?

I just created an account TestWikiValley01.

Merci beaucoup, Seb, for fixing these issues! The account creation page is also working normally now!

The few problems we’ve encountered do indeed seem to be related to styling. I’ve listed them in the attached image.

Wikimini 2025 upgrade - Styling issues (20251030).png (1×1 px, 683 KB)

I noticed a few errors in the console related to a missing cursor.

icursor-edit.cur:1 Failed to load resource: the server responded with a status of 404 (Not Found)

However, the cursor does appear correctly when hovering over the “Edit” links.

When I try to edit a page in wikitext mode, the <textarea> doesn’t appear (it’s set to “display: none;”).

As for Wikimini Stock (stock.wikimini.org) and Lab (lab.wikimini.org), they normally don’t use the Wikimini skin but the default MediaWiki skin.

Other than that, everything seems to be working perfectly!

A huge thank you for all this work!

Hello,
Issue 1b : buttons are working on your side. Which browser are you using ?

When trying to create an account

https://fr.wikimaxi.org/w/index.php?title=Sp%C3%A9cial:Cr%C3%A9er_un_compte&returnto=Sp%C3%A9cial:Connexion

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/wikimini.org/upgrade_wikivalley/1.39/includes/json/FormatJson.php on line 147

(numbers on the image)

  • Issue 1: increased a bit the font-size on the main article text (from 0.875em to 1em)
  • Issue 6: re-enabled the subtitle
  • Issue 10: added the icon for unlogged users
  • Issue 11: removed this part of the footer

@Lorangeo: may we discuss about styling issues during a call of ≈30 minutes? (in French or English) If yes, we may be available next week at 11:30 or 14:00 (CET).

Yes, of course! Next week, I could be available at 14:00 on Tuesday, Thursday or Friday. In English ou en français avec grand plaisir ! ;-)

@Lorangeo: I just saw your message, are you available tomorrow (Thursday) at 14:00 ?

@Seb35 Oui oui, je suis disponible 👍🏻