Feedback

Friday 03 April 2009 5:59:11 am

Hi ,
can you show us your code(of your template)?
it is hard to say why this form don't works, perhaps you have an error in your code?

The theory is when we know everything and nothing works.
The practice is when everything works and nobody knows why.
If the practice and theory are met, nothing works and we do not know why.

Albert Einstein

Friday 03 April 2009 6:57:22 am

{include name=Validation uri='design:content/collectedinfo_validation.tpl' class='message-warning'
                 validation=$validation collection_attributes=$collection_attributes}
                 
<div>
    <div class="long" style="padding-left:25px;">{$node.object.name}</div>
<br/><br/>
<div class="aide">      
<p>
Pour toute question, n'h&eacute;sitez pas &agrave; utiliser ce formulaire pour nous &eacute;crire. Merci de v&eacute;rifier que vous respectez <a href={"/Règles"|ezurl}>les r&egrave;gles</a>.
</p>
</div>
<div class="aide">
               	<form method="post" action={"content/action"|ezurl}>
        <p class="help" ><br/><center>Tous les champs sont obligatoires.</center><br/></p>
        <p><br/>
            <label for="field_896">Adresse e-mail&nbsp;*:</label><br/>
            
            <input class="text" type="text" id="field_896" size="58" name="ContentObjectAttribute_data_text_896" value="" /> 
            {$node.data_map.email.contentclass_attribute.name}
            {attribute_view_gui attribute=$node.object.data_map.email}       
            </p>
        <p>
            <label for="field_670">Sujet&nbsp;*:</label><br/>
            <input class="text" type="text" id="field_670" size="58" name="ContentObjectAttribute_ezstring_data_text_670" value="" />       
             {$node.data_map.email.contentclass_attribute.name}
             {attribute_view_gui attribute=$node.object.data_map.subject} 
             </p>
        <p>
            <label for="field_671">Texte&nbsp;*:</label><br/>
            <textarea class="box" name="ContentObjectAttribute_data_text_671" id="field_671" cols="45" rows="10">
            </textarea> 
            {$node.data_map.email.contentclass_attribute.name}
            {attribute_view_gui attribute=$node.object.data_map.message}       
        </p>
        
        <p>
            <input type="hidden" name="ContentNodeID" value="169" />
            <input type="hidden" name="ContentObjectID" value="46" />
            <input type="hidden" name="ViewMode" value="full" />
            <input type="submit" class="button" value="Envoyer" name="ActionCollectInformation" />
        </p>
        </form>
</div>
</div>
 

Thank you justin!

Here is my template code contact:

It is also true that there can there be a mistake. I try to find the solution to the time I'm posting this message. And in the evening I'll post later. Despite this support from the family ez is always important.

Thank you and a +

Petit poisson deviendra grand pourvu que Dieu lui prête vie.
Petit oiseau volera un jour de ses propres ailes pourvu que Dieu lui ajoute le nombre de jours sur terre.

Friday 03 April 2009 7:23:44 am

Hi,
with this

<input type="hidden" name="ContentNodeID" value="{$node.node_id}" />
<input type="hidden" name="ContentObjectID" value="{$node.object.id}" />

you are sure that you use the good

 node_id and
 object_id

but if you read this link like mentionned by Daniel Lopes

http://ez.no/developer/articles/how_to_create_ez_publish_forms

you will see this

Under this method, the user’s input becomes part of the website as an object in the eZ Publish content node tree. An example of this is creating a new Comment object beneath an existing Article object (to be displayed when visitors view the article). For this to happen, the user must have the appropriate permissions to create the object at a given location within the content structure. Some other examples of this method are the Forum topic and Forum reply objects within an eZ Publish forum.

This approach may use eZ Publish workflows so that a site administrator must approve the user's object before it is visible on the website. 

so

 the user must have the appropriate permissions to create the object at a given 
location within the content structure

i think this can help you

The theory is when we know everything and nothing works.
The practice is when everything works and nobody knows why.
If the practice and theory are met, nothing works and we do not know why.

Albert Einstein