ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

development site msm settings

June 20, 2011 12:39pm

Subscribe [4]
  • #16 / Jun 28, 2011 3:34pm

    fin

    168 posts

    Hey Sue, no, I set up as the screen shot shows: /nfs/c06/h05/mnt/xxxxx/domains/dev.siteA.com/html/edit/default_site and /nfs/c06/h05/mnt/xxxxx/domains/dev.siteB.com/html/edit/stpete. Still the same issue. For some reason ee still isn’t distinguishing between the template groups and the templates in those groups in the url. I get http://example.com/index.php/template_grouptemplate/, not http://example.com/index.php/template_group/template/ ?
    If this is something within the db, ie template tables, please let advise me how I should troubleshoot that?
    june 29, mods any suggestions, thanks?

  • #17 / Jun 30, 2011 9:45am

    fin

    168 posts

    Anyway, since I haven’t heard from mods in a couple of days, I thought I might try updating to 2.2; however, I don’t how this update will work with MSM. With everything I tried, I have a feeling that MSM may have something to do with this current issue.  If anyone else has done the 2.2 update with MSM, please let me know what you’re experiences have been. Thanks.

  • #18 / Jun 30, 2011 3:38pm

    Brandon Jones

    5500 posts

    Hi fin,

    Sorry this is dragging on here. Updating to 2.2 would be recommended eventually, but I don’t think any of this is caused by a bug in 2.1.3. This thread is a little unclear since multiple issues were brought up, some already resolved.

    The main issue now is the missing slash in your URLs, correct? This is actually expected behavior, as EE 2.x doesn’t force a trailing slash like EE 1.x did, and this applies to {path=} variables as well. Adding the slashes to the links in your includes/mainNav template should do the trick. If I’m missing something else, let me know. Thanks for your patience, rest assured we won’t leave you hanging.

  • #19 / Jun 30, 2011 4:32pm

    fin

    168 posts

    Thanks Brandon,

    The main issue now is the missing slash in your URLs, correct?

    Yes, that is the problem. Sorry for the confusion. I should have started a new thread for this issue. I’ve made the following changes from the 1.x code. Here’s an example of the change I made to the links (Sorry, I had to remove the anchor tags to get this to render properly):

    {if segment_1=="news"}class="current"{/if} href="{path='news'}sports">sports
    {if segment_1=="news"}class="current"{/if} href="/news/sports/">sports


    Is this what your suggesting? If so, this has not fixed the issue.

  • #20 / Jun 30, 2011 5:23pm

    Brandon Jones

    5500 posts

    Hey fin,

    I should have been more precise. I meant placing the slash after the closing bracket of the path variable. The path variable only cares about the template group and template it’s being told to display. But placing the slash after the path variable will allow you to add more segments, like

    {if segment_1=="news"}class="current"{/if} href="{path='news'}/sports">sports

    EE 2.x just gives you a little more control here, and I actually find that easier to read. But, it is obviously a pain coming from 1.x. That should work for you.

    Regarding saving templates as files, I stuck a script called whereami.php on your “main” site; if you open it I left some notes in there for you. Basically, the template path just wasn’t correct. After correcting I synchronized templates on that site and it worked great. You shouldn’t have any problems doing the same for the other 2 sites.

    Let me know if this all works!

  • #21 / Jun 30, 2011 5:39pm

    fin

    168 posts

    Thanks Brandon, that should do it. Usually, I use that whereami file. I’ll never do another update without it. Anyway, thanks again. Now I can knock out the rest of this.

  • #22 / Jun 30, 2011 5:42pm

    Brandon Jones

    5500 posts

    Thanks for your patience, and I will leave this open in case you run into anything else. Let us know once you’re all set!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases