Help us test 1.0.1 RC

Quote from: rthrash at Oct 20, 2009, 09:24 AM

@mm_rules for ManagerManager
For the demo content, I propose the following that I think would make the most sense:

[*] Remove the mm_rules.inc.php from the filesystem
[*] Create a mm_rules chunk with the demo content for the installer. This way it can be selectively installed and shouldn’t confuse people due to it’s inclusion on the filesystem and always applying. Tweak the config file for the MM install header to point to the new chunk (/me makes note to allow for multiple configurations for each Element in Evo for future installer by supporting multiple @internal @properties headers that get parsed into radio options, with the first one being the default)
[*] Tweak the rules a tiny bit more for the demo content. Probably create an editor role with limited permissions for such (pulled from original 1.0 branch work). Lots of feedback wanted here!

I’d suggest keeping mm_rules.inc.php in the filesystem, but only containing comments saying "Enter rules here" and maybe a note that you have the option to enter them in a chunk instead. There could be similar content in the default chunk.

With your suggestion, when a users installs and opts NOT to install demo content, would an empty chunk be created?

Quote from: mmjaeger at Oct 20, 2009, 08:28 PM

Hello
there seem to be some issues when creating a weblink - when changing the template while adding the link, the page reloads and it then also opens a resource field with tinyMCE.

Saving and reloading the page shows the link in the content field? Browsing thru the database, I don’t see how I could distinguish a weblink from a document - the contentType shows them as "document" as well.

Am I missing something here?

Nobody else experiencing the same issue with weblinks??

Quote from: mmjaeger

there seem to be some issues when creating a weblink - when changing the template while adding the link, the page reloads and it then also opens a resource field with tinyMCE.

Saving and reloading the page shows the link in the content field? Browsing thru the database, I don’t see how I could distinguish a weblink from a document - the contentType shows them as "document" as well.

Am I missing something here?

Good catch Marco. The Content Type on the second tab, needs to also be set to Weblink from web page when creating a new Resource from the weblink button. Bug report filed in JIRA: http://svn.modxcms.com/jira/browse/MODX-1301

Quote from: ncrossland at Oct 21, 2009, 02:59 AM

With your suggestion, when a users installs and opts NOT to install demo content, would an empty chunk be created?

No they would have the option to install it in the manager still. We’ll need to work on optional config settings in the installer in a future release. Dependencies can get crazy! For the time being, it’ll install MM with the config set for the chunk. It still works if it can’t find the chunk so there shouldn’t be an issue (but it’d probably be good to log to the System Events table in this case).

I got an obstacle with ModX built-in database dumping.
I believe it’s connected with chars escaping.
Is it possible to update the current core (MySQLdumper version 1.0) with the newest one (ver. 1.24)?
Or even better, build it with phpMyAdmin scripts?

btw,
In Manager Page, each time i click the document, the right frame goes to Edit Mode, not General < Page Data.
Is it default way?

Quote from: goldsky at Oct 21, 2009, 10:00 PM

I got an obstacle with ModX built-in database dumping.
I believe it’s connected with chars escaping.
Is it possible to update the current core (MySQLdumper version 1.0) with the newest one (ver. 1.24)?
Or even better, build it with phpMyAdmin scripts?

Sure. Submit a patch to JIRA and we’ll review it for inclusion in a future release.

Quote from: goldsky at Oct 21, 2009, 11:27 PM

In Manager Page, each time i click the document, the right frame goes to Edit Mode, not General < Page Data.
Is it default way?

Yes this is the default action now, coinciding with the behavior in Revo.

Hi here are a couple of bugs and some suggestions that I think would make it a better release. Hope it is some help.

This is out just a little bit in Safari. The check image on the "Edit Resource" button is down to low by 3px and can be fixed by changing the top margin from "” to "" found in > 1.0.1 > assets > plugins > qm > css > style.css : r5795 Line 92

This is a feature request for QM Editor. Auto Hide would be nice to have on the qm toolbar.

1.0.1 > assets > plugins > qm > css > style.css : r5795 Lines 1, 44
the auto hide can be enabled by adding “top: -30px;" to “#qmEditor, #qmEditorClosed" to hide it except for about 3px and to “#qmEditor:hover, #qmEditorClosed:hover” "top: 0px;"


1.0.1 > assets > plugins > qm > css > style.css : r5795 Lines 1, 44
if we add "-webkit-transition-duration: 1.5s;" to "#qmEditor, #qmEditorClosed" there will be a slower transition when hover is removed and if we add "-webkit-transition-duration: 0.5s;" to "#qmEditor:hover, #qmEditorClosed:hover" it will drop down faster so it can quickly accessed if using a webkit based browser. (I have been doing this manually to my sites and I think it would be appreciated by other users.)

and to finish one last bug that was mentioned earlier. I have tested it and it fixes the problem mentioned here. (http://modxcms.com/forums/index.php/topic,41069.msg247872.html#msg247872 )
1.0.1 > install > assets > snippets > weblogin.tpl : r5819 Line 3 needs to be changed from "Weblogin" to “WebLogin”

Thanks Cameron

Quote from: rthrash at Oct 22, 2009, 03:51 AM

Sure. Submit a patch to JIRA and we’ll review it for inclusion in a future release.

done, thx.
http://svn.modxcms.com/jira/browse/EXT-21