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.

Debugging 2.2.2 without debugging tools

August 03, 2011 10:09pm

Subscribe [3]
  • #1 / Aug 03, 2011 10:09pm

    dclarkrenton

    25 posts

    I updated my MSM site yesterday to 2.2.2 and at first, it looked like it went over without a hitch….

    Yet (in Site 5) when visiting Output and Debugging Page, I turned on the Template Display Debugging… and absolutely ‘no Template Display’ details show up.

    Looks like I am not/cannot log in from the outside? Keep getting 404s after I enter my log in info… Even though, I am logged into the CP as Super Admin.

    But wait…  appears I am logged in one site (Site #1)... so templates parsing shows up there. No dice on Sites 2, 4, 5.. (Site 3 was deleted).

    All have identical security and sessions configs.. and template parsing display worked before the update.

    Do I have to set up my access to the CP local to each site… cause I have kept my old CP URL alive (in all for site instances) and not switched to the admin.php regime yet…

    Any ideas?

  • #2 / Aug 04, 2011 11:37am

    Sue Crocker

    26054 posts

    Hi, dclarkrenton -

    You’d need to have cookies set for those additional sites, there were some changes made for MSM during this release.

    You do need to have updated the index.php and admin.php for each MSM site - did you remember to do so?

  • #3 / Aug 04, 2011 12:50pm

    dclarkrenton

    25 posts

    Thanks Sue… but DID all that (including cookie set(s) and even $config[‘multi_login_sites’]), and still did not resolve issues.

    Even more perplexing is that one of the sites is set to be offline… And even though I am logged into the CP as a SuperAdmin and can view and configure all sites… When I go to the site that is set to offline (viewable only by SuperAdmins).... I’m served the offline page (and can’t get in, even with member/login added to path).

    Very weird and difficult to remedy!

  • #4 / Aug 05, 2011 4:16pm

    Sue Crocker

    26054 posts

    So if you visit http://site2/admin.php, which will put you into the control panel, and if you make sure you are in the right site, and then attempt to visit the site, you’re still having problems?

  • #5 / Aug 09, 2011 12:06pm

    dclarkrenton

    25 posts

    As mentioned, I am using the config variable:
    $config[‘multi_login_sites’] = “https://siteone.com/index.php|http://sitetwo.com/index.php|http://sitethree.com/index.php|http://sitefour.com/index.php”;

    I now find it impossible to use the non-cloaked login, as these (new configured on any login) cookies prevent me from using the old login page. FWIW, is at: https://primarysite.com/system/

    I was using Google Chrome which appeared to have/be the issue (even with cookies cleared), at least that’s what I thought at first.

    When I use (cookies cleared) Safari, and log into say SiteTwo of the above (using admin.php) instead… it sets new login cookies correctly for all the domains, as I have configured (under Cookies). So now I am able to view the offline (SiteTwo) site as intended, in addition to any template parsing when turned on…  I can also view and configure any site, from any CP login domain.

    Bad news is that, it has totally broken my public view of the other three sites where the cookies were set by the first CP admin login.

    I tested with all four site domain cookies cleaned out, logged to CP of Site Two, Set template parsing as ON of Site Three and tried to view Template parsing of Site Three in a browser… Broken in Safari, but only the public site (no template parsing) is still visible in Chrome.

    To SET Cookies or NOT is now the issue, I think.

    Lastly, is there currently a way to just login to one primary domain for all CP users to configure all MSM sites, where it won’t interrupt public viewing of any site(s)? I was using my old CP login path to the system folder, yet I auto placed the admin.php file in all MSM sites too.. It was working till update to 2.2.2… After that, viewing parsing details on public pages and now the front pages themselves are having issues…

    IOW, is there a best practice for singular CP login configuration (for all sites), that maintain permissions for all public sites, with new security implementations in 2.2.2?

  • #6 / Aug 11, 2011 4:31pm

    Sue Crocker

    26054 posts

    All great questions, let me ask the dev team. I know there were some changes made in the past few releases to MSM, and there may still be a few minor buglets lingering.

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

ExpressionEngine News!

#eecms, #events, #releases