Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Tobias Klika 101 posts 570 karma points c-trib
    Dec 16, 2014 @ 21:49
    Tobias Klika
    0

    package.manifest doesn't load files when used in custom section

    Hi!

    I have created a custom section (ProductsSection) with a custom tree (ProductsSectionTree). Displaying the section and tree works fine. When I click on a Product tree node I want to edit it, for sure ;-)

    My problem is the package.manifest file is ignored in my plugins folder.

    Following structure:

    enter image description here

    This edit.html file gets correctly loaded with the following content:

    <form name="productForm"
          ng-controller="app.ProductEditController"
          ng-show="loaded"
          ng-submit="save(product)"
          val-form-manager>
        ....
    </form>
    

    package.manifest:

    {
        javascript: [
          '~/App_Plugins/ProductsSection/BackOffice/ProductsSectionTree/edit.controller.js',
          '~/App_Plugins/ProductsSection/product.resource.js'
        ]
    }
    

    Error is: Argument 'app.ProductEditController' is not a function, got undefined
    The network inspector does never request the files.

    Any ideas what I am doing wrong? Naming convention issue?

  • Jan Skovgaard 11280 posts 23678 karma points MVP 10x admin c-trib
    Dec 16, 2014 @ 21:53
    Jan Skovgaard
    1

    Hi Tobias

    At a first glance it seems that the package.manifest file is saved in /ProductSection/Backoffice? - It should be saved in the Root of the /ProductSection folder instead I think.

    Sorry if I'm wrong but when I look at the screedump it appears that way :)

    /Jan

  • Tobias Klika 101 posts 570 karma points c-trib
    Dec 16, 2014 @ 21:55
    Tobias Klika
    0

    Hi Jan! It's in the root, yes. I know, looking at such trees can be weird sometimes ;)

  • Rasmus Eeg 91 posts 457 karma points c-trib
    Dec 22, 2014 @ 06:55
    Rasmus Eeg
    1

    Hi Tobias,

    I've got the same problem. Take a look in your UmbracoLog.txt, and look for an error related to parsing the package.manifest.

    Best regards
    Rasmus E. 

Please Sign in or register to post replies

Write your reply to:

Draft