c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Friday 13 May 2011, you wrote:
> Public bug reported:
> 
> 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'...

I think the functionality you describe is already there. You see, in 
_open_image(filename, path=..) the 'path' parameter serves exactly that 
purpose. It should contain root_path, addons paths etc. I remember having 
tested that with the 'test_orm' module.

In addition, reference to configuration settings from trml2pdf is not 
advisable. We want to keep that file as agnostic of the other server's API as 
possible.

You are talking about v6.0, aren't you?


-- 
Say NO to spam and viruses. Stop using Microsoft Windows!

-- 
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"/>