The approach as was step by step built with your opinion looks very correct and challenging. But finally how should I use Upload Control. Is there existing any Upload Control for a paragraph or should I implement myself reusing the Control Upload from the dialogs?
A. On Wed, Nov 5, 2008 at 1:32 PM, Will Scheidegger <[email protected]> wrote: > And when it comes to pushing data from public to the author instance (just > because Rainer said that the public instance should not contain data the > author instance does not have), I can recommend the use of the observation > module! Simply set it up to observe added or modified nodes in this part of > the public dms and then trigger an action upon these changes. > > -will > > P.S.: Congratulations to the creator of this module. Excellent work! > > On 05.11.2008, at 13:14, Jackson Nicolas wrote: > >> If your goal is to store into the DMS, it's not difficult at all. The >> same way the author adds information into the website repository, you >> can have the public add information to your DMS. It's just not common >> practice, that's all. >> >> So here's the steps I would follow: >> >> Create a form accessible to the target user >> Process the form and collect the content and file >> Save as a Document in the DMS >> >> Cool? >> >> On Wed, Nov 5, 2008 at 3:58 AM, Adrian Butnaru >> <[email protected]> wrote: >>> >>> It sounds quite logical what you guys both say. What actually I want >>> to do is a Form page where users can fill in information about >>> projects, upload at the end some files containing project reports and >>> than submit all the data. After Submit I want to collect these files >>> and the content of all the other fields in a database. That is all. I >>> thought I could easily store the uploaded files into the DMS. But it >>> looks that it would be wiser to store all in a new repository. >>> >>> On Wed, Nov 5, 2008 at 11:47 AM, Matteo Pelucco >>> <[email protected]> wrote: >>>> >>>> rainer ha scritto: >>>> >>>>> I wouldnt do that because: >>>>> If you do so, your author and publish instance will have stored >>>>> different >>>>> data. And the general magnolia concept is to: >>>>> 1. upload on author instance 2. activate the uploaded stuff to public >>>>> >>>> >>>> And what do you think about this scenario: >>>> >>>> 1. user upload a file into public instance without storing into the >>>> local >>>> repository. >>>> 2. a custom filter / control do the staff to send the file back to >>>> author >>>> instance AND start a workflow. >>>> 3. At this point a custom authentication should be provided, to avoid >>>> permission issues. >>>> 4. a "superuser" approve or reject the document answering to the >>>> workflow >>>> engine >>>> 5. workflow end with short-circuit the route back to public instance, >>>> with >>>> "publication" (if approved) or deleting the document (if rejected). >>>> >>>> >>>> can this be a solution? >>>> this can also be useful if you have several public instances... >>>> >>>> Matteo >>>> >>>> >>>> ---------------------------------------------------------------- >>>> for list details see >>>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>>> ---------------------------------------------------------------- >>>> >>> >>> ---------------------------------------------------------------- >>> for list details see >>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>> ---------------------------------------------------------------- >>> >> >> ---------------------------------------------------------------- >> for list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > for list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://www.magnolia-cms.com/home/community/mailing-lists.html ----------------------------------------------------------------
