{field} placeholder does not get replaced with field name in a custom error message

{field} placeholder does not get replaced with field name in a custom error message

Gary
Member
Posts: 185
Threads: 35
Joined: Oct 2019
Reputation: 2

04-17-2020, 03:12 PM

Good going.

What's wrong with modifying the language files... they are in the app directory = for user modification. It's only mods to things in the system directory that's frowned upon.

Messages In This Thread

{field} placeholder does not get replaced with field name in a custom error message - by dgvirtual - 04-17-2020, 06:45 AM

RE: {field} placeholder does not get replaced with field name in a custom error message - by Gary - 04-17-2020, 07:23 AM

RE: {field} placeholder does not get replaced with field name in a custom error message - by dgvirtual - 04-17-2020, 09:08 AM

RE: {field} placeholder does not get replaced with field name in a custom error message - by Gary - 04-17-2020, 09:24 AM

RE: {field} placeholder does not get replaced with field name in a custom error message - by dgvirtual - 04-17-2020, 02:39 PM

RE: {field} placeholder does not get replaced with field name in a custom error message - by Gary - 04-17-2020, 03:12 PM

RE: {field} placeholder does not get replaced with field name in a custom error message - by dgvirtual - 04-17-2020, 03:18 PM

RE: {field} placeholder does not get replaced with field name in a custom error message - by Codinglander - 01-23-2021, 05:44 PM