Re: [Fle3-users] Problem with export...

[Tarmo Toikkanen]

On 31.03.2003, 12:36:48, Richard Ford wrote:
> I saw a couple of posts on the list, but nothing that addressed my ultimate
> concern. I am running FLE 1.3b2, and wish to upgrade to the latest release.
> However, when I attempt to export the current FLE data, I get the following:
> Error: AttributeError
> tmp_objects
> Traceback (innermost last):
...
...
>  File /usr/local/Zope2.5.1/lib/python/Products/FLE/ImportExport.py, line
> 226, in exportGlobalTypes

> Help! This is a running and working FLE install that we use every day, so
> this is important to me. Any help you can give is much appreciated.

Yep, there's a bug in 1.3b2 that breaks the export. It tries to export
uncompleted thinking type sets and if no one has ever created one,
then the holder object "tmp_objects" is missing.

If you have access to the server's file system, you can edit the file
zope/lib/python/Products/FLE/ImportExport.py as follows:

 def exportGlobalTypes(self,globals):
   """Exports globally available knowledge types."""
   elem = self.dom.createElement("GlobalKnowledgeTypes")
   for set in globals.objectValues('ThinkingTypeSet'):
     elem.appendChild(self.exportTypeSet(set))
   if hasattr(globals,'tmp_objects'):
     for set in globals.tmp_objects.objectValues('ThinkingTypeSet'):
       elem.appendChild(self.exportTypeSet(set))                       

(locate the method "exportGlobalTypes" and add one if statement in the
middle (the 4th statement in the snippet above) and indent the two
following lines appropriately)

After you've made the change, refresh the product from Zope's
Management Interface (Control Panel -> Product Management -> FLE ->
Refresh -> Refresh this product). Now you should be able to make the
export.


Another choice is to upgrade to a newer version by replacing the FLE
folder with a newer product. After refreshing the product, the UI will
be quite broken and unusable, but the export functionality should
work, so you can take the export, rename the old environment and
create a new one, importing the data to it. If something goes wrong,
you can always replace the code with the old version and refresh back
to the original state.

Hope this helped.

--
Tarmo Toikkanen
http://www.iki.fi/tarmo/
The Fle3 Team
http://fle3.uiah.fi