Hi Tomas,
We've done that kind of functionality with custom page for non editors (and NO, it is not using Episerver edit mode functionality like you ask).
Basically there was title field, content field and possibility to upload image. Then this information is submitted to server (API controller handless the post) and Episerver page is created programmatically and status set to 'ready for publish'. Image is stored to the pages 'For This Page' folder. Editors will check the page and publish it if everything is fine.
If you can't give limited access to Episerver edit mode to the intranet users (they could only have access to the news section and no publishing rights) then I would go with the above solution.
If it's an intranet then potentially the users can be authenticated via AD or similar and given basic authoring control to only the news items?
Antti, thanks for the feedback.
The users are suppose to upload images and documents but allso create links to existing global files and pages. To use the built in functionallity would save a lot of time instead of creating this ourselfes.
Janaku, to use the built in functionality is not on the table at this time.
I would agree then with Antti. One other thing you might want to consider is using either Content approvals or Notifications API to notify a group of users who need to review the content once it's created.
Hi,
We are working on a intranet solution where the users are allowed to create news pages. The form should be in the public pages and not in edit mode. The gui should look like the "all propertis" view in edit mode. Is it posible to render the properties this way? We allso like to use the build in link dialog and MainBody with TinyMCE.