Project:Signup Ecommerce Integration
Version:5.x-1.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:needs review

Issue Summary

because of og, I need to upgrade to D6. will there be a version of this module available?

C

Comments

#1

I'd be really interested in seeing this too. I've only just started playing with eCommerce (now at RC2 of v4), and currently have a custom 'Paid Event' product type (a CCK date field essentially). However, workflow and reporting doesn't seem that great once a purchase is made, and Signup looks to be a pretty elegant solution to part of my problem. What I'm hoping such a module would do is really help eCommerce gain some ground on Ubercart (especially as Event Registration has a far worse workflow in UC).

I'm not a PHP head, but if someone can point me in the direction of how to help migrate the code (what changes for a module need to be made from D5 to D6) or get involved in testing/documentation that may be a start.

#2

Yeah I might do it, it's a handy module after all... Not that I use it myself!

Pobster

#3

So, I think we need to come together on this and light a fire. Has anyone performed an analysis on the module to determine a strategy for porting to Drupal 6? I'll look through the general document, and both the Signup and Ecommerce documentation and code to try to determine where Signup Ecommerce refactoring of the current version will be necessary for integration with 6. Or, would it be better to start from scratch? I'm assuming this module basically hooks into some of the signup flow while extending some of the ecommerce functionality.

Does anyone have a list of people interested in this? It would be of benefit to run through some of the event/signup/ecommerce posts and collect user info for people who have requested this functionality - I've been reading through these and there seems to be a good amount of demand. If anyone knows of an interested resource in either the Ecommerce or Signup Module, that would be appreciated.

I'll try and update this post with my findings in the next few days. Please chime in to this conversation if you are interested - we might want to begin an off-line conversation.

Regards,
-mark

#4

#5

subscribe

#6

Oh yeah, forgot about this! Please could someone test - apologies I don't have time at the moment to test it myself, I've knocked it up in the fifteen minutes I had spare before going to work...

Pobster

AttachmentSize
signup_ecommerce.tar_.gz 2.49 KB

#7

Ignore this one...

Pobster

AttachmentSize
signup_ecommerce.tar_.gz 2.72 KB

#8

Bugger, I thought of another couple of things as well. As before, all this is untested - please could people test and I'll test tonight when I get home from work.

Pobster

AttachmentSize
signup_ecommerce.tar_.gz 2.72 KB

#9

Status:active» needs review

Okay yeah +1 from me, seems to work fine under light testing (I only tested one of the options - which incidentally can be found under 'workflow settings' on a content-type edit page, eg. /content/node-type/page).

...You know... I'm quite happy if someone wants to add me as a maintainer? I'll support for any bug fixes for both the 5.x and 6.x branches? I'll also make a 7.x release as that'll be a cinch... After this one has been tested more anyway...

Pobster

#10

I'd love to see this module for version 6.x.

Is the .tar pobster posted the version 6.x module? Thanks for any info.

#11

Seeing as that's the whole point of this issue post... Yes of course it is!!! Use comment #8.

Pobster

#12

Hi,
I tried testing the latest attachment posted here, after i post my node it gives me this error

Fatal error: Call to undefined function ec_product_load() in /var/www/signuptest/sites/all/modules/signup_ecommerce/signup_ecommerce.module on line 165

So i tried upgrading the module on my own and got the same error once again.

ec_product_load() is a function in ecommerce module under ec_product module.

Wonder what i may be doing wrong.

cheers
S

#13

ok..found the problem it need product api module in ecommerce to be enabled as well. It should be added in dependencies.

#14

Ah, good spot! Okay that's another of the subtle differences I kept forgetting about above (hence the multiple posts...) it's not an extra though, it's an 'instead of';

signup_ecommerce.info

; $Id$
name = Signup E-Commerce
description = "Integrates the signup and e-commerce modules."
dependencies[] = signup
dependencies[] = ec_product
core = 6.x

Reason being is that ec_product has ec_store as a dependency anyway.

I won't roll another, I'm sure that just pointing this out is enough for people to test with?

Pobster

#15

Another issue: While creating a node signup form gets repeated and any action on the signup form result in one more form. Although if you ignore the multiple signup form and do the settings in 1 form it gets submitted and works fine. Looks like something is throwing it off in a loop.

#16

Apologies but could you clarify this? You're saying 'while creating a node...' yet signup_ecommerce isn't present when you create a node? A new node-type, yes? But I can't recreate your symptoms when doing this? Could you perhaps post a more detailed step-by-step and maybe a screenshot?

Thank you for your time,

Pobster

#17

Hey,
Sorry, work has been crazy for past few days. I will soon post a detailed step by step recreation of the issue with screenshot.

Thx for all your prompt replies.

Cheers
S

#18

Hey,

I found the specific case for this bug. So say i create a node type 'blah' and under Product setting i set it optional (meaning a node may or may not be a product) and allow signup for the node (on by default or off by default anything). Now i go create a node and select it to be a product and add it to store as soon as i do this 1 more signup setting form/field appear beside the 1 that is there already there. However if select a node type to be a product always no additional signup setting form appears. So, additional signup setting form appears on add to store button action.

Cheers
-S

#19

Meh, I'd look into it but no-one other than you actually seems to be bothered so I guess there's little point...? It's not like I'm even using this module myself, I just felt obliged to port it seeing as I ported it for the last major Drupal release.

Pobster
edit: I think I'm just going to leave this until at least three other people request that they're actually bothered enough to have tested my unpaid, unrewarding work

#20

Thought I should leave a comment to say that I gave it a whirl to see if it would work for my site and have had no problems so far.
(that's hardly testing though)

nobody click here