11-10-2015, 06:35 PM
The problem was fixed. You can update your code.
We introduce this problem when we sync all the modules with the vtlib module code base. The directory to create a new module.
In the construct before we call the function getColumnFields("Contacts" or "Service", ...) but now we have getColumnFields($currentModule).
This was the problem, because the current module when call to construct was "PDFMaker" and not the related module.
Now we use the class name for not have this kind of problems.
You can do a git pull in your code and you can see the next commits:
https://github.com/tsolucio/corebos/commit/1e07132b7e06323bbda24832160cec966f2fd366
https://github.com/tsolucio/corebos/commit/1b2885d2af5d7f19f5cd60b8ec27dcc75c119463
Thank you for find this problem and contribute to the project.
Regards,
Omar.
We introduce this problem when we sync all the modules with the vtlib module code base. The directory to create a new module.
In the construct before we call the function getColumnFields("Contacts" or "Service", ...) but now we have getColumnFields($currentModule).
This was the problem, because the current module when call to construct was "PDFMaker" and not the related module.
Now we use the class name for not have this kind of problems.
You can do a git pull in your code and you can see the next commits:
https://github.com/tsolucio/corebos/commit/1e07132b7e06323bbda24832160cec966f2fd366
https://github.com/tsolucio/corebos/commit/1b2885d2af5d7f19f5cd60b8ec27dcc75c119463
Thank you for find this problem and contribute to the project.
Regards,
Omar.