Jcasal 13:17, 28 December 2010 (UTC)
The examples uses the language model for I18N of the plugin, but does not show how this elements are added to the plugin the language directories.
Looking at profile5.xml it indicates that the language files are to be found in:
<languages> <language tag="en-GB">en-GB.plg_user_profile.ini</language> <language tag="en-GB">en-GB.plg_user_profile.sys.ini</language> </languages>
But these are the language files for the User:Profile plugin. So basically, the language translations would need to be done on another plugin's language files?
Should this tutorial show the plugin containing its own language files? For example:
<languages> <language tag="en-GB">en-GB.plg_user_profile5.ini</language> <language tag="en-GB">en-GB.plg_user_profile5.sys.ini</language> </languages>
and examples of how these files would look like...
Jcasal 21:00, 28 December 2010 (UTC)
Actually, after lots of trial and error, I have found a few other things that needed to be updated, so the changes are now published. Hope they work for others and save you some time doing your first user profile extension plugin.
I made the changes for plug-in to work as expected.
As before it was not running onUserAfterSave functon, because profile5 property in $data array was not set.
If profile keys stay the same in database, profile plugin wipes out profile5 keys and vice versa.