ConLite

  • Status Researching
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Backend
  • Assigned To
    Ortwin Pinke
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version ConLite 2.0 RC
  • Due in Version ConLite 2.1
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: ConLite
Opened by Anonymous Submitter - 17.01.2013
Last edited by Ortwin Pinke - 18.01.2013

FS#98 - 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 ConLite try to get the module information over the last opened database connection instead of using it’s own connection $db?

Attached is a module for showing a Modified Shopsoftware article in ConLite for testing.

Project Manager
Ortwin Pinke commented on 18.01.2013 15:53

I have to check db-behaviour.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing