I'm looking forward to trying out the new Web Form Builder 2.5, but have some questions that I could find no answers to:

1) Again, multi-page forms are listed as "Coming Soon" in the Feature Roadmap, as they were since the introduction WFB 2.x. Some of us bought prior versions of WFB for this purpose, but it never happened. Is this something we can count on actually coming soon this time?

2) Will forms created in WFB 2.x open in 2.5 for continued editing & changes to older forms. I just created a new form with 2.4 and am wondering if I'll be able to edit it in 2.5. Since there seem to be many fundamental changes to 2.5, it's a valid concern.

3) Can WFB 2.5 be installed side-by-side with WFB 2.x or does it install over & replace 2.x? (Only important if older forms are not editable in 2.5)

4) In the WFB Feature Roadmap, there's this: "Customize the stylesheet for maximum control. (You’ll be able to import your changes.). Editing the CSS after the forms were generated have been a bear in WFB 2.x. Is this some improvement to that and can this be explained more fully?

5) I'm considering purchasing RED soon. In the WFB 2.5 email announcement I received this morning, there's information about integration between RED & WFB. Can this be explained more fully since there doesn't seem to much info yet on the CC website?

Thank you & looking forward to upgrading.

No multi-page forms yet. See change logs for full list of what was included: http://www.coffeecup.com/forums/web-for … ange-logs/


You will be able to edit older forms with 2.5.


No. Only one copy of the software can be installed at a time.


No changes have been made there. See change logs for full list of what was included: http://www.coffeecup.com/forums/web-for … ange-logs/


We have full instructions in our documentation on how to use RED and WFB together here at http://www.coffeecup.com/help/articles/ … on-emails/

Although WFB 2.5 contains welcome additions and fixes, a true confirmation of payment for PayPal users is still absent. Even PayPal admits that without IPN integration, a truly positive confirmation may not be possible.

The file checkoutpps.cls.php contains the code to communicate the notify_url and a custom value (_transactionid_ would be perfect) needed for IPN. Other portions of the button code on this page are used by WFB. Is it possible to add what is missing?

Since the notify_url can be hard-coded as a name value pair, I have been able to return a good IPN, but without the "_transactionid_" or "route" custom value (they have the same value), it is not possible to mark the original submission as "paid." If one of these was maintained in the $_SESSION, that might do the trick.

Don't get me wrong, I think WFB is a great app, but a truly positive confirmation of PayPal payment is needed. Even CC's own SCC app has this.

Has anyone found a work-around for the missing custom value without building their own php page to process the original form submission and pass it along to PayPal?