Hello,
I've installed Concerto 3.2 (with patch v3.x-v3.2.0 ) on CentOS 5.5. As
mentioned by others in a prior defect report, the configuration steps succeed
and I am able to create a sample test in the concerto interface. Examination of
the database shows that it is successfully creating tables etc. Thus the
database is accessible to the concerto platform.
But when I try to run a test, I get the error copied below and the test fails.
Looks like database access is being achieved as some of the indices are being
set correctly in the R code but the first section template is not being found
and loaded correctly.
Thanks in advance for any help. By the way, MySQL connections do work through
the R console, see that output at end of message.
__________________________________________________
Here is the error message obtained when running the test:
R output
Loading required package: sfsmisc
Loading required package: methods
[1] ""
Loading required package: DBI
[1] "Start of section with index: 1"
[1] "Start of section with index: 3"
[1] "HTML variable LOAD_HTML_SECTION_INDEX set to: 3"
[1] "HTML variable CURRENT_SECTION_INDEX set to: 2"
Error in Test1Section3() : object 'CURRENT_TEMPLATE_ID' not found
Calls: do.call -> Test1Section3
Execution halted
__________________________________________________
Here is the info showing MySQL connections are working when done through the R
console with RStudio (user, pwd and dbname info removed from con):
R version 2.14.1 (2011-12-22) Copyright (C) 2011 The R Foundation for
Statistical Computing ISBN 3-900051-07-0 Platform: x86_64-unknown-linux-gnu
(64-bit)
> library(RMySQL) > con <- dbConnect(dbDriver("MySQL"), user = "", password =
"", dbname = "") > dbListTables(con) [1] "CustomSection"
"CustomSectionVariable" "DS_Module" [4] "DS_Right"
"DS_Sharing" "DS_TableColumnType" [7] "DS_TestSectionType"
"Setting" "Table" [10] "TableColumn"
"Template" "Test" [13] "TestSection"
"TestSectionValue" "TestSession" [16] "TestSessionVariable"
"User" "UserGroup" [19] "UserType"
"UserTypeRight"
Original issue reported on code.google.com by kscalis...@gmail.com on 18 Mar 2012 at 1:02
Original issue reported on code.google.com by
kscalis...@gmail.com
on 18 Mar 2012 at 1:02