Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • stacks stacks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • YourHeadYourHead
  • stacksstacks
  • Issues
  • #607
Closed
Open
Issue created Nov 11, 2020 by Isaiah Carew@isaiahcarew☕Owner

Image stacks inside partials have HTML that is sometimes incorrect

The stack correctly exports the image, but the HTML generated doesn't always point to the correct place.

The HTML generated always points to the path of the files directory for the first time the partial was rendered to preview or rendered for publish. After this point the path is compiled in and rendered without adjustment.

There is no meta template created for the files path. Finding the use of the RW API filesFolderPath and using Stacks' exportAssetpath instead.

It would probably be good to remove the passthrough for filesFolderPath so that nodes can't use it, because it seems like it's always going to be problematic for this same reason.

Assignee
Assign to
Time tracking