drugCMS

  • Status New
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Backend
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Normal
  • Reported Version CL 2.0 PR
  • Due in Version 2.1.0
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: drugCMS
Opened by René Mansveld (Spider IT) - Y-m-d

drugCMS#14 - Problems while connected to a second database

If, in a module, you connect to an external database, all modules after that one in the template won’t work.
The configuration for those following modules says “-unnamed module-”.
If you close the connection to the external database in the module, the following modules work as they should.

If you have the module with the external database connection more than once in the template, directly following eachother, then each second one won’t connect to that database even if you use different variables for the connection, but only in the backend (configuration).
In the frontend everything works as it should even with the same variable for the external database connection, but only while closing the connection in the module (every instance).

Question/Problem:
Why does drugCMS try to get the module information over the last opened database connection instead of using it’s own connection $db?

This task does not depend on any other tasks.

Loading...