Issues are inserted in the database without project_id value.
We probably need to A) update the CLI to inject a project ID and B) update the SQL dump.
I believe we are not 100% clear how to handle "projects".
Actually the projects are implemented as custom fields aka categories which is, i have to admit it, a more than limited solution.
I think we should implement a simple CRUD thingy for managing a projects table that may hold project specific fields. I have that already in the mvc branch using JForm without touching legacy (I hope).
Until then, maybe we should hard code a 1
where that data gets inserted :P
the csv file is just another thingy to get data from somewhere (actually a quite important place) without being really useful.
BTW: Are there any new on how to access jcode somehow and maybe integrate the "events" from there into our "events stream" ?
Sam passed on to me a while back they had a solution in their code on the developer site. When I get back from my mandated focus solely on my day job, I can talk to Andrew or someone to try and get access to that.
I'll also switch the live instance over to working with the CMS repo, and will probably be able to receive from both Joomlacode and GitHub once I figure out their solution on the developer site.
Ahh yes, just seen the csv isn't actually being used. its getting its data from sampledata.sql. My bad
The issue seems to be in the processscsv.php file
There are no project_id's in the CSV so they have hardcoded a 2. But even that isn't going through to the db