Forum .LRN Q&A: .LRN 2.1 update

Collapse
1: .LRN 2.1 update
Posted by Tracy Adams on 08/06/04 10:16 PM
Hi everyone,

We've been heads down trying to get the oacs2-1 branch ready for the Sloan upgrade.  (August 15th).  We NEED to hit this date because it is the only window until January.
We've been fixing lots of bugs, got a lot of Sloan's fixes from the last year or so in, and stabalizing various modules.

Here is the plan.
-- On Sunday, I'm going to cut a .LRN 2.1 alpha release.
-- We are going to use this release, do a merge with Sloans (much smaller now) customizations, and spend the week preparing for the upgrade.
-- After the upgrade, we'll continue on the .LRN 2.1 release path toward beta, release candidate, etc.

One notice....

If you are going to be a user of .LRN 2.1, it is your or your institution's responsibility to fully test the code, make a list of bugs you would like fixed, and participate in the community to help get these bugs fixed.

Open source is a highly participatory process.  If you don't do this, you will have no right to later complain that the release does not have a given fix you need.

There is not much participation in this release.  I have the feeling that everyone is on to future things.  I want to raise awareness that if you want certain items in the release, now is the time to step up and get it done.

Collapse
2: Re: .LRN 2.1 update (response to 1)
Posted by Rocael Hernández Rizzardini on 08/06/04 10:37 PM
Hello Tracy,

its the oacs-5-1 branch that you'll tag sunday night as dotlrn-2-1-alpha...
Also, this release should come with the openacs-5-1-2 release (cut), its time to do it, OCT?
For the openacs-5-1-2 there's a need to integrate the latest changes on the catalogs (as usual).
But this new openacs-5-1-2 release should come with the dotlrn-2-1-RC1, don't you think?

Collapse
3: Re: .LRN 2.1 update (response to 2)
Posted by Tracy Adams on 08/06/04 10:46 PM
<blockquote>>But this new openacs-5-1-2 release should come with the dotlrn-2-1-RC1, don't you think?
</blockquote>

Yes, I'd agree.  If openacs-5-1-2 comes soon (next few weeks), then we'd use that as the core in any of the .LRN 2-1 releases that come after openacs-5-1-2 is released.

Collapse
4: Re: .LRN 2.1 update (response to 1)
Posted by Nima Mazloumi on 08/09/04 12:03 PM

Hi all,

here is the stuff I was working on last week:

Still Open

  • Orzenil/Dave and I were trying to fix a news aggregator problem. But we had no success. Since I was never able to verify this on the test server (for oracle) it would be great if someoen could try this out. The portlet should be broken and adding feeds too (diff see below). Also we found out that the queries a_add_source.add_source and na_add_source.add_item for news-aggregator-procs-oracle.xql have semi-colons after the "end" key word which Oracle doesn't like.
  • Photo-Album didn't work. I added the missing album-chunk-oracle.xql. Still I have an error adding a picture. Can someone verify this as well?
  • portrait upload fails (reported a bug: #2055)
  • community-member unable to include shared files temlate, page broken (reported a bug #2054)

Fixes/Improvements

  • While the weblogger-portlet package on CVS is accurate the one offered by the openacs repository contains an error in the sql: /packages/weblogger-portlet/www/weblogger-portlet-oracle.xql to_char(e.posted_date , 'HH24:MI') should be to_char(e.entry_date , 'HH24:MI') order by p.package_id asc, e.posted_date desc should be order by p.package_id asc, e.entry_date desc. This was fixed. Also a missing noquote in the webloger-portlet.adp (entries.content)
  • Missing noquote for the context-bar in dotlrn/www/community-member.adp added
  • Added unarchive for communities and classes. Works on Oracle and PostgreSQL (Thanks to Bergen).
  • Added links to forum admin portlet to see all forums and to admin the current forum (dotlrn-forums package)
  • Photo-Album - missing oracle queries for album-chunk added (thanks to Dave and Mark)
  • Added Translate Link to acs-developer-support header
  • Added Administration Cockpit for dotLRNs: User's controlpanel-->Cockpit link

Greetings,
Nima 

Index: news-aggregator/tcl/news-aggregator-procs-oracle.xql
===================================================================
RCS file: /cvsroot/openacs-4/packages/news-aggregator/tcl/Attic/news-aggregator-procs-oracle.xql,v
retrieving revision 1.2.4.1
diff -r1.2.4.1 news-aggregator-procs-oracle.xql
15,16c15,16
< 		 description => :description,
< 		 creation_user => :owner_id,
---
> 		         description => :description,
> 		         creation_user => :owner_id,
30,47c30,32
< 		 description => :description,
< 		 => sysdate,
< 		 => '0'
<              );
<              end
<         </querytext>
<     </fullquery>
< 
< <fullquery name="na_add_source.add_item">
<       <querytext>
< 	     begin
<              :1 := na_source.new (
<                  source_id => :source_id,
<             	 link => :link,
<              	 title => :title,
< 		 description => :description,
< 		 => sysdate,
< 		 => '0'
---
> 		         description => :description,
> 		         creation_date => sysdate,
> 		         deleted_p => '0'
Index: news-aggregator/tcl/news-aggregator-procs.tcl
===================================================================
RCS file: /cvsroot/openacs-4/packages/news-aggregator/tcl/news-aggregator-procs.tcl,v
retrieving revision 1.6
diff -r1.6 news-aggregator-procs.tcl
132a133,151
> ad_proc -public na_get_elements {
>      nodes
>      match
>  } {
>      set matches [list]
>      foreach node_id $nodes {
>          if { [string equal $match [xml_node_get_name $node_id]] } {
>              lappend matches $node_id
>          } else {
>              #set children [ns_xml node children $node_id]
>              set children [xml_node_get_children $node_id]
>              if { [llength $children] > 0 } {
>                  set matches [concat $matches [na_get_elements $children $match]]
>              }
>          }
>      }
>      return $matches
> }
> 
170,172c189,191
< 	    set title [string_truncate -len 245 -no_format -- [lindex $channel 0]]
< 	    set link [string_truncate -len 245 -no_format -- [lindex $channel 1]]
< 	    set description [string_truncate -len 245 -no_format -- [lindex $channel 2]]
---
> 	    set title [string_truncate -len 245 -- [lindex $channel 0]]
> 	    set link [string_truncate -len 245 -- [lindex $channel 1]]
> 	    set description [string_truncate -len 245 -- [lindex $channel 2]]
182,183c201,202
< 		    set title [string_truncate -len 245 -no_format -- [lindex $item 0]]
< 		    set link [string_truncate -len 245 -no_format -- [lindex $item 1]]
---
> 		    set title [string_truncate -len 245 -- [lindex $item 0]]
> 		    set link [string_truncate -len 245  -- [lindex $item 1]]
214,215c233,234
<             set title [string_truncate -len 245 -no_format -- [lindex $item 0]]
<             set link [string_truncate -len 245 -no_format -- [lindex $item 1]]
---
>             set title [string_truncate -len 245 -- [lindex $item 0]]
>             set link [string_truncate -len 245 -- [lindex $item 1]]
249,251c268,270
< 	    set title [string_truncate -len 245 -no_format -- [lindex $channel 0]]
< 	    set link [string_truncate -len 245 -no_format -- [lindex $channel 1]]
< 	    set description [string_truncate -len 245 -no_format -- [lindex $channel 2]]
---
> 	    set title [string_truncate -len 245 -- [lindex $channel 0]]
> 	    set link [string_truncate -len 245 -- [lindex $channel 1]]
> 	    set description [string_truncate -len 245 -- [lindex $channel 2]]
Collapse
5: Re: .LRN 2.1 update (response to 1)
Posted by Tracy Adams on 08/09/04 04:37 PM
Nima,

News aggregator, weblogger and photo album are not modules we are focusing on in this release.

By all means, people can work on them and release new versions - we don't want to stop progress.

However, we selected the core modules to clean up and prepare officially for .LRN 2.1.

Thanks for your help!

Tracy