Installed as neither, they were exported by folder.
On Mon, Feb 25, 2013 at 6:29 PM, Chris <[email protected]> wrote: > Can you describe how you are exporting? Are you selecting only > individual elements, whole folders? Are the scripts installed as a > module/package/neither? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1112223 > > Title: > Package Exporter - Applies the </MudletPackage> too early in the XML > > Status in Mudlet the MUD client: > New > > Bug description: > I created two seperate XMLs for small systems. Both inserted the > </MudletPackage> tag just after the Trigger package ended. When > attempting to import those XMLs, mudlet never read and imported the > Alias' or Scripts. > > Mudlet ver. 2.1 - Current Build > OS X Mountain Lion > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mudlet/+bug/1112223/+subscriptions > -- Respectfully, SGT Daniel Johnson 2nd Brigade Combat Team Public Affairs -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1112223 Title: Package Exporter - Applies the </MudletPackage> too early in the XML Status in Mudlet the MUD client: New Bug description: I created two seperate XMLs for small systems. Both inserted the </MudletPackage> tag just after the Trigger package ended. When attempting to import those XMLs, mudlet never read and imported the Alias' or Scripts. Mudlet ver. 2.1 - Current Build OS X Mountain Lion To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1112223/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
