User talk:Sophivorus

About createwiki extension

Hi. My wiki farm use extension create wiki but it The CreateWiki interface is only available on global wikis. Can you help me? thanks Doramsn (talk) 06:51, 23 December 2024 (UTC)

@Doramsn Hi! Sorry but I'm not looking for new projects. Good luck! Sophivorus (talk) 11:36, 23 December 2024 (UTC)

ProveIt - wiki date standarts

Hi! Thanks for your work on ProveIt. Can you tell me what is the "wiki's standarts" here?: translatewiki:Wikimedia:Proveit-proveit-normalize-date-tooltip/en. Nemoralis (talk) 21:14, 3 September 2025 (UTC)

@Nemoralis Hi! It means the local wiki's preferred date format. In the case of the English Wikipedia, that's discussed at en:MOS:DATEUNIFY and en:MOS:YEARS. Other wikis can configure their own preferred date format, see the 'proveit-date-format' config option at ProveIt#Installation for details. Thanks for the translations! Sophivorus (talk) 12:57, 4 September 2025 (UTC)

Firmulario: algunas cosas

Hola @Sophivorus, ¿qué tal?

Tengo algunas cosas que pedirte con respecto al módulo wikiform, cuando lo puedas leer (y hacer ;)):

1. Lo primero, que es lo más importante, es ajustar el parámetro grupos. Estoy probando varias ideas y encuentro dos problemas:

  • Primero: Los bibliotecarios en la eswiki nos excluimos de grupo cuyos permisos tenemos inherentes. No pertenecemos a los grupos de reversores, verificadores, editores de plantilla, etc., ya que contamos con estos permisos. El único grupo al que estamos asignados automáticamente es el de autoconfirmados, que se asigna por el sistema, aparte de eso solo tenemos marcadas las casillas de sysop y burócrata (normalmente el bibliotecario que asigna los permisos a un nuevo sysop, quita las demás casillas marcadas). Pero para el formulario, esto significa que si pongo por ejemplo verificadores, los sysop estamos excluidos.
  • Segundo: Poder incluir más de un grupo en el parámetro. Estoy teniendo ahora mismo un caso que quiero habilitar tanto para sysops como para adinistradores de interfaz. Una solución aquí podría ser también para el primer punto.

Luego añado aquí lo que te había dejado en tu PD en la eswiki (para que dejar constancia):

2. Incluir el parámetro "resumen" (similarmente a summary en pantallas de precarga), para resúmenes de edición.

3. Poder deshabilitar el botón de enviar (lo mismo que se puede con los demás campos).

Y nada, gracias y que vaya bien! Virum Mundi (talk) 08:35, 10 September 2025 (UTC)

@Virum Mundi ¡Hola! He leído tus pedidos y me parecen razonables, pero me voy a demorar algunos días en implementarlos, pues ahora mismo tengo que dar prioridad a otra cosa. ¡Saludos! Sophivorus (talk) 11:43, 10 September 2025 (UTC)
Gracias, Sophivorus! Y una cosa más, que no sé si es factible, pero por preguntar... ¿Se puede dirigir el output después de un punto de anclado (#), lo mismo que se hace al final de una sección? Un saludo. Virum Mundi (talk) 17:25, 10 September 2025 (UTC)
@Virum Mundi ¡Hola! Perdón por la demora, pero finalmente me senté y generalicé el parámetro "grupo" a "grupos". Fijate la documentación en es:Plantilla:Formulario y observa que el viejo parámetro "grupo" ya no funciona, por lo cual seguramente tengas que actualizar algunos de tus formularios.
También hice varias otras actualizaciones al código, que no deberían cambiar la funcionalidad, e hice varias pruebas, pero si pudieras hacer algunas pruebas tu también y avisarme de cualquier problema, lo agradecería.
En cuanto a las otras funcionalidades, seguramente las implemente en los próximos días, ahora que hice el trabajo de actualización de base. Mientras tanto, aprovecho para preguntar por qué quieres deshabilitar el botón de enviar, ya que parece ser una práctica no recomendada.
Con respecto a la funcionalidad de redirigir a un punto anclado, lo estuve pensando y me temo que no será posible, ya que los ids solo se exponen en el HTML, y encontrar el wikitexto que produce ese HTML es una tarea que bordea lo imposible, e incluso si se pudiera, complicaría el código desproporcionadamente. Sophivorus (talk) 13:48, 23 October 2025 (UTC)
Hola @Sophivorus, todo bien, me imaginaba que andarías ocupado; sí, ya me he enterado de la actualización, gracias (es que tengo las plantillas y módulos en seguimiento), has visto que además he actualizado uno de los parámetros, es que lo necesitaba y no quería molestarte más (hay algunos otros que no son tan urgentes). Me parece perfecto lo de las pruebas, las iré realizando.
  • En cuanto a lo de deshabilitar en botón enviar, sé que es una práctica desaconsejada como medio de evitar que se envíe un formulario cuando no todos sus campos están correctamente rellenados; en lugar de ello se recomienda el uso que en nuestro caso se produce con el parámetro "obligatorio". Pero no para eso lo quería, sino más bien como un elemento de diseño para procedimientos cerrados. En este caso la idea sería desactivar todos los elementos (cosa ya posible en los elementos input); de hecho hubiera sido incluso mejor un parámetro que deshabilita el formulario entero para este tipo de casos. Ahora bien, dicho esto, tampoco es tan urgente, pues ya lo he reemplazado de momento por una representación gráfica del formulario, como puedes ver en los concursos cerrados (aquí o aquí, vs. concurso abierto aquí). En todo caso siendo formulario de un solo elemento, esta consideración de práctica no recomendada no se aplicaría en este caso (pero repito, ahora mismo no es crucial).
  • Con respecto al punto de anclado, lo pregunté más que por casos como en esta propuesta de la página VEC (que veo que ya has repasado). Los formularios de respuesta en cada entrada requieren de un identificador y para "saber" donde añadir la respuesta. Me hubiera gustado que no fuera visible (como ahora en el título de la sección), y también me bridaría más flexibilidad en otros aspectos (evitando lo que conlleva el elemento de título de sección), pero claro, si no se puede pues no se puede.
Bueno, por lo demás, sabes dónde encontrarme ;) Saludos! Virum Mundi (talk) 20:55, 23 October 2025 (UTC)
@Virum Mundi ¡Hola! Como habrás notado, recién agregué el parámetro "resumen" que agrega un campo para el resumen de edición al final del formulario. También agregué un resumen de edición automático (Edited with #WikiForm) que muy pronto espero internacionalizar y que nos permite rastrear el uso desde https://hashtags.wmcloud.org. Como siempre, aunque hice mis pruebas, agradecería si tu también pudieras hacer algunas y permanecer atento por cualquier nuevo bug que pueda surgir. ¡Saludos! Sophivorus (talk) 15:58, 25 October 2025 (UTC)

How to track pageviews behind CDN with Analytics extension?

Hello! Thank you very much for your development work, but I have encountered a small problem with the use, how can I troubleshoot and solve it? My website situation is as follows:

  • Special:Analytics No charts are shown, just drop-down options and preset interface text
  • rest.php/analytics/views?frequency=daily Similar network requests display a 404 error code in the browser console
  • I do need a CDN service due to performance considerations and browsing experience optimization (I'm using Tencent Cloud's EdgeOne though, and I don't know much about the details, but I think it's probably very similar to Cloudflare CDN)
  • I've never used Google Analytics, and I probably wouldn't mind using it if I had to use it to get the extension to work (although I want to prioritize reader privacy as much as possible)

The above is my description of the situation, how can I troubleshoot and solve the problem? Thanks again for your development work, thank you! Looking forward to hearing from you. 🙏 Ztm0929 (talk) 09:51, 21 December 2025 (UTC)

@Ztm0929 Hi! Have you read Extension:Analytics#Tracking page views? As explained there, if you're behind a CDN, your server won't get the requests and so this extension can't track them. As a solution, you can enable GA4 and run the maintenance script bundled with this extension (via a daily cronjob). If you don't want to use GA4, you can try coding a new maintenance script that gets the pageviews from your CDN via their API, if they have one. But that's up to you. Lastly, regarding the empty Special:Analytics, you can start debugging by verifying that there actually is some data to show, by checking the content of the pageviews table in your database. Let me know how it goes, cheers! Sophivorus (talk) 12:49, 22 December 2025 (UTC)
@Sophivorus Thanks for the reply! I did read the instructions before asking questions about my situation. However, from your response, I clearly know that I need to enable GA4 (because I don't have the ability to modify the maintenance script to fetch data directly from the CDN yet). However, I had never heard about GA4 and it took some time for me to try it.
Thanks again for your reply and development! If I encounter unsolvable problems in the future, I will leave you a message again.♥️ Ztm0929 (talk) 02:33, 23 December 2025 (UTC)

Class for GoogleTranslate extension (for add icon)

Hello! First I'd like to thanks for for the Google Translate extension. It's very helpful as our site has many visitors from countries whose English is not their first language, and their English generally is not good.

I'd request for a small modification on this extension.

I want to add icon for google translate (by the way, it's font awesome fa-language (https://fontawesome.com/v4/icon/language)

However, due to the google translate do not have class="ca-google-translate", it cannot be formatting.

Could you add class= along side id="ca-google-translate"

<div id="ca-google-translate" class="mw-list-item"><a href="#">Translate</a></div>

Thank you.

Duyhungwiki (talk) 01:37, 17 February 2026 (UTC)

@Duyhungwiki Hi! Sorry for the delay, I've been on vacation. I'm not sure I understand you. Do you want me to add the class "ca-google-translate" alongside the ID? If so, then that shouldn't be necessary, because you can always style based on an ID rather than a class. Or do you want me to add a config option like $wgGoogleTranslateClass that you can set to "fa-language" (or whatever) to add any Font Awesome class alongside the ID? Please clarify and I'll be happy to help. Kind regards, Sophivorus (talk) 13:50, 23 February 2026 (UTC)
Well what I want is the latter "add a config option like $wgGoogleTranslateClass that you can set to "fa-language" (or whatever) to add any Font Awesome class alongside the ID".
My specific case is setting with Chameleon skin. It has setting for Font Awesome class
'cmln-icons' => '(ca-google-translate: fas fa-language)'
I did it my modify the extension code, and add 'class' => 'a.ca-google-translate' in $readAloud. The reason it has a. due to if it does not have, there will be 2 language icons show up (1 for the link itself, and 1 for the div wrap around the link)
Hope you have another cleaner way to do it.
I have another question, that how can I make the Google Translate button appear on the Side bar? On the Chameleon skin, the Side bar become the top navigation head, which is easier to access for user.
Thank you and have a good day. Duyhungwiki (talk) 12:40, 26 February 2026 (UTC)
@Duyhungwiki Hi! I just published a new version of the extension that introduces the $wgGoogleTranslateClass config option we discussed. You can use it to add "fa-language" as a class, and you can also use it to add "ca-google-translate" as a class, or both (by setting $wgGoogleTranslateClass = "ca-google-translate fa-language"; in your LocalSettings.php). Please download the latest master version (3.6) and let me know how it goes.
Regarding your second question, on how to make the Translate button appear on the sidebar, maybe it's possible using the SidebarBeforeOutput hook, but you'll need to experiment and hack yourself. Good luck! Sophivorus (talk) 15:44, 26 February 2026 (UTC)

Wording of MediaWiki:Gadget-Global-OWIDPopup.js message

Hi Sophivorus. CC @Bawolff. In MediaWiki:Gadget-Global-OWIDPopup.js, the wording of OWIDPopupConsentMessage may be too strong. Someone may read it as if OWID is activelly collecting our IP data, i.e. linking it to our Wikipedia user names. I believe this is not true, as this may only be the IP data every web server collects about its clients. Since you're in charge and know all the details, can you think of a better message, one that does not sound so scary. Maybe something along the lines "OWID will register the IP address of the computer accessing their site (but will not link it to your WP account)". When I hear back from you, I am going to ask you to add translations for Croatian: hr:Template:OWID. Thanks, ponor (talk) 21:19, 8 April 2026 (UTC)

@Ponor Hi! I was thinking something similar. The message is also not precise, because it's not only the IP that is "shared", but also the User-Agent and the preferred language (and not much else). Perhaps a more precise and less-scary message would be "The content of Our World in Data is hosted externally. Do you consent to request it?", or something along those lines. Thoughts? Sophivorus (talk) 22:43, 8 April 2026 (UTC)
A few more options to choose from or to work on:
  1. This content is hosted externally by Our World in Data. Do you want to load it?
  2. This content comes from Our World in Data, which may log your request. Proceed?
  3. This content is provided by Our World in Data. Loading it will contact their servers. Proceed?
  4. To display this content, your browser will request it from Our World in Data. Continue?
  5. This content is provided by Our World in Data. Loading it will connect to their servers and will be logged. Continue?
  6. This content is served by Our World in Data. Loading it will contact their servers and may be recorded in their access logs. Continue?
Not sure if people will be happy with removing any mentions of their requests being logged elsewhere (though the same happens when we click on any external link).
When it comes to these translations, would you be willing to introduce a window.OWIDPopupMessages variable, so interface administrators can add translations to their wiki without asking you to update the script (one day you may have tens of different languages served to all wikis, unnecessarily). You could then use something like messages = Object.assign({}, englishMessages, translatedMessages || {}, window.OWIDPopupMessages || {});. ponor (talk) 16:26, 9 April 2026 (UTC)
@Ponor Good options. Would you mind re-posting this issue and your proposals at Template talk:OWID, so that more users get a chance to comment? Regarding the translations, I fully agree. I'm thinking on eventually changing the system to something similar to MediaWiki:Gadget-Global-ProveIt.js, where only the English translations are hard-coded (per being the most frequently requested and a common fallback) and the translations are requested from Gerrit when available (see line 352). The advantage of hosting them at Gerrit is that they can be translated via translatewiki.net, which is very effective. If you want, you could open a separate topic about this issue at Template talk:OWID too. Kind regards, Sophivorus (talk) 22:10, 9 April 2026 (UTC)