We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 33337
    • 3,975 Posts
    Quote from: rthrash at Mar 17, 2006, 02:14 AM

    I love it Zi... much better and committed already. smiley

    Thank you! cool
      Zaigham R - MODX Professional | Skype | Email | Twitter

      Digging the interwebs for #MODX gems and bringing it to you. modx.link
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      <p>It seems you haven't installed MODx yet, because MODx couldn't found the configuration file.</p>


      Tsk. That should be "couldn’t find the configuration file".
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 25663 MODX Staff
        • 12,272 Posts
        Or as it is as committed:

        It seems MODx is not currently installed, or the configuration file cannot be found.
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 18397
          • 3,250 Posts
          "It seems you haven’t installed MODx yet, because MODx couldn’t found the configuration file.

          Install Now!"

          Shouldn’t that be

          "It seems you haven’t installed MODx yet, because MODx couldn’t find the configuration file.

          Install Now!"

          Also, maybe a sans-serif font might look better since it matches the manager more?
            • 7455
            • 2,204 Posts
            Great work was gone for a week but wil start testing this new release and let you know
              follow me on twitter: @dimmy01
              • 25663 MODX Staff
              • 12,272 Posts
              Just posted the fourth test build including Banzai’s manager.

              After installing and a quick run through, and fixing two small bugs, most things look pretty good except the editing or creating new content pages... they’re a slight mess. There’s also missing icons and a few icons that don’t quite match as well scattered about, but a very respectable first stab at it.

              The installer sql definitely needs to be updated to adjust for the different manager layouts, etc, now, so plan on making a manual change at first.


                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 6726
                • 7,075 Posts
                Great !

                Donwloaded and off to test it this week-end !!

                This will be an exciting release grin
                  .: COO - Commerce Guys - Community Driven Innovation :.


                  MODx est l&#39;outil id
                  • 25663 MODX Staff
                  • 12,272 Posts
                  Please keep in mind that banzai’s manager template is very rough still, but the hard work is done. I’m amazed that it now renders (almost) everything with a completely different image and css path structure. The cleanups and details are easy to fix.

                  With that said, though, if anyone can help on the Pop-up tree, that would be tremendous. It’s not quite as straightforward.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 25663 MODX Staff
                    • 12,272 Posts
                    I’ve found the function that is causing the failure of the icons on the context-menu to fail:
                    <?php
                    if(IN_MANAGER_MODE!="true") die("<b>INCLUDE_ORDERING_ERROR</b><br /><br />Please use the MODx Content Manager instead of accessing this file directly.");
                    function constructLink($action, $img, $text, $allowed) {
                    	if($allowed==1) {
                    ?>
                    <link rel="stylesheet" type="text/css" href="media/style/<?php echo $manager_theme ? "$manager_theme/":""; ?>contextMenu.css<?php echo "?$theme_refresher";?>" />
                    <div class="menuLink" onmouseover="this.className='menuLinkOver';" onmouseout="this.className='menuLink';" onclick="this.className='menuLink'; parent.menuHandler(<?php echo $action ; ?>); parent.hideMenu();">
                    	<img src='media/style/<?php echo $manager_theme ? "$manager_theme/":""; ?>images/icons/<?php echo $img; ?>.gif' align=absmiddle><?php echo $text; ?>
                    </div>
                    <?php
                    	} else {
                    ?>
                    <div class="menuLinkDisabled">
                    	<img src='media/style/<?php echo $manager_theme ? "$manager_theme/":""; ?>images/icons/<?php echo $img; ?>.gif' align=absmiddle><?php echo $text; ?>
                    </div>
                    <?php
                    	}
                    }
                    
                    ?>


                    The part in particular that is weird is that the $manager_theme variable works in the stylesheet context, but not in the actual links being built. Very odd.

                    Also, since the following constuct(?) is used over and over again, isn’t there a simpler way where we could just declare a single variable at the top rather than repeating that over and over again?

                    <?php echo $manager_theme ? "$manager_theme/":""; ?>


                    My thought is assigning it as a variable at the top of relevant pages and then using it inline as appropriate via {$varname} if that would work... will it? My coding skills aren’t a bit rusty; they’re virtually nonexistant.
                      Ryan Thrash, MODX Co-Founder
                      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                      • 22303 MODX Staff
                      • 10,725 Posts
                      The $manager_theme_path should probably simply be set as a configuration option or a ManagerAPI function, then read from the $modx->config object or directly from $modx->manager->getThemePath() respectively. In fact, $manager_theme should already be in the config object, right?