Hi Valentin

My guess here is that a MacroPartial is a special kind of Partial View in Umbraco, it can receive Parameter values entered by editors when the Macro is inserted, and to achieve this it must @inherits a specific Model:

@inherits Umbraco.Web.Macros.PartialViewMacroPage

But this then mucks up adding an MVC form like you are attempting here as you want the Model for this partial view to match your Form Fields eg

@model Umbraco.Model.ContactViewModel

But in a partial view you can only have one or the other!

The workaround therefore is to create a new 'normal' Partial View in your Views/Partials folder, called something like RenderContactForm.cshtml

Move your MVC form implementation into this Partial View with it's reference to your ContactViewModel at the top.

If you only need to render your form in a template then you do not need to use a Macro at all, you can just write:

@Html.Partial("/views/partials/RenderContactForm.cshtml", new ContactViewModel())

But if you do need a Macro, eg so editors can choose to add the Form in the grid or Rich Text Area, then create a separate Macro Partial and make sure it has

@inherits Umbraco.Web.Macros.PartialViewMacroPage

at the top...

and then all that Macro Partial needs to do is render the normal MVC partial view eg:

@Html.Partial("/views/partials/RenderContactForm.cshtml", new ContactViewModel())

regards

marc

Hi Valentin

That outter div with class umb-macro-holder is generated by the Macro Partial...

is the issue not having an @ before the using statement, and so the template 'doesn't know' to write out the form in the template eg:

@using (Html.BeginUmbracoForm<Umbraco.Controller.ContactController>("Submit")){
...

}

make any difference for you?

regards

Marc

Hi Valentin

I just had to try this out to confirm what might be going on!!

I'm using 8.7RC

I Create a Model:

namespace Umbraco_8_7_RC.Models
{
    public class ContactViewModel
    {
        public string Name { get; set; }
        public string Email { get; set; }
        public string Message { get; set; }
    }
}

and a Controller:

namespace Umbraco_8_7_RC.Controllers
{
    public class ContactController : SurfaceController
    {
        // GET: Contact
        public ActionResult Submit(ContactViewModel vm)
        {
            return View();
        }
    }
}

and a partial view:

@inherits UmbracoViewPage<Umbraco_8_7_RC.Models.ContactViewModel>

@using (Html.BeginUmbracoForm<Umbraco_8_7_RC.Controllers.ContactController>("Submit"))
{
    <div>
        <p>
            @Html.LabelFor(m => m.Name)
            @Html.TextBoxFor(m => m.Name)
            @Html.ValidationMessageFor(m => m.Name)
        </p>
    </div>
    <div>
        <p>
            @Html.LabelFor(m => m.Email)
            @Html.TextBoxFor(m => m.Email)
            @Html.ValidationMessageFor(m => m.Email)
        </p>
    </div>
    <div>
        <p>
            @Html.LabelFor(m => m.Message)
            @Html.TextAreaFor(m => m.Message)
            @Html.ValidationMessageFor(m => m.Message)
        </p>
    </div>

    <input type="submit" value="Send" /> <input type="reset" value="Reset" />
    <p>
        <div class="g-recaptcha" data-sitekey="6LexiiETAAAAAMcC8Fjj72f3MPJmgi3Kxmil8D8v"></div>
    </p>
}

and then a Macro Partial:

@inherits Umbraco.Web.Macros.PartialViewMacroPage

   @Html.Partial("~/Views/Partials/Contact.cshtml",new Umbraco_8_7_RC.Models.ContactViewModel())

When I use either a grid or a rich text area, and choose to insert the contact form macro, and publish, then ...

I get the form fields in the backoffice AND on the frontend...

So you can see from my example, it's really similar to what you have!

The only difference perhaps that I'm using @Inherits instead of @model at the top of the partial view? and that my models arent' coming from a namespace with the name 'Umbraco' - could that be conflicting?

But sure is strange!

Hi again Marc

Right now I am running Umbraco 8.6.4. Maybe I should try to upgrade it to V8.7?

Now I have upgraded my website to V8.7, but I still have the same problem.

is working on a reply...