• Resolved olivermerk

    (@olivermerk)


    I see in the source code that you are preparing for localization of subscription texts, like “Name”, “Email” and also the text that is shown in the input fields. I appreciate this development, however, I’d suggest to make ALL text, that is shown to the end user (front end), configurable in the settings section in the back end. And only the default text for these settings is localized in the translation templates.

    By using this approach, I have already localized front end text, but I am not happy with the localized text, I still can use my own. For example, I don’t want to have a placeholder shown in the input fields. If the value comes only from a localized file, I can’t use an empty string. Currently I need to edit your source code every time you release a new version to get the result I need.

Viewing 5 replies - 1 through 5 (of 5 total)
  • I second this request.

    For the placeholder, you can use CSS as a workaround to hide it:

    .es-field-wrap input::placeholder {
    	color: white;
    }
    Thread Starter olivermerk

    (@olivermerk)

    Thank you!

    I didn’t knew the css selector format “input::placeholder” until now.

    Thread Starter olivermerk

    (@olivermerk)

    .es-field-wrap input::placeholder {
    	color: transparent;
    }

    is even more flexible

    yes, and you can also add this for Edge:

    .es-field-wrap input::-webkit-input-placeholder {
    	color: transparent;
    }
    Plugin Contributor Malay Ladu

    (@malayladu)

    @olivermerk

    Make subscription text user configurable

    Thanks for your suggestion. We will consider to add this in the future version of Email Subscribers.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Make subscription text user configurable’ is closed to new replies.