I've tried this module and just got a bunch of errors that shutdown my site. Is this working for anyone? Any examples of how it should be used? thanks.

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Working on my testing. Please describe your errors.

To test:
* install and enable
* create a new 'page' node and set it to PHP type
* for body, put the following and then preview. You should get a rendered form.


$form = array();
$form['title'] = array(
  '#type' => 'textfield',
  '#title' => t('Title')
);
$form['body'] = array(
  '#type' => 'textarea',
  '#title' => t('Body')
);

print drupal_get_form('testform', $form);
jasonwhat’s picture

jasonwhat commented

Shuts down my whole site with this error:

Fatal error: Cannot redeclare form_clean_id() (previously declared in /home/mysite/public_html/drupal/includes/common.inc:1587) in /home/mysite/public_html/drupal/modules/backport/form.inc on line 1013

I'm not using standard 4.6, but a version before the forms change and have an ajax module running. Basically I tweaked it to have some 4.7 js features, but not use the new form api so I could use 4.6 modules. I guess I'm wondering if backport could help me span the gap, using both some 4.7 and 4.6 modules at once...is that it's purpose?

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Title: Anyone using this? » Conflict with pre-Forms API CVS HEAD
Category: bug » support

Because you don't have 4.6, your code includes some of the functions introduced for 4.7, and so conflicts with this module.

using both some 4.7 and 4.6 modules at once. is that it's purpose?

Well, a small minority of 4.7 modules might work in 4.6 with backport. More likely, they will need some adjustments. Backport can be used to:

  • Facilitate backporting of 4.7 modules to 4.6
  • Enable 4.6 development using 4.7 methods, therefore saving time with the eventual 4.7 upgrades.
nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Active » Closed (fixed)

closing.