jpoesen | πŸ‡ͺπŸ‡Ί | πŸ³οΈβ€πŸŒˆ

211 Followers
91 Following
1.4K Posts

πŸ”₯ FOR HIRE: Your Personal Drupal Coach πŸ”₯

--------------------
I teach #PHP, #Drupal, #SQL, and #Linux foundations.

I talk less about Drupal over at https://social.jpoesen.com/@jpoesen

Your Personal Drupal Coachhttps://jpoesen.com/drupal-training
Pixelfedhttps://pixelfed.social/jpoesen
Drupalhttps://drupal.org/u/jpoesen
Linkedinhttps://linkedin.com/in/jpoesen

So I'm making a small #Drupal-side API to let javascript #tests interact with a Drupal site.

I want to keep this as lightweight as possible, and rely on as few dependencies as possible. No JSON:API or JWT-related modules involved at the moment.

The JS calls are adding a custom HTTP header with a "secret" token, and my API routes ensure that token is present.

But anyone who sniffs web traffic can pick up that secret token, no?

I feel like I'm missing something fundamental here. Thoughts?

There does seem to be an issue with the new "main" Drupal core branch introduced today:

It throws an UnexpectedValueException in Composer's VersionParser, called by Core's getPossibleCoreUpdateVersions()...

Hey #Drupal 8 #D8 #Composer friends, I'm having a weird composer issue:

Admin pages suddenly crash, seemingly out of the blue:

```
UnexpectedValueException: Invalid version string "main" in Composer\Semver\VersionParser->normalize()
```

It seems like Drupal is trying to see if there are core updates (>= 8.9.20), and then receives a "main" version identifier that composer can't deal with?

Possibly related to the new "main" branching scheme in D11 pushed 2 hours ago?

Ah... green tests across the board.
Nice.

Cheers to whomever we have to thank for #Drupal's incredibly useful #Twig #Debug Mode:

➑️ https://www.drupal.org/docs/develop/theming-drupal/twig-in-drupal/debugging-twig-templates

- Enables debug printing inside templates with `{{ debug(your_variable) }}`.
- Adds template naming hints to html output.
- Lets you avoid having to clear the cache after every Twig template change.

πŸ’™

Drupal.org having a seasonal meltdown?
Oh dear.

At this point, the terribly confusingly named product "Drupal CMS" should be renamed to "Drupal AiCMS" or "Drupal AI/XP" or something.

Placate marketeers, warn potential users, and further distance the infernal contraption from Drupal Core in one fell swoop.

- Why aren't we receiving any applications?
- No sΓ©.

---

"ΒΏCΓ³mo Aplicar?

Si cumples con los requisitos y te interesa formar parte de nuestro equipo, envΓ­a tu CV actualizado a [******] con el asunto "Desarrollador Drupal 10 - Remoto".

Β‘Esperamos tu candidatura!"

---