The SpikerSoft login page displays English text despite the platform being set to Spanish. Key interface elements such as labels, buttons, and links remain untranslated, creating inconsistency and accessibility issues for Spanish-speaking users.
🧪 Steps to Reproduce
Navigate to ids.spikersoft.com/realms/spikersoft/protocol/openid-connect/auth.
Observe the login form.
Note that all visible text (labels, buttons, and links) are in English.
✅ Expected Behavior
All interface elements should be localized to Spanish when the platform language is set to Spanish.
Example translations:
“Sign In” → “Iniciar sesión”
“Username or email” → “Nombre de usuario o correo electrónico”
“Password” → “Contraseña”
“Remember me” → “Recordarme”
“Forgot password?” → “¿Olvidaste tu contraseña?”
❌ Actual Behavior
All login form text remains in English.
No Spanish localization is applied to the authentication interface.
The user experience feels inconsistent compared to the rest of the localized platform.
📸 Evidence
The attached screenshot shows the login page with English text under a Spanish interface context.
🧠 Possible Root Cause
Missing localization keys in the authentication module.
Static English strings not linked to the translation system.
Language context not passed correctly to the login service.
### 🧩 Summary
The **SpikerSoft login page** displays English text despite the platform being set to Spanish. Key interface elements such as labels, buttons, and links remain untranslated, creating inconsistency and accessibility issues for Spanish-speaking users.
### 🧪 Steps to Reproduce
1. Navigate to `ids.spikersoft.com/realms/spikersoft/protocol/openid-connect/auth`.
2. Observe the login form.
3. Note that all visible text (labels, buttons, and links) are in English.
### ✅ Expected Behavior
All interface elements should be localized to Spanish when the platform language is set to Spanish.
Example translations:
- “Sign In” → **“Iniciar sesión”**
- “Username or email” → **“Nombre de usuario o correo electrónico”**
- “Password” → **“Contraseña”**
- “Remember me” → **“Recordarme”**
- “Forgot password?” → **“¿Olvidaste tu contraseña?”**
### ❌ Actual Behavior
- All login form text remains in English.
- No Spanish localization is applied to the authentication interface.
- The user experience feels inconsistent compared to the rest of the localized platform.
### 📸 Evidence
The attached screenshot shows the login page with English text under a Spanish interface context.
### 🧠 Possible Root Cause
- Missing localization keys in the authentication module.
- Static English strings not linked to the translation system.
- Language context not passed correctly to the login service.
Addressed in spikersoft-backend PR #5. The custom Keycloak login theme only had messages_en.properties (and didn't declare locales), so its SpikerSoft-specific strings stayed English even under a Spanish realm. Added messages_es.properties (Sign In → Iniciar sesión, Forgot password? → ¿Olvidaste tu contraseña?, New to SpikerSoft? → ¿Nuevo en SpikerSoft?, etc.) and declared locales=en,es.
One runtime caveat: Keycloak only serves the Spanish bundle if the realm has Internationalization enabled with es in Supported locales (Realm settings → Localization). That's a server setting, not something in the repo — so the theme change + that toggle together fully localize the login/register/reset pages.
Addressed in spikersoft-backend PR #5. The custom Keycloak login theme only had `messages_en.properties` (and didn't declare `locales`), so its SpikerSoft-specific strings stayed English even under a Spanish realm. Added `messages_es.properties` (Sign In → Iniciar sesión, Forgot password? → ¿Olvidaste tu contraseña?, New to SpikerSoft? → ¿Nuevo en SpikerSoft?, etc.) and declared `locales=en,es`.
One runtime caveat: Keycloak only serves the Spanish bundle if the realm has **Internationalization enabled** with `es` in **Supported locales** (Realm settings → Localization). That's a server setting, not something in the repo — so the theme change + that toggle together fully localize the login/register/reset pages.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
🧩 Summary
The SpikerSoft login page displays English text despite the platform being set to Spanish. Key interface elements such as labels, buttons, and links remain untranslated, creating inconsistency and accessibility issues for Spanish-speaking users.
🧪 Steps to Reproduce
ids.spikersoft.com/realms/spikersoft/protocol/openid-connect/auth.✅ Expected Behavior
All interface elements should be localized to Spanish when the platform language is set to Spanish.
Example translations:
❌ Actual Behavior
📸 Evidence
The attached screenshot shows the login page with English text under a Spanish interface context.
🧠 Possible Root Cause
Addressed in spikersoft-backend PR #5. The custom Keycloak login theme only had
messages_en.properties(and didn't declarelocales), so its SpikerSoft-specific strings stayed English even under a Spanish realm. Addedmessages_es.properties(Sign In → Iniciar sesión, Forgot password? → ¿Olvidaste tu contraseña?, New to SpikerSoft? → ¿Nuevo en SpikerSoft?, etc.) and declaredlocales=en,es.One runtime caveat: Keycloak only serves the Spanish bundle if the realm has Internationalization enabled with
esin Supported locales (Realm settings → Localization). That's a server setting, not something in the repo — so the theme change + that toggle together fully localize the login/register/reset pages.