Installation Error

[tsega]

I'm having problems installing blaze-layout:

Problem installing blaze-layout
  ✘ [branch: https://github.com/EventedMind/blaze-layout.git#master] conflicts with [branch: https://github.com/EventedMind/blaze-layout.git#devel]
Can't resolve dependencies! Use --force if you don't mrt taking a wild guess and running your app anway.

Here is my smart.json file:

{
  "packages": 
  {
    "accounts-ui-bootstrap-dropdown": {},
    "font-awesome": {},
    "accounts-ui-bootstrap-3": 
    {
        "git": "https://github.com/mangasocial/meteor-accounts-ui-bootstrap-3.git",
        "branch": "blaze"
    },
    "bootstrap3-less": {},
    "moment": {},
    "bootstrap3-datetimepicker": {},
    "iron-router": 
    {
        "git": "https://github.com/EventedMind/iron-router.git",
        "branch": "blaze-integration"
    },
    "inspector": {},
    "blaze-layout": 
    {
        "git": "https://github.com/EventedMind/blaze-layout.git",
        "branch": "devel"
    }
  }
}

I've tried to use the --force and the error goes away. However, when I try to use the blaze-layout features it doesn't work as expected. How can fix this?

[PeppeL-G]

I'm getting the following error (which I guess is related):

Problem installing blaze-layout
  ✘ [branch: https://github.com/EventedMind/blaze-layout.git#master] conflicts with [latest]
Can't resolve dependencies! Use --force if you don't mrt taking a wild guess and running your app anway.

Using --force makes no difference in my case.

Here's my smart.json (I've played a bit with it with the humble intention of fixing the problem (without success), so now it's maybe even more messed up):

 {
  "packages": {
    "iron-router": {
      "git": "https://github.com/EventedMind/iron-router.git",
      "branch": "blaze-integration"
    },
    "blaze-layout": {},
    "bootstrap-3": {},
    "collection-hooks": {},
    "codemirror": {}
  }
}

[cmather]

If you're trying to use this package with iron-router, it's included automatically. I would remove the blaze-layout from smart.json and just have iron-router.

[cmather]

Also change iron-router branch to dev. It's moving closer to release. But keep in mind the dev branch (and any branch other than master) is pre-release and a moving target :).

[PeppeL-G]

Thanks @cmather , removing blaze-layout made it work again (and using the dev branch of iron-router also works). Seems though like my calls to pathFor isn't working anymore if the path uses of parameters. You haven't changed how that's supposed to work, right?

[cmather]

I have but it's not documented yet. Check out iron router lib/client/helpers.js. The implementation should be pretty easy to understand and I can help if need be.

On Mar 21, 2014, at 12:53 PM, PeppeL-G notifications@github.com wrote:

Thanks, removing blaze-layout made it work again (and using the dev branch of iron-router also works). Seems though like my calls to pathFor isn't working anymore if the path uses of parameters. You haven't changed how that's supposed to work, right?

—
Reply to this email directly or view it on GitHub.

[PeppeL-G]

Thanks for your time, it's very appreciated!

I did found the helper (in lib/client/ui/helpers.js), and it turned out I'll have to change all my {{pathFor 'routeName'}} to {{pathFor 'routeName' params=this}}. Unless it is I who use the helper wrong, this seems like an unnecessary detour to me, but let us not discuss an iron-router matter in the blaze-layout anymore. Instead, I say thank you and wish you good luck with your otherwise promising work :)

[cmather]

No worries. Yeah I had to change the params=this to accommodate blaze in
Meteor core. It was a change they made to how data contexts are handled.

On Fri, Mar 21, 2014 at 1:31 PM, PeppeL-G notifications@github.com wrote:

Thanks for your time, it's very appreciated!

I did found the helper (in lib/client/ui/helpers.js), and it turned out
I'll have to change all my {{pathFor 'routeName'}} to {{pathFor
'routeName' params=this}}. Unless it is I who use the helper wrong, this
seems like an unnecessary detour to me, but let us not discuss an
iron-router matter in the blaze-layout anymore. Instead, I say thank you
and wish you good luck with your otherwise promising work :)

Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-38320690
.

[tsega]

@cmather thanks for the prompt response and removing blaze-layout does the trick. @PeppeL-G my regular iron-route routes, {{pathFor 'routeName'}}, work perfectly. I'm going to close this issue, since like you mentioned, this is not a blaze-layout issue. Thanks for the help guys.