This could work, but seems to have the same problem as using ezhttp. The form posts to <i>content/action</i>, but it then redirects to content/edit. The view parameters (and the ezhttp, I guess) is lost in the redirection. Am I doing anything wrong here?
Yes that is more difficult. A few possible solutions:
- Set a cookie with Javascript.
- Modify kernel/content/action.php to pass on a hidden field with your node id. - Add a new action as an extension which largely copies the 'NewButton' action but with your additions.
This thread interests me as I'm working on a forum at the moment also. How did you go with this, I'd also be interested in hearing of any other improvements you created.
www.dbinformatics.com.au
We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.