Developer forum

Forum » Dynamicweb 10 » Creating content from Front-end

Creating content from Front-end

Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply

Hi guys,

I have a situation in one of our project related to the ability to create content from front-end.

My understanding is that Item Creator and Item Publisher are deprecated in DW10.

For the purpose of creating content from front-end, can I use the Management API? Or any other API?

Would the Management API help me create the interface for adding the content (fields, field types etc)?

It would be very useful if there is a place where this part is documented.

Thank you,
Adrian


Replies

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

Hi Adrian

Item publisher still exists - item creator does not.

Item creator had a number of issues - first of all security issue, second it was relatively tightly connected to backend features of DW9 which do not exist in DW10. So if we will add that module back, it would be somewhat different.

You can use the management API to create content from the frontend - but it would be a security issue. The management API requires that you use an API key and you do not want to expose that in your frontend as the API key could be used to all kind of things on the management API.

Instead you could take one of these approaches

  • Create the items using code in a .cshtml template
  • Create a custom module for DW10 by implementing ContentModuleBaseAddIn for an item creator (we can help you on the way, and provide the code from the old creator module)
  • Use a template for the frontend form and either middleware or a notification subscriber to catch the form post and

What kind of content do you need to create?

 
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply

Hi Nicolai,

Thank you for the reply.

In my situation, I need to build a community in DW. We already have the users, and the forum but we need to allow the members also to create some content.

News, Partner profile, Solution description, etc. The content will not be just a simple HTML, it may have multiple fields where we need to store data for filtering, grouping, etc.

Option 3 from your suggestions was our alternative to Management API but I would like to explore more Option 2. It seems more robust and potentially reusable.

How do you suggest we should approach it? Where do we start from?

Thank you,
Adrian

 

 

You must be logged in to post in the forum