Forum .LRN Q&A: dotlrn-xowiki and xowiki-portlet available

Here are some comments though:

a) Providing the URL via APM is great, if the install from URL process would work 😊. At least on my Ubuntu it failed miserably, so I had to download the APM in the /packages directory and untar it manually

b) When I add the page (selecting on from the drop down box), this is what happens:

Error:

No page 'admin/portal-element-add' available.

From the URL:

/dotlrn/clubs/technics/xowiki/admin/portal-element-add

I found out why: You added the page to xowiki, but did not increase the version and the dependency, so I had to first update XoWIKI in CVS :).

Now this works, but I wonder if there is a parameter to NOT display the editing links (or search aso.) in the portlet itself. Not sure if you want to have them in a portlet. And if you do, it would make more sense to have an edit button in the portlets header.

Last but not least, will you commit it to CVS ?

Just one comment/bug: the content of the portlet doesn't fit in correctly.

Regards,

Jose Pablo

Thank you very much for this. I was already losing a lot of time, because one of my clients requested the same thing. I can say you saved me a lot of time, and I'm very thankful for this.

I'm still trying to install it, but I have a question: does it work on dotLRN 2.2.0? The dependencies say that it doesn't, but I really didn't want to upgrade right now. I have a large system, and upgrade it allways gives a hard time. Is there anyway I can make it work on dotLRN 2.2.0?

https://openacs.org/forums/message-view?message_id=546200

I checked the changes and the packages seem to work very well in dotlrn 2.2.0. Maybe you should change the number in the .info.

I bumped down the version number of dotlrn required to 2.2.0 to allow the install as Eduardo did.

I followed the instructions through to clicking on:

Add New Xowiki Portlet

This should add a new xowiki portlet but I get an error message as follows:

wrong # args for method 'resolve_request': valid arguments -path method_var
while executing
"::xotcl::interpretNonpositionalArgs $args"
(procedure "resolve_request" line 2)
::2475139 ::xowiki::Package->resolve_request
invoked from within
"$package_id resolve_request -path $page_name"
invoked from within
"set page_id [$package_id resolve_request -path $page_name]"
("uplevel" body line 17)
invoked from within
"uplevel {
::xowiki::Package initialize -ad_doc {
Add an element to a given portal

@author Gustaf Neumann (mailto:gustaf.neumann@wu-wien.ac.at)
@creati..."
(procedure "code::tcl::/var/lib/aolserver/dotlrndev/packages/xowiki/www/..." line 2)
invoked from within
"code::tcl::$__adp_stub"
invoked from within
"if { [file exists $__adp_stub.tcl] } {

# ensure that data source preparation procedure exists and is up-to-date
adp_init tcl $__adp_stub
..."
("uplevel" body line 3)
invoked from within
"uplevel {

if { [file exists $__adp_stub.tcl] } {

# ensure that data source preparation procedure exists and is up-to-date
adp_init t..."
(procedure "adp_prepare" line 2)
invoked from within
"adp_prepare "
(procedure "template::adp_parse" line 30)
invoked from within
"template::adp_parse [file root [ad_conn file]] {}"
(procedure "adp_parse_ad_conn_file" line 5)
invoked from within
"$handler"
("uplevel" body line 2)
invoked from within
"uplevel $code"
invoked from within
"ad_try {
$handler
} ad_script_abort val {
# do nothing
}"
invoked from within
"rp_serve_concrete_file [ad_conn file]"
(procedure "rp_serve_abstract_file" line 60)
invoked from within
"rp_serve_abstract_file "$root/$path""
("uplevel" body line 2)
invoked from within
"uplevel $code"
invoked from within
"ad_try {
rp_serve_abstract_file "$root/$path"
set tcl_url2file([ad_conn url]) [ad_conn file]
set tcl_url2path_info..."

Any ideas anyone?

cheers

To ease release management, we will store a "stable version" of xowiki in the oacs-5-3 branch in the future.

-gustaf

[[image:podcast.jpg|Download Conference Presentationa as as Podcast|-href itpc://oacs-dotlrn-conf2007.wu-wien.ac.at/conf2007/podcast]]

For providing a link to a single podcast content file, use
[[file:ACSkonferenz_neumann_xowiki_cutVGA.mp4|Presentation Neumann]]

Error in include template "/srv/www/openacs-4/packages/xowiki-portlet/www/xowiki-admin-portlet": unknown argument '-order_clause' for method 'instance_select_query': valid arguments {-select_attributes {}} {-orderby {}} {-where_clause {}} {-from_clause {}} {-with_subtypes:boolean true} -publish_status {-count:boolean false} -folder_id {-page_size 20} {-page_number {}}

Is my xotcl (1.5.3) too old?

The quick solution is as follows:

• i added a global varible to view:
  http://cvs.openacs.org/cvs/openacs-4/packages/xowiki/lib/view.tcl?r1=1.8&r2=1.9
  (this is committed to cvs head)

• and added the following to blank-compat.tcl (after the translation loop)

  if {[info exists ::xowiki_head]} {
    append head \n $::xowiki_head
  }

  Not committed to cvs, since there must be a better way of achieving this.... but it does the trick

Thanks

a) create a new category tree "state of work" with e.g. categories "open", "under work", "done" and map it to the xowiki of the community.

b) create an xowiki page for e.g. the open items (en:open) with a content like
----
{{weblog-portlet -category_id 4305 -summary 1 -decoration plain}}
----
where the category_id is the one for the open items (find the category_id e.g. via "en:weblog", by clicking on the categories)

c) add the xowiki page "en:open" as portlet from the admin-page of the community

If you create some pages with an description, categorized with "open", you will get the listing with the description in the page en:open (since "-summary 1" is used above).

In case, you want to change the layout of the summary, edit en:weblog-portlet (or rename it) and change the WeblogRenderer (responsible for rendering the full listing) and/or the EntryRenderer (responsible for rendering a single entry). Most likely it is sufficient to remove some of the markup. If you rename e.g. en:weblog-portlet to en:listing, don't forget to change the name as well in (b) above.

Does this help?

-gustaf neumann
PS: i have just updated the weblog-portlet to accept the category_id from the includelet call. If you have a fairly recent installation, you should be able to make the following change to packages/xowiki/www/prototypes/weblog-portlet.page
http://cvs.openacs.org/cvs/openacs-4/packages/xowiki/www/prototypes/weblog-portlet.page?r1=1.12&r2=1.13

I have a little doubt about the way xowiki portlets are inserted in community pages. My Portal has a growing need for internationalization, in such a way that even the community content must be in many languages. The community description, static info, everything must be internationalized.

The best way to do that was to use Xowiki Portlets to serve multi-language content, the same way as it's done in Xowiki when use_conncetion_locale parameter is set to 1. However, I found a problem when trying to do that: the portlets are created based on the full page name, wich includes the locale already (ex.: en:index). In that way, every page translation is like a different portlet.

I was trying to discover how to solve this, but I've stucked in my poor Xowiki skills. I've seen that the creation request is sent to the xowiki/www/admin/portal-element-add, wich gets the page_id using the page_name by the resolve_request method. It would be also necessary to change te portlet render page, wich seems to me the /xowiki/lib/view file.

So, can you guys point me a direction to solve this issue?

Thank you very much for your help again. I was thinking about to do almost the same thing you told but your approach is the best, as usual.

I've seen your presentation video about xoportal and I'm very excited about it. Let me know if I can help somehow.

Thank you for the help again.