Thanks for this module.

The only issue I face so far is that with a long list of fields and/or field data, I get a watchdog warning about overlong referer when I submit the new node form. This is because of use of URL parameters passed via the GET method.

Could we add a POST method to give users a choice of submitting the prepopulated fields without encountering the overlong fields/data URL warning ?

I did a quick hack to convert from $_GET to $_POST. Additional, I added a urldecode on data that contains % (which arises when a space was encountered). So far this works with my data which are either alphanumeric+space or decimal numeric.

If there's demand, perhaps, we could incorporate a dual handling for GET and POST methods, whereby if no URL parameters were found, it looks for POST variables. Or alternatively, just a simple GET vs POST priority (whichever has at least one variable); OR even a combination of both method's variables whereupon duplicate variables encountered are resolved via priority of one over the other.

Any interest in this ?

Mine has mainly been to avoid the watchdog warnings clog up my logs.

Comments

add1sun’s picture

Version: 5.x-1.3 » 6.x-1.x-dev

If you can supply a patch that moves in this direction, I'd definitely look it over. A patch for new features should go against HEAD so I'm changing the Version on the issue.

robloach’s picture

Priority: Minor » Normal

Prepopulate rocks my socks off, and so do POST requests. Subscribe.

robloach’s picture

Status: Active » Needs review
StatusFileSize
new2.96 KB

Moved over from $_GET to $_REQUEST.

robloach’s picture

Priority: Normal » Critical

Ping! Is this module maintained? Last commit was in 2008. Does it need help? If so, I'm willing to help out....

robloach’s picture

StatusFileSize
new1.81 KB
new1.8 KB

Here it is for both HEAD (Drupal 6) and DRUPAL-5 branches with documentation.

robloach’s picture

Status: Needs review » Reviewed & tested by the community

Sticking it in the RTBC queue.

jbrauer’s picture

Priority: Critical » Normal
Status: Reviewed & tested by the community » Patch (to be ported)

Committed to 6.x-1.x branch. Marking as to be ported for 5.x and 6.x-2.x branches which I need to get the branches coordinated.

robloach’s picture

The DRUPAL-5 patch is right here, from #5:
http://drupal.org/files/issues/242749-drupal5.patch

jbrauer’s picture

Thanks Rob... Sorry I wasn't more clear. I'm not setup with Drupal 5 at the moment but will be soon and will get your Drupal 5 patch when I do.

robloach’s picture

Ah, haha :-) .

jbrauer’s picture

Issue summary: View changes
Status: Patch (to be ported) » Fixed

At this late stage no plans to port to the unsupported 5.x branch

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.