c2c-oerpscenario team mailing list archive

["Equipo OPENTIA \(http://www.opentia.com\)" <781967@xxxxxxxxxxxxxxxxxx>]

Using the 6.0 branch here, on Debian wheeze/sid and on squeeze, with
Python 2.6.6.

Thanks xrg. You are right, it's not the right place to add modifications
to the path. It's the _get_path() method, in the 'report_rml' who should
include the additional 'addons_path' directories.

In this case it's more clear, since the image element just needs the
name of the file put in the same directory than the RML template file:

       <image file="my_report_image.png" x="0" y="0"/>

** Patch added: "20110513-_get_path.patch"
   https://bugs.launchpad.net/openobject-server/+bug/781967/+attachment/2126666/+files/20110513-_get_path.patch

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/781967

Title:
  RML based reporting broken for addons with images outside root_path

Status in OpenERP Server:
  New

Bug description:
  Currently, in order to be found by OpenERP, image elements within RML
  templates must be specified making use of paths relative to
  'root_path'. With the 'addons_path' functionality, this behaviour
  becomes inconsistent; if an addon is moved to a valid directory
  outside the 'root_path' directory, the reporting process is broken and
  the server raises an IOError exception.

  To deal with this problem, the RML template must contain the full path
  to the image file (which can be anything but flexible), or make use of
  a custom tag to set up the path dynamically.

  Attached is a patch that enables the server to recognise image
  elements with paths relative to the module directory, regardless of
  the addons directory where it is. I.e.:

      <image file="my_addon/images/my_report_image.png" x="0" y="0"/>