Results 1 to 3 of 3

Thread: Architect 2 + Cmd 3 - bug when defining stores etc on the Controller not on the App

    Success! Looks like we've fixed this one. According to our records the fix was applied for a bug in our system in a recent build.
  1. #1
    Sencha Premium Member
    Join Date
    Jan 2011
    London, UK
    Vote Rating

    Default Architect 2 + Cmd 3 - bug when defining stores etc on the Controller not on the App


    Not sure if this is the right place to post - so feel free to move if you want to.

    I have a simple app
    - created by Architect for Ext 4.1.x
    - then using Sencha Cmd v3.0.0.230 and Ext 4.1.2a I run
    sencha generate app
    to create app of same name into the Architect app folder.

    Then I updated
    - index.html to point at app.js generated by Architect
    - Architect to point at ext library folder /ext/ as generated by Cmd
    - Architect Application name to match the app name generated by Cmd

    See attached zip for the resulting application. (excludes /ext/ source folder)

    This has a simple store / model defined - and works well when tested using

    Then after running
    sencha app refresh

    bootstrap.js is regenerated to pick up the custom model / store etc...
    And the app can be tested using

    All fine so far.

    But I like to include stores / models / views in the relevant Controllers so that
    - the app is more tidy
    - I can use the handy generated getter and setter methods in the Controller

    Here's where I hit the problem.

    Testing with app.html is all still fine.
    But when I regenerate the bootstrap.js and test again via index.html - the relative paths are messed up.

    Failed to load resource: the server responded with a status of 404 (Not Found)

    See attached zip where the store and model are now referenced in the Controller. (excludes /ext/ source folder)

    This isn't something that would normally be a big issue - but I am working on an application that gets additional data included in index.html from the server when it's launched.
    I can't simulate this data on app.html as Architect would keep trashing it.
    So I use index.html instead.

    Workaround for now is to keep all references out of the Controllers .. or to always preview a built version of the application.

    Apart from that I've not hit any other issues with Architect and Cmd working together .


    Attached Files Attached Files

  2. #2
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Olney, MD
    Vote Rating


    moved to Cmd forum. My short answer is I'm not sure and that I'll be learning something when Cmd team responds!
    Phil Strong

  3. #3
    Sencha Premium Member
    Join Date
    Oct 2010
    Vote Rating


    This is fixed in latest Sencha Cmd V3.0 GA (

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts