Ah, now I can see the field in the foruminfo array. Many thanks.
I've noticed an interesting detail: The foruminfo array contains 'ivwcode' as well as 'ivw_code'. In the database I can see only 'ivw_code', but I remember that in the beginning I had named the field 'ivwcode', without underscore, in my installer code. So it seems like the installer code somehow worked, but it did not actually create the field in the database?!
/Edit: Okay, I've added code to drop the 'ivwcode' field on uninstall and then uninstalled and reinstalled the add-on. Now the 'ivwcode' field is gone, and foruminfo contains only the 'ivw_code' field. But it does not get inserted to the database, I have to do this manually.
--------------- Added [DATE]1370685483[/DATE] at [TIME]1370685483[/TIME] ---------------
ARGH! Never mind, I'm doing all this on a test installation and my colleague has moved this test installation to a new database server without telling me. He has left the old database on the old server, so I have been looking at the wrong database all the time.
--------------- Added [DATE]1370729379[/DATE] at [TIME]1370729379[/TIME] ---------------
I have an issue with unwanted data type conversion. My custom SQL field is of type varchar(25). When it contains the string '12E03611', it will be stored as a float in the $foruminfo array. How can I force VB4 forum cache to store this as a string?
|