Is there a way to have a RELATIVE PATH for the inclusion of objects within pulse elements, e.g. pictures in blog files.?
When using Pulse standalone I can put “./content/media/pic1.jpg” as a reference for loading the image. This will be ok when moving the project to a different server. When using Pulse with the RW-Integration stack (from instacks.com) this is no longer possible because the hierarchies of the RW-generated objects will eventually change with the publishing so the links of the objects to be included get broken. Until now I have to correct every single file. This is tedious and error-prone.
Please continue our private support conversation we already have. Thanks.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.