Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
4.0.3 comment failure
Just upgraded from 4.0.2 > 4.0.3
Noticed that my comments doesn´t work… have I missed something in the hurry?
Run my site i live mode but it still generates the following code just above my comments form:
id=116#cpreview” id=“txpCommentInputForm”>
Any ideas?
Offline
Re: 4.0.3 comment failure
This happens when you do not use textpattern’s own tags for form-elements, but insert your own html-input elements instead. Try using <txp:comment_message_input /> in your form and the problem will go away. I wasn’t even aware people were preferring to use their own html-code instead of the built-in tags, so this wasn’t tested during development.
Offline
Re: 4.0.3 comment failure
Ahh… even I forgot that I used this =) experimented a long time ago… hehe, sorry again for making a fool out of myself…
EDIT:
No, It still doesn´t work. Threw the hardcoded pieces away and copied paulasaur.us comment form (But didn´t do the changes in comment.php since I couldn´t find the code to replace). Also tried the default form as recommended in the FAQ.
When previewing a comment I´m pointed to a HTTP 405 page. (url example: http://www.mattiasskoog.se/id=122#cpreview)
Problem accured after upgrade 4.0.2 > 4.0.3
Last edited by skoggy (2006-01-10 17:46:01)
Offline
Re: 4.0.3 comment failure
Your problem is related to you using IIS as your webserver. My guess is that previously two bugs were overshadowing each other for you, which is why in the end it worked (request_uri being empty and a sometimes empty action-field in comment forms). We have added (the second) fix for request_uri being empty.
Take a look at this topic: http://forum.textpattern.com/viewtopic.php?id=12619
Offline
Re: 4.0.3 comment failure
Thanx Sencer. (Nice Avatar by the way) :)
EDIT: Got it! :) added the codestring as mentioned in the thread above.
I´m not familiar with all that information. And that thread is full of links to other threads… In other words, I don´t get it.
Is this IIS-problem fixed in the latest SVN?
or, do I have to “downgrade” my txp version back to 4.0.2?
Last edited by skoggy (2006-01-11 20:55:09)
Offline
Pages: 1