Currently the callback functions are stored in a file inside the extension directory, so in order to update the extension this file gets overwritten and your own written (if you have some) functions are gone. I'm thinking about another way to fix that (for example include a file that doesn't get overwritten all the time) but for the moment it just gets overwritten – keep that in mind!
DEPRECIATED: With version 2.3.0 callback functions can be stored in an external file (see Configuration/ADVANCED/Callback Functions for details).
As all callback functions also callback functions for file handling columns receive the input of this database field. So in case you have a callback function defined for file handling files, the function will receive a coma-list of files like they are stored inside the database (depending on the option 'How to save paths into database'). You may split the files using the TYPO3 function t3lib_div::trimExplode(',', $_sValue, true) and work on the single files.
With version 2.3.0 the extension is capable of handling parameters it receives with _GET parameters. Using this and the additional links feature you are now able to create sub forms (a table of musicians with an additional link pointing to a page containing the plugin displaying songs of this musician submitted via _GET). To use this function you have to know only two things:
First of all _GET params have to in the following format: tx_mhomsqlio_pi1[param-name] This means that if you want to submit the parameter pid with value 15 you need to write tx_mhomsqlio_pi1[pid]=15 To submit more than one parameter you need to repeat this format several times: tx_mhomsqlio_pi1[pid]=15&tx_mhomsqlio_pi1[uid]=8&tx_mhomsqlio_pi1[username]=admin
And secondly, the access to _GET parameters is possible via the marker ###name### even though in this case only the param name itself is needed. In the example above: ###pid### For security reasons only parameter names of columns (shown and not shown ones) are allowed. You may then use these markers in one or several of the following flexform settings: Additional WHERE part, Foreign keys, Additional links, Pre-defined values per column.
The output format for the list is saved in a template. You can find this file named “tx_mhomsqlio_pi1.html” in the res/ directory of the extension (typo3conf/ext/mh_omsqlio/res/tx_mhomsqlio_pi1.html). If you want to change the styles first try in the template.
The default included one is splitted into two parts:
One part is also located inside the res/ subfolder of the extension directory.→ tx_mhomsqlio_style.css
The second part is part of the mh_lib extension and therefore located in typo3conf/ext/mh_lib/lib/css/.→ mh_table.css
The extension need JavaScript to be enabled on clientside. The JavaScript files are compressed, so if you want to change them – use the uncompressed (human-readable) version, change it, and compress it again, since – of course – only the *_compressed.js files are included.
Update: In case you are debug user (TYPO3 Basic Configuration → devIPmask), the uncompressed version is included.
By the way: I compressed the files using http://www.refresh-sf.com/yui/
The extension basically uses two spinners. One big one if the whole loading lasts longer and one small one for searching and file uploading process. You might want to change these so I collected a few examples. They can be found inside the res/spinner/-directory inside the extension directory. Default used ones are grey-default.gif and colored-running.gif.
In order to change them just rename them so that two spinners are called grey-default.gif and colored-running.gif.
Warning: When updating from 0.x or 1.x to 2.x versions it's very important to know that you need to reconfigure the whole backend stuff for the plugin (due to new features, restructuring, etc.). So remember that you cannot see your current configuration anymore after installing the new version!
