 September 24, 2007 - 11:28am | also, what about have a Document exist in TWO (or moore) projects? for example: Laser Pistol document could be in : Remastered OCS 25th Ani get the point? I'm saying if the information is the same why duplicate it.  |
September 24, 2007 - 11:35am | Just to be clear, I'm talking about transferring (not duplicating) whole pages, and w00t would like to be able to use the same pages for two projects without duplication. |
 September 25, 2007 - 8:25pm | I understand what you're both asking. w00t - I'm not sure how to facilitate that. A document can only have one "Parent Node" in Drupal. Making one have multiple parents doesn't seem completely doable. I was initially thinking about making a tag that could be used, such as <<insertnode,123>> or something similar. Then the original node would be copied into the place provided by the tag. But my tag parser couldn't parse that inner section (I tried this), resulting in some odd effects. I'll see what I can do about this, but I'm not promising the ability to ape content among multiple projects.Corjay - this is actually possible now, but only with siteref permission status. It's something I could do for you fairly easily. I didn't provide this tool to the masses because it doesn't filter out those projects to which you lack edit permission. If you want to know how you, too, can do this feature, PM me and I'll let you know a way. 3. We wear sungoggles during the day. Not because the sun affects our
vision, but when you're cool like us the sun shines all the time. |
September 25, 2007 - 11:35pm | I have a solution for both your requests. Project Managers can now reposition document pages (along with any subordinate pages) among any/all projects they manage. This is done using the more advanced Outline utility I gave ya... just click "Reposition" like you would have if you were repositioning within the same design document hierarchy. There will be two options located at the top of the page - the traditional "Repositioning" section and a new "Transfer" section, which will allow you to transfer the page (along with subordinates) to the top level of any other project you manage. If you don't manage it you can't transfer into it. This option will only show up to a manager of a project's documents. As to the second option, I created a new tag called simply: <<node,123>> Inserting a tag like that will insert the body of the contents of any other design document. Some managers won't want their material duplicated. If you want to allow others to reference your design documents in a project you manage, edit your project settings to allow "Node Referencing". If you don't allow node referencing, then all users will see when that tag is used will be a link to the page. If referencing is allowed, users will see the entire document page along with links to the project and that project's manager. You'll have to try it to see what I mean. 3. We wear sungoggles during the day. Not because the sun affects our
vision, but when you're cool like us the sun shines all the time. |
