Ticket #238 (closed defect: invalid)

Opened 19 years ago

Last modified 16 years ago

Reactor XSL Problem

Reported by: spills Owned by: somebody
Priority: normal Milestone:
Version: 2.0.304 Severity: normal
Keywords: Reactor XSL Cc:

Description

When using scaffold=true or other Reactor ORM methods such as list, MG passes the Reactor XSL files without dot notation for example: MG wants to use metadatacustom.xsl but should be metadata.custom.xsl.

Change History

Changed 19 years ago by spills

Existing 2.0 application.

Changed 19 years ago by joe.rinehart

  • priority changed from highest to normal
  • severity changed from blocker to normal
  • milestone changed from Release Public Beta 2 to Defects Awaiting More Information

Where does this "passing Reactor XSL" files happen? I'm not too sure what you're talking about: a MG .xsl file for scaffolding, or a Reactor .xsl file for a plug-in you've written?

Changed 19 years ago by joe.rinehart

  • status changed from new to closed
  • resolution set to invalid

Closing - Never got more info.

Changed 16 years ago by cfgrok

  • milestone Defects Awaiting More Information deleted

Milestone Defects Awaiting More Information deleted

Note: See TracTickets for help on using tickets.