Drupal 6

I'm trying to get it to work with 5.7
could you please explain what you did and what the problems were?
right now filter seems not to parse filter tags [node: ] etc.

I tried the original patch and it did not apply cleanly. I've made the changes manually and created a new patch file (attached). The module works quite happily within Drupal 6 although the Coder module suggests a number of changes that should be made in order for the module to meet the coding standards. The attached patch DOES NOT address coding standards.

Can somebody please update. Thanks.

I have my own version now... 8-)

Pretty much the same, it includes a "collapsible" mode as well, and the code is reformatted.

Just in case, I put the entire module rather than a patch since it is a lot easy for many people to use a complete tarball instead. (also really the patches were close to nothing.)

Thank you.
Alexis Wilke

hi alexis and thanks

just fyi-
i am using this on drupal 6.9

works like a charm- perfect!
thanks for sharing your work.

vincent, in buffalo
http://basicmagic.net

adding tags for this node...

Thanks for the archive, Alexis.

It looks like fine, thx!

Nice.

Just one small point, the module ends with a trailing ?> and a single whitespace\linefeed. This is not needed and can lead to the nasty "white screen of death". Just remove this closing tag altogether.

There is a newer version. I also fixed the version in the .info file.

Thank you.
Alexis

I have the latest version posted above by Alexis working in my Drupal 6.9 install and it's working perfectly except when trying to insert WebForms. I assumed this would behave like any other node, but I guess not. Does anyone have any suggestions on this?

Thanks.

What do you call WebForms? Is that a module?

Thank you.
Alexis

It's a module used for formbuilding. Surveys, Polls, Quizzes, and the like. If InsertNode isn't working with it, I'd guess it doesn't use the same node fields for it's content. For example, $node->body might not have the webform content.

dchaffin & Grayside,

I would think that this module creates the content of pages in a way that does not indeed get copied in the node body variable. I would think that would require us to write specialized code...

I have now created version 6.x for the project (I'm one of the developers since Mar 2, 2009).

Please, create a new post to talk about this problem, so that way we can track that separate from the main Drupal 6 port.

For now, I will close this issue (mark it fixed).

Thank you.
Alexis Wilke

@dchaffin

In the fieldset "Webform advanced settings", select "Show complete form in teaser"

Alan,

Will that show the Webform with [node:whatnot teaser] ? Or will it also work with the body?

Thank you.
Alexis

Just a note to readers, this issue is closed

@Alexis With that option checked, both the teaser and body should have the form (see footnote). When it is not it checked, the teaser part of the body section should show by itself

If this is not the case, paste the following code directly into a template, changing xxx to the webform node id: (this only shows for the admin user)

<?php
  global $user;
  if ($user->uid == 1) {
    echo '<h1>teaser only</h1>';
    print node_view(node_load(array('nid' => xxx)), TRUE);
    echo '<h1>Complete</h1>';
    print node_view(node_load(array('nid' => xxx)), FALSE);
  }
?>

If this shows correctly, but the insertnode tag does not, then check your tag format, and if still an issue, lodge another ticket here. If this does not display properly, lodge an issue in the WebForm queue. Make sure all modules are up to date.

footnote: Please note that if you have defined the teaser break in the description field, the form will not show.

Eg: The following only shows "The description field, Go to form"

The description field
<!--break-->
After break

The form will never show in the teaser, even with the "Show in teaser" option checked. This can be considered as a bug or a feature, depending on your requirements.

I tried all you sugested , but still empty page .

The dev version seems to have solved the problem

The dev version seems to have solved the problem

Strestus,

Yes. This is also an older bug. You could have created a new entry instead.

Thank you.
Alexis Wilke