MODx9.1 Todo

Are pages that are created, by say the newspublisher snippet, supposed to inherit the document groups of their immediate parent docs?

Answer: They don’t. I just filed a bug on this one, and it’s pretty critical for private sites I think:

This has major implications for private web apps created with MODx. Examples include private newsboards.

When creating documents inside a page that belongs to a webgroup, it’s parent groups are not automatically inherrited... they are publicly accessible by default. I believe the proper behavior is too inherrit the docgroups from the parent document.

Thoughts?

That sounds like a logical assumption to me. I can see certain circumstances where documents in a folder would want to have other groups, but it seems to me it would be a good default.

In fact, I just IM’ed my partner, who immediately responded that he would have assumed this to be the case.

Only one bug outstanding of note. Lots of little fixes committed in the interim too. The only thing outstanding is the apparent regClient stuff failure in cached snippet calls. Does anyone have a comment on that. In the interim, a new testing build in the other topic.

regClient scripts are only inserted before document is cached. Might need to also insert scripts again

I read what you said, but I don’t get it.

Go figure.

So is it a bug or not? 

It’s by design but can change to support non-cached snippets

Quote from: xwisdom at Dec 13, 2005, 07:45 PM

regClient scripts are only inserted before document is cached. Might need to also insert scripts again

Yea, I ran into this with QE and had to wirte my own code to handle post cache script additions. It would be nice to have this work either way.

I committed a fix for this tonight, btw.

Along these same lines, the css file insertion piggybacks off of the javascript insertion, thus getting installed at the beginning of the header. Very awkward in a "cascading" system, where the regular css in the main css file may very well override the css in the inserted file, while the whole point of the secondary file may have been to override some general style in the main css file. A secondary css file really needs to be inserted near the end of the header, after the main css file is called, maybe just before the </head> tag.