Forum .LRN Q&A: Re: .LRN 2.5.0

At yesterday meeting, Dario from Universidad de Valencia offered to test assessment on postgresql 8.3. Alvaro also offered to do some testing (pg too). Thank you both!

We are still missing people to test .LRN install and upgrade on Oracle. This is making very difficult to keep supporting Oracle for future releases ... so please, Oracle users, show up!

Thanks, that's great news.

If you can, please join the next meeting to report on your testing (check your local time for tuesday 2-jun-2009 16:00 GMT).

here are our results:

Our LRN 2.5 tests
We at Viaro tested dotLRN 2.5 this last few days and this are our results.

We tested it using Oracle 11G, doing both fresh installs and upgrades.

Doing a fresh install we did not found any problems.
Doing an upgrade from 2.4.1 to 2.5.0d2 on Oracle 11G

• Assessment now requires Views, so it asked for it while doing the upgrade.
• For some reason the first time we tried to do the upgrade the upgrade script upgrade-5.5.0d3-5.5.0d4.sql did not ran correctly, we were missing the column implements_subsite_p but a second test did loaded the file correctly.
• While upgrading ACS Events we got an error with a call done to: apm_package_version.add_dependency, it complains about having the wrong number/kind of arguments.

On both fresh installs and upgrades we ran the automated tests and did some manual tests.

Assessment
• assessment_create_and_respond
• cleanup_test

dotlrn
• tclwebtest_dotlrn_edit_term
• tclwebtest_dotlrn_edit_subject
• tclwebtest_dotlrn_new_class

dotlrn-homework
• homework_new

Manual Tests:

We tested the normal operation of a few packages, including forums, file storage, faq, Lars blogger and the general use of dotlrn, like creating classes, everything seems to be working fine but we did noticed a weird problem on some dotlrn pages, especially the “assignments” portlet under the “class material” page inside a class. The problem is that the text, links, all, is painfully small to the point that is impossible to read.

Thanks for your commit.

Regarding the way to get the localized pretty_name, I recommend to use lang::util::localize instead of lang::message::lookup. It would be more straightforward requiring less code and dealing with the cases when the pretty_name is a combination of literal text and message keys (can happen!).

Regarding the form to edit assignments types, the pretty name form fields should be enabled for edition (the value need to be localized as you did). Those types are created by default to provide a pre-configured environment but they may not match the end users needs so they need to be editable.

Also, usually a course will be used in one sole language, so if the admin/teacher decide to enter a literal string it's OK. Anyhow, it should be admin/teacher decision, not the developer one. Also it would be a bit excessive to ask for a message key here.

Thanks for the help with the render of the message-keys, it's a lot better this way, I just commit again using that proc.

The tiny text in the evaluation portlets has been fixed.

I take advantage to remind that the <small> HTML tag must not be used, styles must be set via CSS only.