Ric Le Poidevin

Founder: U&US @storyblok

Creator: Laravel Storyblok @curiosityofpod

[Ric Le Poidevin @RicLeP]

Exciting news! I am incredibly happy to announce I have founded a new branding and web design studio with two long time colleagues called U&US. We’re based in Belfast and Guernsey and bringing years of experience creating great work for good brands to you! https://t.co/JCF2ZFCqrP

[Ric Le Poidevin @RicLeP]

@footballzlin Go Zlín! My Czech team 💙

[Ric Le Poidevin @RicLeP]

Hello, what's this...?

[Ric Le Poidevin @RicLeP]

Credit where credit’s due: https://t.co/mk9mCyDNcr

[impulsive @weezerOSINT]

Lovable has a mass data breach affecting every project created before november 2025.

I made a lovable account today and was able to access another users source code, database credentials, AI chat histories, and customer data are all readable by any free account.

nvidia, microsoft, uber, and spotify employees all have accounts. the bug was reported 48 days ago. its not fixed. They marked it as duplicate and left it open.

[Ric Le Poidevin @RicLeP]

Lovable putting so much love into their own product that they use AI to write a statement addressing a serious concern (judging by the em dash), then they need a statement to address the statement. This is schoolboy level stuff. 😅

[Lovable @Lovable]

We were made aware of concerns regarding the visibility of chat messages and code on Lovable projects with public visibility settings.

To be clear: We did not suffer a data breach.

Our documentation of what “public” implies was unclear, and that’s a failure on us.

Specifically for public projects, chat messages used to be visible — this is now no longer possible.

When it comes to code of public projects: That is intentional behavior. We have experimented with different UX for how the build history is surfaced on public projects, but the core behavior has been consistent and by design.

Importantly, for enterprise customers, being able to set visibility to public for new projects has been disabled since May 25, 2025.

[Ric Le Poidevin @RicLeP]

https://t.co/qzEJyCDQxD

https://t.co/05ijpFB3w5

[Ric Le Poidevin @RicLeP]

Hi @Storyblok, PHP 8.5 support has landed in Laravel Storyblok 2.53.0! 🛬

https://t.co/3Jk0Q7PF81

#Laravel #Storyblok #HeadlessCMS #PHP

[Ric Le Poidevin @RicLeP]

Anyone else experienced ‘new’ Outlook rendering emails differently in the reading pane (right) and popped-out window (left)? It’s like the reading panes looses some CSS. Email created using the @Mailchimp builder.

[Ric Le Poidevin @RicLeP]

2.46.2 for the older branch

[Ric Le Poidevin @RicLeP]

If you’re getting an Undefined array key "Total" error in my Storyblok package update to 2.50.1. The API response changed. Investigating why but this will keep it working for you for now.

[Ric Le Poidevin @RicLeP]

And the docs are updated with the latest features: https://t.co/w8a1Dm1QwN

[Ric Le Poidevin @RicLeP]

Another day, another release! 🚀

After a chat on Discord Laravel Storyblok 2.50 allows you to override the Field classes. Simply make a Class in \App\Storyblok\Fields\Defaults\... matching the name of the field to override and it’ll be used!
#StoryblokAmbassadors @storyblok

[Ric Le Poidevin @RicLeP]

See more here: https://t.co/YG34h1Omcm

[Ric Le Poidevin @RicLeP]

Another day, another release! 🚀

After a chat on Discord Laravel Storyblok 2.50 allows you to override the Field classes. Simply make a Class in \App\Storyblok\Fields\Defaults\... matching the name of the field to override and it’ll be used!
#StoryblokAmbassadors @storyblok

[Ric Le Poidevin @RicLeP]

@storyblok https://t.co/3Qpv1RLVTw

[Ric Le Poidevin @RicLeP]

Whoops! This broke caching your config. Instead you need to load the extensions with a service provider. If you only want the default Storyblok extension then skip this step and the package will handle it for you.

[Ric Le Poidevin @RicLeP]

🚀I’ve just released Laravel Storyblok 2.48.

This release allows configuring TipTap extensions and includes a <figure> extension that replaces the default <img> tag one and includes transformations via the image service!

#StoryblokAmbassadors @storyblok

[Ric Le Poidevin @RicLeP]

Whoops! This broke caching your config. Instead you need to load the extensions with a service provider. If you only want the default Storyblok extension then skip this step and the package will handle it for you.

[Ric Le Poidevin @RicLeP]

🚀I’ve just released Laravel Storyblok 2.48.

This release allows configuring TipTap extensions and includes a <figure> extension that replaces the default <img> tag one and includes transformations via the image service!

#StoryblokAmbassadors @storyblok

[Ric Le Poidevin @RicLeP]

There are new configuration options to use all this lovely new goodness! See there changes here:

https://t.co/nECtvV3A9f

[Ric Le Poidevin @RicLeP]

The email everyone wants to receive.

I guess I’ll wait until their team remembers to test before deployment then...

It’s still less annoying than dealing with the AI powered support though, things only started progressing when I coaxed a human into helping.

[Ric Le Poidevin @RicLeP]

This is great if you want to introduce a field to lots of blocks. For example, I have a custom plugin to manage responsive padding, I can make a JSON file (or export a Block already using it), then merge that field into all the Blocks that need it.

[Ric Le Poidevin @RicLeP]

I just updated my @storyblok Laravel CLI to introduce merging component fields. The way it works is you create a JSON file of just the new/updated fields you want and run the command specifying the Block to update.

artisan ls:merge-component block_name changes.json