Forum .LRN Q&A: Re: LAMS2 and .LRN integration (beta) released!

Sorry it took so long to get back to you. Thanks for looking into this.

I installed the dotlrn LAMS packages into a new dotLRN 2.3.0 install and got the same error that I got in the dotLRN 2.3.1 install. The $xml variable is an empty string.

I added some ns_log statements to add.tcl & add-2.tcl to help debug things. The call to [ad_httpget -url $lesson_url -timeout 30] in add-2.tcl is returning "page {} status 505 modified {}". Any idea way this might be happening?

Here is the slightly modified $lesson_url being passed into ad_httpget "http://xxx.xxx.xxx.xxx:8080/lams/services/xml/LessonManager?method=start↦serverId=dotlrn&ldId=26↦datetime=October+02%2c2007+01%3a32+PM↦hashValue=9b0713f421a8c5f691349eb5f46c6f4ec809ce11↦username=567↦courseId=2346↦title=SHFR-DEVEL TEST↦desc=Test LAMS course.↦country=AU↦lang=en"

The LAMS2 server was installed into a CentOS 4.5 server using the instructions on the LAMS site. The LAMS2 server seems to work fine on its own so I think its running properly.

Thanks,

Rob

I'm running LAMS 2.0.4 and I couldn't find any 505 errors in any of the jboss or LAMS logs.

I did manage to solve the issue though.

I started looking at the $lession_url in add-2.tcl and noticed that '&title=$name' and '&desc=$introduction' were not being URL encoded so in the 'set lession_url "$lams_server_url/...' statment I added a 'ad_urlencode' to URL encode the vars '...&title=[ad_urlencode $name]&desc=[ad_urlencode $introduction]...' then everything worked as expected. I guess the spaces in the text of the URL was causing the 505 error.

Thanks,
Rob