It's in the way that PHP scripts call their database connection. If they all referenced which database on each call, it would be ok, but most simply assume that their connection is still opened. As the calendar is wedged between calls in Nuke, when Nuke resumes it uses the last database connection (which is the calendar's).
It's a simple enough fix, and there is no issue with having the calendar and Nuke co-existing in the same database.
__________________
-- Gervais
EPC Tutorials... We're here to help!
Offering custom integration services. Contact me here.
* Not affiliated with EasyPHPCalendar or NashTech Inc.
|