Hi there,
I am making myself a plan or structure in overrides organisation. Since in equestrian sports I need to serve so many disciplines I have to divide blocks and sign different blogs to individual disciplines.
For example:
1. Privat People
2. Companys
3. Breeders
4. Organizers
5. Guest (default)
Block: Imprint
Block: Phone Numbers
Block: Services
Block: Equestrian Champion Chip results
Block: Stallions and Mares
Block: Search Products
and much more - and always two languages
In Germany companies must have an imprint section which is a europe data protection government rule. Imprint in my case is a block assigned where it is necessary. Each block is using a bunch of form field entries taken from the fabulous form builder in easy social.
Now for each block I am writing language overrides. This makes it a lot easier to find and separate overrides.
Here is my question: I don´t use necessarily EasySocial predefined override string names. Instead I use my own string names. I create them with specific names I understand so I can assign form fields easily.
Screenshot 1: http://prntscr.com/g8rsp1
Screenshot 2. http://prntscr.com/g8rt8r
This technique seems to work fine. But I do not know if from your technical point of view this is the ride approach. Since easysocial updates coming with more form field possibilities - is it OK?. Can I just go ahead an keep using my own language strings in form field generator.
Hopefully you understand what am try to accomplish:
I am making myself a plan or structure in overrides organisation. Since in equestrian sports I need to serve so many disciplines I have to divide blocks and sign different blogs to individual disciplines.
For example:
1. Privat People
2. Companys
3. Breeders
4. Organizers
5. Guest (default)
Block: Imprint
Block: Phone Numbers
Block: Services
Block: Equestrian Champion Chip results
Block: Stallions and Mares
Block: Search Products
and much more - and always two languages
In Germany companies must have an imprint section which is a europe data protection government rule. Imprint in my case is a block assigned where it is necessary. Each block is using a bunch of form field entries taken from the fabulous form builder in easy social.
Now for each block I am writing language overrides. This makes it a lot easier to find and separate overrides.
Here is my question: I don´t use necessarily EasySocial predefined override string names. Instead I use my own string names. I create them with specific names I understand so I can assign form fields easily.
Screenshot 1: http://prntscr.com/g8rsp1
Screenshot 2. http://prntscr.com/g8rt8r
This technique seems to work fine. But I do not know if from your technical point of view this is the ride approach. Since easysocial updates coming with more form field possibilities - is it OK?. Can I just go ahead an keep using my own language strings in form field generator.
Hopefully you understand what am try to accomplish: