Forum OpenACS Q&A: Glossary content dissapears

Collapse
Posted by Ben Koot on
Something funny happend im glossary. I created http://snorri.mine.nu/helpforaday/glossary/ . It worked fine for 72 hours and than all of a sudden all content (248 items) disapeared. Does anybody have a similar experience? I noticed this before but thought it was due to errors on our old installation.

Thanks
Ben

Collapse
Posted by Samir Joshi on
Ben,

I know this was a bug in glossary - terms expire after 2 days. Terms are there but not displayed as the code considers them as expired...

AFAIK, it was fixed - what is the OACS version / Database you are using ?

Collapse
Posted by Lokman Tsui on
I have the exact same problem with glossary.
I have been using OACS 4.6 and postgres 7.2.2

In addition, when I try to change the status of an existing term from live to, let's say, production, I get the following error message (upon reload and despite the error, the status of the specific term *is* changed from live to production)

---

can't read "mime_type": no such variable
    while executing
"ad_html_text_convert -from $mime_type -- $definition"
    invoked from within
"set html_definition [ad_html_text_convert -from $mime_type -- $definition]"
    ("uplevel" body line 88)
    invoked from within
"uplevel {
          # glossary/www/term.tcl

ad_page_contract {
    the ACS 4 Glossary Package based on the glossary module written by Philip Greenspun (..."
    (procedure "code::tcl::/web/openacs-4/packages/glossary/www/term" 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 7)
    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([ad_conn url]) [ad_conn path_inf..."

Collapse
Posted by Ben Koot on
Jade,

Thanks for the tip. I will be upgrading this week from 4.6 and postgres 7.2.2

Ben

Collapse
Posted by Ben Koot on
Hi folks,

We upgraded our installation, but the problem is still there. I hope this can be solved, because Glossary is one of the core modules i am using for the final Timedesk site.
Thanks
Ben

Collapse
Posted by Lokman Tsui on
Same thing here. I upgraded my OpenACS installation
plus the glossary package to the 4.6.2 final release and the problem of expiring terms persists.

Someone please help?

Collapse
Posted by Robert Locke on
I haven't used glossary, but poking around the code shows these lines in glossary-oracle/postgresql.tcl:
    and publish_date > sysdate -1 (oracle)
    and publish_date > current_timestamp - interval '1 day' (pg)

Perhaps changing it to:
    and publish_date < sysdate (oracle)
    and publish_date < current_timestamp (pg)

or maybe removing the clauses altogether will achieve the desired effect.

Please take this with a grain of salt, as I haven't used the module yet. =)

Collapse
Posted by Windell Dubois on
Ive been using the glossary package in my 4.6.3 instance, and have poked around its code, as suggested in this thread, I managed to keep the glossary terms alive, but the other error mentioned on this thread (the one about changing the state of a term from live to any other) still remains.  Has anyone found a way to fix this or to at least go around it?

Thanks in advance.

Collapse
Posted by Windell Dubois on
Just another thing, is there any reason why a function for deleting terms within a glossary was never created?