Burriana, Castellón
Account created on 19 January 2024, about 1 year ago
#

Merge Requests

Recent comments

daniel_mm02 Burriana, Castellón

Dear Maintainers,
I have submitted a merge request that introduces an optional $custom_prompt parameter to the generate function.
Please let me know if you have any questions or require further adjustments.
Best regards,
Dani

daniel_mm02 Burriana, Castellón

Hi everyone, I've updated the issue summary with the necessary details regarding the replacement of \Drupal:: with $this->container->get() in our test classes.

daniel_mm02 Burriana, Castellón

Hi, I have created a MR: https://git.drupalcode.org/project/json_ld_schema_ui/-/merge_requests/13 which needs revision to merge it, I have tested it and now if you mark the new chockbox in the form and separate the values with commas the result will be as follows:

With checkbox marked:
<script type="application/ld+json">{"@context":"https:\/\/schema.org\/","@type":"Organization","awards":["test1","test2","test3 test4 test5","test6"]}</script>

With checkbox unmarked:
<script type="application/ld+json">{"@context":"https:\/\/schema.org\/","@type":"Organization","awards":"test1, test2, test3 test4 test5, test6"}</script>

daniel_mm02 Burriana, Castellón

daniel_mm02 made their first commit to this issue’s fork.

daniel_mm02 Burriana, Castellón

I have tested it, and it works fine.
I get this result:

daniel_mm02 Burriana, Castellón

Hi, I've added a commit to try to fix it, I think it's correct, if not let me know and I'll take a look at it.

daniel_mm02 Burriana, Castellón

daniel_mm02 made their first commit to this issue’s fork.

daniel_mm02 Burriana, Castellón

Hi, I would like to maintain this module because I think it can be useful for my organisation in a project I'm working on right now, and if my work can help someone in the community it would be great.
I'm waiting for your answer to know if I can maintain this module and work on it to make it useful, thanks!

daniel_mm02 Burriana, Castellón

Daniel_MM02 made their first commit to this issue’s fork.

daniel_mm02 Burriana, Castellón

Daniel_MM02 made their first commit to this issue’s fork.

daniel_mm02 Burriana, Castellón

Daniel_MM02 made their first commit to this issue’s fork.

daniel_mm02 Burriana, Castellón

Tras seguir los pasos propuestos para testear en local, no se aprecia ningún problema a la hora de configurar el sitio para tener contenido en inglés, español y lenguas cooficiales.
Tras testear el último comentario se ve el cambio en el menú mencionado.

daniel_mm02 Burriana, Castellón

Tienes razón, tras insertar el comando "$settings['config_readonly'] = TRUE;" en el archivo "settings.all.php" muestra el siguiente mensaje que impide guardar nuevas configuraciones:

daniel_mm02 Burriana, Castellón

Daniel_MM02 changed the visibility of the branch 3417788-config-read-only to active.

daniel_mm02 Burriana, Castellón

Daniel_MM02 changed the visibility of the branch 3417788-config-read-only to hidden.

daniel_mm02 Burriana, Castellón

El módulo "config read_only" no está instalado en "core.extension.yml", por lo que al añadir el comando "$settings['config_readonly'] = TRUE;" no se aplica ninguna configuración ya que no está el modulo habilitado.

daniel_mm02 Burriana, Castellón

He instalado el script y se ve bien la página

daniel_mm02 Burriana, Castellón

The error was that it was not necessary to create a vocabulary for each taxonomy; instead, it was necessary to create a taxonomy for each vocabulary so that Autotagger could correctly identify it in the "Destination fields" field. I attach screenshots below where you can see the process for it to work correctly.

daniel_mm02 Burriana, Castellón

Daniel_MM02 made their first commit to this issue’s fork.

Production build 0.71.5 2024