<![CDATA[ MODX3 first impressions - My Forums]]> https://forums.modx.com/thread/?thread=104043 <![CDATA[MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559533 BobRay Jul 13, 2018, 08:53 AM https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559533 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559728
In fact, I think if you ran this script after putting the files in place, Setup would no longer ask you where the core is:

$rootCoreConfig = MODX_BASE_PATH . 'config.core.php';

if (file_exists($rootCoreConfig)) {
   $newStr = "define('MODX_SETUP_KEY', '@traditional@');\n?>";
   $content = file_get_contents($rootCoreConfig);
   if (strpos($content, 'MODX_SETUP_KEY') === false) {
        if (strpos($content, '?>') !== false) {
            $content = str_replace('?>', $newStr, $content);
        } else {
            $content .= "\n" . $newStr;
        }
        file_put_contents(MODX_BASE_PATH . 'setup/includes/config.core.php', $content);
   }
}


If you download the advanced distribution, I assume that you'd want to change @traditional@ to @advanced@.

]]> BobRay Jul 19, 2018, 10:26 PM https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559728 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559727 Quote from: BobRay at Jul 16, 2018, 08:30 PM
There's also no excuse for Setup asking you where the core is during an update -- there are three different config.core.php files it could check.

Yes, it baffles me why setup doesn't see where the core is in custom setups. It makes me go and find where I put that folder, and what it's named, for each site (since I don't do them all the same way). It's a big waste of time.]]> rainbowtiger Jul 19, 2018, 09:18 PM https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559727 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559691 Quote from: raffenberg at Jul 16, 2018, 08:12 AM
It was discussed a lot to have the upgrade in the core. Conclusion always was to have it not in the core. The profit is to have a more maintainable core. As it is with different other extras, it would be helpful for new users if they know about them. I see the startpage after succesfull installation as a possible place to give users a hint about them.

Yes 100% yes, the startpage but also the basic manager view needs to finally be a development center not a bug-fixing report.

Extras need to be right. There. Hot ones, basic ones, new ones. 1000%

Advanced users can always modify what they want to see, and they don't need the dash to the extent that new users do.

Or they spend 6 months figuring it out! Trust me I know!! :'(

What are the 5 most basic things we need people to know, once install is complete? 10 things perhaps]]> nuan88 Jul 18, 2018, 10:49 PM https://forums.modx.com/thread/104043/modx3-first-impressions?page=3#dis-post-559691 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559686 is a bad practice.]]> BobRay Jul 18, 2018, 10:14 PM https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559686 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559672 https://github.com/modxcms/mab-recommendations/blob/master/06-restful-api-move-from-extjs.md]]> markh Jul 18, 2018, 12:03 PM https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559672 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559662

Somehow, WordPress has managed to do it for years.]]> BobRay Jul 18, 2018, 06:58 AM https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559662 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559646 Quote from: BobRay at Jul 16, 2018, 08:30 PM
This could be done with a self-contained widget. Yes, it would have to be modified if and when MODX changes the location of the downloads or stops tagging versions at GitHub, but that's no reason to make users do a manual upgrade in 2018 (especially with a moved/renamed core). There's also no excuse for Setup asking you where the core is during an update -- there are three different config.core.php files it could check. In fact, what UpgradeMODX does now is just copy the root config.core.php file to the setup directory (with a small mod to keep setup happy).

Don't get me wrong, i just repeated the conclusion from several discussions over on slack.]]> raffenberg Jul 17, 2018, 09:26 AM https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559646 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559644 Quote from: jonleverrier at Jul 16, 2018, 09:36 AM

...
We love MODX because it's agnostic (it doesn't dictate how to manage content) and gives you the freedom to change what you want - this particular design update to resources goes against those founding principles.

As an example, I customise the manager so that all unnecessary clutter and fuzz is removed from content editors, so that they can focus on what they do best...generating and editing content.

So in this scenario, when looking at the 3 new side panel regions, I would only have 2 bits of data displayed ("published" and "hide from menus") out of the 9 pieces of new functionality on display, this seems like a great waste of space I can't get rid of.

I don't want to be branded as holding the project back, or not wanting a new modern manager. I'm simply providing feedback and some solutions. I'm all for the new layout if that appeals to the masses, but please give us the tools, through form customisation, to change the layout back if we need todo so. For example;

  1. Allow us to move the content field out of the document summary into it's own space
  2. Allow us to move publishing, template, behaviour in menu panels into tabs or different regions
  3. Allow the document summary to go full width if we hide publishing, template, behaviour in menu panels into tabs

If you have an opinion about this, I encourage you to leave a comment with a solution:
https://github.com/modxcms/revolution/issues/13968

I love this! Thanks for describing Creative Freedom.]]> mrhaw Jul 17, 2018, 05:18 AM https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559644 <![CDATA[Re: MODX3 first impressions]]> https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559636 Quote from: raffenberg at Jul 16, 2018, 08:12 AM
It was discussed a lot to have the upgrade in the core. Conclusion always was to have it not in the core. The profit is to have a more maintainable core. As it is with different other extras, it would be helpful for new users if they know about them. I see the startpage after succesfull installation as a possible place to give users a hint about them.

This could be done with a self-contained widget. Yes, it would have to be modified if and when MODX changes the location of the downloads or stops tagging versions at GitHub, but that's no reason to make users do a manual upgrade in 2018 (especially with a moved/renamed core). There's also no excuse for Setup asking you where the core is during an update -- there are three different config.core.php files it could check. In fact, what UpgradeMODX does now is just copy the root config.core.php file to the setup directory (with a small mod to keep setup happy).]]> BobRay Jul 16, 2018, 08:30 PM https://forums.modx.com/thread/104043/modx3-first-impressions?page=2#dis-post-559636