Symphony.

While translating a couple of strings related to the email gateways preferences, I noticed this paragraph:

The following default settings will be used to send emails unless they are overwritten.

I tried to translate the following, but the more I tried the more I realized this string is quite useless. In fact, it doesn't add any useful informations that can't be already perceived from the context. After all, if an user is in the Preferences page he knows he's dealing with settings.

Furthermore, it doesn't seem to be frequent to use black paragraphs inside the backend to explain something. So... what about getting rid of that string?

I think the point of the copy, which it probably doesn't emphasis completely, is that these settings can overridden programmatically, these are just the defaults.

Brendo is right. What this line wants to say is something like:

The following default settings will be used to send emails (with the selected gateway) unless they are overwridden by extensions or custom code using the Core Email API.

Would be nice to have a short version of this...

The following default settings will be used to send emails (with the selected gateway) unless they are overwridden by extensions or custom code using the Core Email API.

Looks more like a developer thing rather than a help message for users though...

I'm with Simone that the copy is confusing as it mixes up developers and users. Why don't we rename the fieldset to Default Email Gateway which implies that overriding the settings is possible.

In my opinion this help text can be removed, too:

The Symphony core will use the selected gateway to send emails. More gateways can be installed using extensions, and any gateway may be used by custom events or extensions.

There is no other place in the interface where we inform the user this way (we don't highlight in the section editor that more fields can be installed via extensions for example).

we don't highlight in the section editor that more fields can be installed via extensions for example

Really good point, Nils :)

Why don't we rename the fieldset to Default Email Gateway which implies that overriding the settings is possible.

I'm not sure about "Default Email Gateway", but sounds like we are close...

What about Default Gateway Settings?

I'd hate to nitpick and stall this any further, but Gateway in Symphony context refers to the CURL/socket wrapper.

Default Email Gateway Settings?

Ah, you're right. To make it shorter, what about Default Email Settings using Gateway as label for the select box:

Attachments:

sym_emailgateway.png

@Nils: Perfect!