Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!
If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.
If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.
 |
By default, all closed tasks are hidden from view. Click here to see all tasks. |
FS#54 - NoCurrDB at HCI-LOVD
Attached to Project:
LOVD 2.0
Opened by Russell Bell (rbell) - Saturday, 31 March 2012, 03:34 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 18 April 2012, 13:05 GMT+2
Opened by Russell Bell (rbell) - Saturday, 31 March 2012, 03:34 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 18 April 2012, 13:05 GMT+2
|
DetailsWe've set up LOVD at our institution using the network security mandated version 5.5 of PHP
and are having the following trouble with the installation: when Im on a the gene home page, http://hci-lovd.hci.utah.edu/home.php?select_db=MSH2 ,and select type, or simple or advanced the next page is the select gene database which will send me back to a gene home page depending on which I select another behavior: If I go to a gene page and select Unique sequence variants it will take me to http://hci-lovd.hci.utah.edu/variants.php?select_db=MSH2&action=view_unique but if I click on Hide Specific Columns I get this error: Error: NoCurrDB (Logged) Currently, no gene was selected or sent, but the currdb class has been initiated. This is a in LOVD or in one of it's modules. Debug: /views_columns.php?action=view_all&hide=true any ideas would be greatly appreciated |
This task depends upon
Closed by Ivo F.A.C. Fokkema (ifokkema)
Wednesday, 18 April 2012, 13:05 GMT+2
Reason for closing: Not a bug
Additional comments about closing: Hi, I haven't heard from you further, and I see now the problem is not occurring any more, so I'm assuming it was a problem in the server's configuration.
Wednesday, 18 April 2012, 13:05 GMT+2
Reason for closing: Not a bug
Additional comments about closing: Hi, I haven't heard from you further, and I see now the problem is not occurring any more, so I'm assuming it was a problem in the server's configuration.
Thank you for your report. I have visited this LOVD and indeed it seems to lose the CurrDB (currently selected database). However, from here I can see also other session data is lost. Can you even log in to that LOVD database? Do you have access to the php.ini file?
Thanks,
Ivo