My 0.9.7 experience

First, to recap installation and startup procedure:

1. Edit the _build/build.config.sample.php file, set the proper values for the database connection. Save as build.config.php

2. from the command line, cd to the _build folder and run "php transport.core.php"

3. from the browser open the site and install.

4. log in, and in the Manager home page click on the Resources link.

5. from the "new" dropdown select "Template" and create a template. Upload support files (css, images, etc) to the /assets/templates folder to correspond to the paths in your template file.

6. create a document.

A few minor differences in the Manager interface. There is no "Resources" item in the main menu, so I used the Resources link on the "My Modx Site" tab to access them. The "New" menu item in place of a "new" link on the page gave me pause for a bit, but once I clicked around on things I found it.

it’s very slow; I’m not complaining since it’s alpha, just noting it.

Now to go find the new tags syntax!

For the new Tag syntax, please see: http://modxcms.com/roadmap

Google was my friend; I got that link about 10 minutes ago!

Also discovered the "Elements" tab at the bottom of the document tree; I suppose that can no longer be called "document tree" since it now displays other ...er elements!

Templates worked fine, but when trying to check out the Snippets (Ditto and Wayfinder, which I installed at installation) it gives this error:

Fatal error: Call to undefined method modX::dbQuery() in /Applications/MAMP/htdocs/0.9.7-2928/manager/controllers/element/snippet/update.php on line 36

All other elements views work fine; TVs don’t work at all, but I seem to recall reading something about that; after all, this is alpha. At least the TV view itself works.

Get the same error if I go to the Snippets tab from the Resources link on the Manager home page.

Wayfinder snippet isn’t working, wonder if that has anything to do with the inability to view existing or save new snippets?

Checking the database, the new snippet is in fact saved to the database. Still get that same error though.

The new snippet works just fine.

Quote from: sottwell at Sep 18, 2007, 01:56 AM

A few minor differences in the Manager interface. There is no "Resources" item in the main menu, so I used the Resources link on the "My Modx Site" tab to access them. The "New" menu item in place of a "new" link on the page gave me pause for a bit, but once I clicked around on things I found it.

As it seems you found in a later post, the Elements tree is kind of replacing the Resources page. We found it to be a bit more intuitive for browsing all your Elements and such.

it’s very slow; I’m not complaining since it’s alpha, just noting it.

Speed-wise or process? If the speed is slow - are you running Firebug? FB makes Ext run ridiculously slow. If it’s process, then your experience is invaluable, and we’ll try to streamline the UI more to make for an easier environment.

Quote from: sottwell at Sep 18, 2007, 02:25 AM

Templates worked fine, but when trying to check out the Snippets (Ditto and Wayfinder, which I installed at installation) it gives this error:

Fatal error: Call to undefined method modX::dbQuery() in /Applications/MAMP/htdocs/0.9.7-2928/manager/controllers/element/snippet/update.php on line 36

All other elements views work fine; TVs don’t work at all, but I seem to recall reading something about that; after all, this is alpha. At least the TV view itself works.
Get the same error if I go to the Snippets tab from the Resources link on the Manager home page.

Snippets probably wont work for a bit, since they’re all coded in legacy 096 code, rather than the new 097 codebase.

Quote from: sottwell at Sep 18, 2007, 02:47 AM

Wayfinder snippet isn’t working, wonder if that has anything to do with the inability to view existing or save new snippets?

I’ve committed a temporary fix this morning for the Update Snippet page - it had to do with module dependencies. Update your SVN to get the fix. We’re still deciding on what to do with modules and how to handle them in 097.

Speed-wise or process? If the speed is slow - are you running Firebug? FB makes Ext run ridiculously slow. If it’s process, then your experience is invaluable, and we’ll try to streamline the UI more to make for an easier environment.

Ah, yes, I am running firebug. I’ll check it out with Safari then.

It’s just fine in Safari, in fact maybe even a bit snappier than 0.9.6, or maybe it’s just that Safari is quicker; I seldom use it.

Quote from: splittingred at Sep 18, 2007, 07:54 AM

Snippets probably wont work for a bit, since they’re all coded in legacy 096 code, rather than the new 097 codebase.

I did add a "test" snippet that simply returned a string, and even though saving it produced the error i’ve mentioned, and I can’t open it for editing again, but the snippet was in the database and [[Test]] in my content did in fact product the string in the page. So I’ll update and hopefully that nasty error will go away.

Quote from: sottwell at Sep 18, 2007, 09:49 AM

Ah, yes, I am running firebug. I’ll check it out with Safari then.
It’s just fine in Safari, in fact maybe even a bit snappier than 0.9.6, or maybe it’s just that Safari is quicker; I seldom use it.

I recommend always keeping Firebug turned to ’off’, and enable it only for certain sites that you’re developing on. Firebug in general causes Firefox to balloon in memory, and makes overall running slower, because of all the checks and procedures that it does upon load.