Prohibit Front-End modifications after date

Hi Tuan,
Is there an option to prohibit the possibilty to edit some/all fields of the userregistration on the front-end.
The case is:
When a participant made a registration a Joomla user is also created, when the participant want's to edit/modify some of his data he/she can logon (History feature of com_eventbooking).
One week in advance of the event, processing of the registrant data will begin, several suppliers must personalise startnumbers, etc.
From that moment we would like to prohit the possibilty for users to edit their personal data. For the eventmanagers these modifications must still be possible trough the backend.

My thought was to extend the "fields" table with an additional field "user_readonly" and the "event" table with a field "user_readonly"
When the event manager has exported the registrationdata , the event field "user_readonly" will be set 1 (True).
For all the fields where "user_readonly" has been set, the inputfield must be set readonly when the event itself has been set "user_readonly"

Is there already some kind of functionality or is scheduled to be available somewhere in march 2016, please let me know. Otherwise I will start with custom modifications. The disadvantage would be that i have to reapply these modifications every every update.
If you think this feature could be an enhancement of Event Booking, but you don't have the resources the develop this I could send you the modifications so you can integrate them.

Is ./components/com_eventbooking/view/registrant/tmpl/default.php the proper file where this modification must be made, or are there additional files which are used for background processing?

Hi Vincent

I am afraid of I could not include this modification to the core download package. It makes sense if you only want to disable users from updating the data on registration history, however, it doesn't make sense to me if you only want to disable updating data after their data is exported to csv file. For normal customers, I don't think this is a useful feature

So in this case, I think you will need to perform the customization and maintain it yourself

Regards,

Tuan

Hi Tuan,

Thank you for your explanation.
I already thought this would be a too specific feature to integrate in the core.
The option to disable data modification in the history, integrated as a general configuration option , would already help me a lot.
When we don't allow editing data anymore I can set this parameter.
Can this feature be realized in a core update?

Could you also please confirm if the file which I mentioned is the correct file to modify. I can make an estimate of the time to maintain this customization and discuss this with the event manager.

Vincent