Esther E.

Yup, already fixed for the next release. 😉 I really just needed to make sure I had the same setup as you.

☕️☕️☕️

Probably just the way that the form is built. But we've never supported translations in there.

I'm pretty sure this is working as intended. The options in custom fields are meant to be displayed as is. The software does not expect to parse these values.

Changed Status to Not a bug

No worries, glad it's resolved.

😭😭

What is your setting for site guidelines? Check the ACP under System -> Terms & Privacy Policy. If "Site Guidelines" is set to "none", this menu item won't show.

This is working as intended. The single/two/three column layouts are deprecated and are only present if you have a page that is already using them. With our new Page Editor, these layouts are unnecessary and only cause confusion within the system.

Typically JS files are loaded by hooking into the Dispatcher class (for v4). In v5, we created the Loader extension to handle this kind of situation. The Loader has several methods that allow you to inject JS, CSS, or even manipulate output immediately before execution is complete.

I can't reproduce this. Can you please test on 5.0.5 and let us know if it's still an issue?

We're aware of this and it will be handled in a future release. Unfortunately it's not as straightforward as other areas of the site and will need quite a bit of work.

Can you post a couple of screenshots so that we can have a clearer idea of what's happening? Without that, it's a little difficult to track things down. Some links would be even better.

You have it set to repeat an unlimited number of times. Try changing that to repeat 1.

Can you please post a screenshot of the ad configuration?