🇧🇷Brazil @luco

oh, I see. thanks for the update. I'll work on a solution.

hi msn5158,

thanks for reporting this issue. I'll look into it.

hi msn5158,

are you trying to load 10.000 articles at once in your page? if not, are you employing pagers?

from what you're saying, it looks like you need to leverage some form of caching strategy on your website.

if possible, could you please test with other Views display formats and report back?

thanks

hi Clemens,

thank you so much for the contribution! unfortunately for a long time there was simply too much going on, but I'm willing to get back on track and make up for the lost time.

my humble module has been updated to Drupal 11 and so I'm closing this ticket. but please do feel free to open new issues in the future, as applicable.

best regards,
Luciano

patch #2 📌 Automated Drupal 11 compatibility fixes for tardis Needs review merged.

luco → made their first commit to this issue’s fork.

patch #2 📌 Automated Drupal 11 compatibility fixes for loremipsum Needs review merged.

closing this ticket as automated Drupal 11 patches have begun to be rolled out.

excellent, thank you!

I'm closing this ticket. in the future I'll be more mindful of the docs. 😬

best regards,
Luciano

excellent, thank you!

I'm closing this ticket, but feel free to reopen it in case of any issues.

best regards,
Luciano

hi Andrii,

done, please check on your end.

I'm striving to answer tickets more promptly, but there's been a lot going on lately, so please bear with me.

best regards,
Luciano

hi Andrii,

please test right away by removing the module and requiring it once more, in a testing environment.

best regards,
Luciano

I see... not needed, but it's for "the wider PHP community". for me that's justification enough 😅

I've added the file - should be present in the next build. thank you! please test and let me know once done.

best regards,
Luciano

excellent! thanks again for taking the time to help improve my code.

I'm closing this ticket with credit to you; in the future, if you encounter any issues, don't heasitate to reach out.

best regards,
Luciano

hi Andrii,

I've successfully reviewed and merged your changes for this ticket. would you please test on your end?

best regards,
Luciano

hello Andrii,

thank you for the generous contribution! I gotta say I'm a little embarrassed I didn't think of this one in particular before... 😅

Anyway I'll review this along with your other additions and incorporate everything.

thanks again!

best regards,
Luciano

hello Andrii,

thanks for running CodeSniffer on my code! I'll review the changes and apply them asap.

best regards,
Luciano

hello Andrii,

thank you so much for taking the time to work on my humble module! your input in invaluable for me to further my learning.

I wasn't aware that a composer.json file is needed. did the tests or anything else break without it? would you please link me with the docs outlining this requirement?

best regards,
Luciano

hi Daniel,

I have tested locally and can confirm it's working: therefore, I'm closing this ticket.

however, should you still encounter issues, please feel free to reopen this.

cheers,
Luciano

hi Daniel,

thank you so much for bringing this to my attention. I missed that detail since I was cloning the project directly from git.drupalcode.org.

it should be fixed now; please test and report back so we can confirm.

cheers,
Luciano

gulp-cli installation threw an error for version 5.0.10 → of the theme, therefore moving the item under "optional" as its installation could (or should) be skipped.

The error is:

npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm ERR! code EEXIST
npm ERR! path /home/username/.nvm/versions/node/v16.20.2/bin/gulp
npm ERR! EEXIST: file already exists
npm ERR! File exists: /home/username/.nvm/versions/node/v16.20.2/bin/gulp
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/username/.npm/_logs/2023-12-16T22_27_51_618Z-debug-0.log

Node version 16 is required for version 5.0.10 → of the theme.

browserSync proxy URL is on line 79.

Updated subtitles and corrected filename.

Updated content for Drupal 10; added tags.

luco → created an issue.

Added a mention to the loremipsum.services.yml file.

Updated content, code snippets, and summary; added tags; tests can't be run via Drupal anymore. The module Testing tools → is now seeking a co-maintainer. Offered a guide for testing with Lando instead.

Code sample cleanup.

Updated content, code snippets, and summary; added tags; swapped images for text.

Updated content, code snippets, and summary; added tags; cleared page status.

Added a note related to the other Form this module uses.

Updated Page status.

Updated Summary.

Updated text and code snippets.

Removed the tip linking to https://www.drupal.org/project/site_settings → as it is not related to this tutorial, either in scope or complexity.

Updated Summary.

Updated Summary.

Updated Summary.

Removed observations related to Drupal prior to version 8.7.7, since it's not recommended to be used anymore. Also removed comparisons to Drupal 7, as they now feel anachronistic. Stripped the last section, as it pertains to more complex modules and never offered sample code related to this situation. Before adding complexity to this tutorial, please keep in mind: this is a basic example to assist in the learning curve. For more complex scenarios, please refer to the Examples → module.

There is hardly the need to keep saying how basic this guide is. In fact, that "From .info to tests, just the basics" subtitle was there only because there wasn't a sidebar back when this guide was first written, if memory serves.

Fixed the folder structure.

The image hadn't been properly uploaded.

The module has been updated to Drupal 10, so the guide needs updating as well.

The module has been updated to Drupal 10, so the guide needs updating as well.

Hello!

Thank you so much for taking the time to test the module, finding the bug, and proposing a solution!

I see the problem is a bit more complex - on the one hand, if we resort to using Twig only, all text is escaped automatically. But on the other hand, that introduces a possibility for the template to be overridden, so there's a breach.

For the time being, I'll be adding your suggestion (and crediting you, of course). Later, though, I plan to add an option for flexibility.

Good job!