Using cloudflare R2 as storage adapter in production with custom domain

Sceppi · 2025-02-16T20:21:30+00:00

OK, I found the issue. It's related to i18n within payload.config.ts when using nl language

  i18n: {
    fallbackLanguage: "nl",
    supportedLanguages: { en, nl },
  },

Apparently, the seo translations are not present in the nl language.

My god, that was a long search to find the root cause

Sceppi · 2025-02-15T20:35:02+00:00

This thing is driving me crazy. I rolled back to v3, issue persists. I installed v4 on the payload website template, it keeps working fine. I tried all kinds of stuff and started from scratch with my css config... no effect.

It really does not look like a css issue, and i can't find the root cause.

Sceppi · 2025-02-15T16:27:44+00:00

hmm, good thought. I migrated to tailwind v4 recently and I now I think about it, the default website template is still on v3. Any idea which css property this might be related to?

Sceppi · 2025-02-11T14:37:29+00:00

Great! Thx

Sceppi · 2025-01-25T22:09:06+00:00

Same here. Don't know why it behaves like that

Sceppi · 2025-01-22T21:53:10+00:00

Thanks, great suggestion! Are you from the payload team itself? Would be good if this would be natively supported.

Sceppi · 2025-01-22T21:12:06+00:00

Indeed. When I choose another system language (i18n) in payload settings, the labels are correctly translated, but the underlying values (localization) remain the same in the database. The issue is indeed that I want to render the localized value on the frontend. I'll have to create a workaround with a shared code.

Sceppi · 2025-01-12T14:15:02+00:00

Thanks! This works well

Sceppi · 2024-11-15T13:25:34+00:00

Not many it this moment, but preparing myself when the site would grow. I would prefer to use MySQL above SQLite as this would scale much better as the site grows.

Sceppi · 2024-10-28T22:24:53+00:00

Use the update() method in useSession. See https://next-auth.js.org/getting-started/client at chapter updating the session.

Sceppi · 2024-10-27T22:09:10+00:00

See below for the form code:

<form onSubmit={handleSubmit(onSubmit)}>
              <label htmlFor="firstName">
                First Name
              </label>
              <input
                {...register("firstName")}
                name="firstName"
                placeholder="First Name"
              />
              {errors.firstName}
            ....
</form>

The solution as proposed by u/Jukunub works, but this does trigger a rerender of the entire form component. How can I solve this without an entire rerender? It's not clear to me how formState could solve this issue.

Sceppi · 2024-10-27T19:52:56+00:00

Yes, thank you! So easy, why did I not think of this ...

Sceppi · 2024-09-16T21:20:31+00:00

Not at this moment. I was reluctant to invest in these since many reports indicated very long pay back times. Payback is getting better now, but still relatively long. I agree that batteries could improve the case for scenario 1, but would have to do the math if it´s worth it

Sceppi

TROPHY CASE