'perch_' Added to Input Name When Using $Form->receive_from_template_fields()

Thanks - that's what I thought. I'm using the same template for the front end (via the customer-facing website) and the backend within Perch. The frontend works fine (stripping perch_ from the input name and saving the data correctly) but the inputs for Administrators retain perch_.

Can you spot anything in my edit.pre.php or edit.post.php which would cause this...

edit.pre.php:

$Things = new BusinessListings_Businesses($API);

$HTML     = $API->get('HTML');
$Form     = $API->get('Form');
$Text     = $API->get('Text');
$Template = $API->get('Template');

// Load master template
$Template->set('businesslistings/my_listing.html', 'input');

$Form->set_required_fields_from_template($Template);

$result = false;
$message = false;

//check to see if we have an ID on the QueryString
//If yes, this is an edit. Get the object and turn it into an array
$thingID = (int) $_GET['id'];    
$Thing = $Things->find($thingID, true);
$details = $Thing->to_array();
$heading1 = 'Edit Listing';

if ($Form->submitted()) {

    $data = $Form->receive_from_template_fields($Template, $details, $Things, $Thing);

    //if we have a Thing update it
    if (is_object($Thing)) {
        $result = $Thing->update($data);
    }

    if ($result) {
        $message = $HTML->success_message('Your thing has been successfully updated. Return to %sthing listing%s', '<a href="'.$API->app_path() .'">', '</a>');  
    }else{
        $message = $HTML->failure_message('Sorry, that thing could not be updated.');
    }

    if (is_object($Thing)) {
        $details = $Thing->to_array();
    }else{
        $details = array();
    }

}

edit.post.php

# Side panel
echo $HTML->side_panel_start();

echo $HTML->side_panel_end();


# Main panel
echo $HTML->main_panel_start();
include('_subnav.php');

echo $HTML->heading1($heading1);

if ($message) echo $message; 
echo $HTML->heading2('Edit Listing Below');

echo $Form->form_start();

echo $Form->fields_from_template($Template, $details);

echo $Form->submit_field('btnSubmit', 'Update', $API->app_path());

echo $Form->form_end();



echo $HTML->main_panel_end();

Thanks.

Sorry Drew - here's some more info:

• The site will contain a lot of user generated content, this part is a directory of businesses
• Members register (standard Members Add-on) and then within their account there is a page which contains the form to accept the data from the member (business name, description and so on) - this is part of the add-on so it is called like this:

     perch_wbn_directory('my_listing.html');

• Once a member has submitted their data it becomes available to view within Apps -> Business Listings within Perch
• Administrators can then view/edit the data as required

So far a member can register and submit their data and I can view it within Perch, but get errors when trying to update the listing via the add-on in Perch due to the mistmatched form fields.

If perch_ wasn't appended to the each input their would be no problem - but I can't see how to get around this problem.

Does that make sense?

Thanks for looking.

Perhaps this is where I'm coming unstuck... I'm just using perch:input in my template (my_listing.html) to create the input elements:

<perch:form id="updateListing" method="post" app="businesslistings" type="default">

<h2>About Your Business</h2>

<div>
    <perch:label for="listingTitle">Listing Title</perch:label>
    <perch:input type="text" id="listingTitle" required="true" label="Listing Title" />
    <perch:error for="listingTitle" type="required">Please add your listing title</perch:error>
</div>

<div>
    <perch:label for="listingIntro">Listing Introduction - Briefly Describe Your Business</perch:label>
    <perch:input type="text" id="listingIntro" required="true" label="Listing Intro" maxlength="140" />
    <perch:error for="listingIntro" type="required">Please add your listing introduction</perch:error>
</div>

    // etc...