Forums / Developer / Redirect error after posting a comment

Redirect error after posting a comment

Author Message

Iris Hoekstra - Roscam Abbing

Monday 05 April 2004 6:08:45 am

If you would, please have a look at http://www.elysee.nl/index.php/content/view/full/100

Click on the 'n comments so far' link and try to add a comment. See the error that occurs. I have been trying to figure this one out for I don't know how long but I don't have a clue. Does anyone have any ideas?

I know some things still look a bit daft, especially in IE. I'm still working on it.

Thanks in advance, Iris

Eirik Alfstad Johansen

Wednesday 07 April 2004 1:32:12 am

Hi Iris,

I didn't find any errors, but rather I was brought to the version editing page. If this is what you're referring to as the error, it's probably because you are missing a hidden form field or two in your post-a-comment form.

Sincerely,

Eirik Johansen

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Iris Hoekstra - Roscam Abbing

Thursday 08 April 2004 4:46:05 am

Yes, this is exactly what I mean. When testing the site in Opera, you get an error, but in IE, it does what you described.

My form action looks like this:

action={concat("/content/edit/", $object.id, "/", $edit_version)|ezurl}

(Not sure I understand this, but I copied it from the "tscm" tutorial .)

And I have got these two hidden variables:

<input type="hidden" name="MainNodeID" value="{$main_node_id}" />
<input type="hidden" name="RedirectURI" value="{concat("content/view/full/", $object.parent_node.url_alias)|ezurl}" />

And I'm importing these two templates:

{include uri='design:content/edit_validation.tpl'}
{include uri='design:content/edit_attribute.tpl'}

Do I need anything else?

Eirik Alfstad Johansen

Tuesday 13 April 2004 12:09:42 am

Hi Iris,

If I remmeber correctly, there are also some hidden form fields in the edit_placement.tpl template which need to be included. I would recommend that you start with the default edit template and then remove code bit by bit to see which parts that are vital for the edit process to work, and which are not. Sadly, this is not documented anywhere.

Sincerely,

Eirik Johansen

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Iris Hoekstra - Roscam Abbing

Thursday 15 April 2004 1:31:56 pm

Thanks, Eirik. Unfortunately edit_placement didn't do the trick. The funny thing is that I also have the blog demosite up and running and there I can add comments without any problems. So I tried to copy everything I could from the templates from that site. I have compared everything about a hundred times but I can't see what's different.

When I look at Apache's access.log, I see that when I add a comment on the blog demosite it does this:
127.0.0.1 - - [15/Apr/2004:19:18:26 +0200] "GET /index.php/elysee/content/view/full/100 HTTP/1.1" 200 13168
127.0.0.1 - - [15/Apr/2004:19:18:42 +0200] "GET /index.php/blog/content/view/full/194 HTTP/1.1" 200 17071
127.0.0.1 - - [15/Apr/2004:19:18:52 +0200] "POST /index.php/blog/content/action HTTP/1.1" 200 8955
127.0.0.1 - - [15/Apr/2004:19:18:53 +0200] "GET /index.php/blog/content/stylesheets/admin.css HTTP/1.1" 200 11843
127.0.0.1 - - [15/Apr/2004:19:18:58 +0200] "POST /index.php/blog/content/edit/302/1 HTTP/1.1" 200 18427
127.0.0.1 - - [15/Apr/2004:19:19:10 +0200] "POST /index.php/blog/content/edit/302/1 HTTP/1.1" 200 12770
127.0.0.1 - - [15/Apr/2004:19:19:12 +0200] "GET /index.php/blog/content/edit/302/stylesheets/admin.css HTTP/1.1" 200 6912
127.0.0.1 - - [15/Apr/2004:19:19:18 +0200] "POST /index.php/blog/blogs/personal/party HTTP/1.1" 200 20423

But when I add a comment on my own site, all it does is this:
127.0.0.1 - - [15/Apr/2004:19:20:10 +0200] "GET /index.php/elysee/active_speakers/test HTTP/1.1" 200 12824
127.0.0.1 - - [15/Apr/2004:19:20:15 +0200] "POST /index.php/elysee/content/action HTTP/1.1" 200 8966
127.0.0.1 - - [15/Apr/2004:19:20:16 +0200] "GET /index.php/elysee/content/stylesheets/admin.css HTTP/1.1" 200 16555
127.0.0.1 - - [15/Apr/2004:19:20:20 +0200] "POST /index.php/elysee/content/edit/327/1 HTTP/1.1" 200 14407

Don't know if that helps, it's really just a different way of describing the same problem. But maybe it'll jog you memory or something.