Help us test 1.0.1 RC

hi, I did a fresh 1.0.1 install with "install sample website", so far everything worked nicely except i had to rename the Weblogin call from WebLogin to Weblogin.

one feature i love is the documentTags TV (text) with a choice of red words. could somebody explain how this is done?

also the "Send the new password by e-mail." is fixed which is really cool. thanks guys for this!!!!

The Tags bit is the ManagerManager tagging widget (red words).

ah cool, i thought it was ManagerManager, but I really have a hard time where the tags are defined. Could you point to where "demo howto miniblog older posting tutorial" is specified?

Show Image TVs (imageTVpreview) still present in distributive. It has been deprecated or not?

After MODx install, plugins don’t have comments with events. No problem if you use fresh install, but otherwise you can’t check is events checked on the right checkboxes. Same for properties.

In demo content chunks: footer, meta, styles are in Login group. MODxHost template too. I think that they can be in one Template group, with MODxHost and navigation chunks.

Quote from: Paprikas at Oct 19, 2009, 12:34 PM

Show Image TVs (imageTVpreview) still present in distributive. It has been deprecated or not?

Not in the current SVN branch for 1.0.1, though. We’ve got the deprecation bits handed there too for disabling it if it’s installed on upgrades.

After MODx install, plugins don’t have comments with events. No problem if you use fresh install, but otherwise you can’t check is events checked on the right checkboxes. Same for properties.

Do you mean that stripping the initial comments in the header out when installing causes the problems? Are upgrades not applying the events/properties?

In demo content chunks: footer, meta, styles are in Login group. MODxHost template too. I think that they can be in one Template group, with MODxHost and navigation chunks.

Thanks for the sharp eye, and please log that one in JIRA if you don’t mind.

Quote from: eerne at Oct 19, 2009, 10:25 AM

ah cool, i thought it was ManagerManager, but I really have a hard time where the tags are defined. Could you point to where "demo howto miniblog older posting tutorial" is specified?

Those are the values that are in the demo content. The delimiter is set to a space.

Quote from: rthrash at Oct 19, 2009, 06:36 PM

After MODx install, plugins don’t have comments with events. No problem if you use fresh install, but otherwise you can’t check is events checked on the right checkboxes. Same for properties.

Do you mean that stripping the initial comments in the header out when installing causes the problems? Are upgrades not applying the events/properties?

I don’t have any problems. But if in some case you uncheck some events and will forget about it, you need to have a MODx distributive to restore events (look at comments, and manually check them)
Actually it’s not pain for me. But in future would be great to see button ’reload events and settings’.

Quote from: rthrash at Oct 19, 2009, 06:36 PM

In demo content chunks: footer, meta, styles are in Login group. MODxHost template too. I think that they can be in one Template group, with MODxHost and navigation chunks.

Thanks for the sharp eye, and please log that one in JIRA if you don’t mind.

done

Quote from: rthrash at Oct 19, 2009, 06:37 PM

Quote from: eerne at Oct 19, 2009, 10:25 AM

ah cool, i thought it was ManagerManager, but I really have a hard time where the tags are defined. Could you point to where "demo howto miniblog older posting tutorial" is specified?

Those are the values that are in the demo content. The delimiter is set to a space.

wow that’s a really cool widget.

@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!

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?