Support/Comments for FoxyBack-MODx (modular ecommerce backend)

This is an auto-generated support/comment thread for FoxyBack-MODx.

Use this forum to post any comments about this addition or any questions you have regarding its use.

Brief Description:
A MODx backend for managing orders, built to integrate with FoxyCart. FoxyBack-MODx attempts to be as flexible as MODx itself. Wherever possible, functionality has been done as "MODx" as possible, using chunks, snippets, and etc. in order to allow customization.

Full Description:
FoxyBack-MODx is a modular order management system for MODx + FoxyCart.

It can handle orders:
- display orders to manager (or webuser) users
- handle custom order statuses (pending, cancelled, approved, denied, sent to fulfillment, etc.)
- handle custom "hooks" on order status change (ie. add webgroup permission to user on status "application approved")
- handle different types of orders (shippable products, membership applications, etc.) and assign an initial status

It can handle webusers (or manager users, if you wanted to):
- automatically create webusers from FoxyCart customers
- grant/deny webuser permissions
- allow webusers to view their own past orders

It can handle e-commerce specific stuff:
- integrate with fulfillment companies (AtLast Fulfillment, Smart Fulfillment are already coded)
- handle returns/refunds (using custom hooks and forthcoming functionality)

In short, it’s built to handle whatever you need, exactly how you need it.

For the latest code and additional information please check FoxyBack-MODx out at Google Code:
http://code.google.com/p/foxyback-modx/issues/detail?id=1

FoxyBack is currently ALPHA. It _works_, but there is very little documentation, and the code is being restructured to allow for easier use. We are uploading it because people have been asking, and we’d love help finding bugs and improving it.

Brett - Great.

Does FoxyBack work alongside Foxy Inventory? One of the client’s other things she "sells" are admissions to events, so I could see this working pretty well for that too.

And can this setup email out confirmations to the Site Owner and the Customer, or will our team need to customize it for that?

Pretty awesome.

- John

It could definitely work with the inventory code. Right now it only does a few things "out of the box", but the intent is to provide a framework that’s flexible enough to build on top of.

Seems like inventory control and subscription management (with expirations) are the next things to do.
Worth understanding is how FoxyBack can handle the initial user creation. FoxyCart checkout -> MODx webuser. It doesn’t necessarily have to work this way, but FoxyBack can handle the initial MODx webuser creation (and add appropriate permissions based on product added). If you’re creating the webuser prior to going through FoxyCart it might have to be modified slightly.

(We’ll also be adding some user API functionality to FoxyCart at some point to allow for better user synchronization.)

Does that help? I have a feeling I might have just complicated things.

No, thats good, it didn’t complicate things.

I’m just making my list for my programmer. If you guys get to these things first, great, but if not, this is how I’ll have to modify it for my situation.

1) Subscription expirations in FoxyBack.
2) Some kind of mod so that FoxyBack will create the user if they are truly new, but, will simply add appropriate permissions if the user already exists.
3) Ensure that inventory management works easily and accurately with this combination, both for me (as the system admin) and ideally also for the client (who adds products/events). From what you’re saying, it sounds like it will. And for this particular app, she only hosts about 8 events a year, so its no big deal if I have to handle the setup for those.


I’m just realizing that FoxyCart already sends custom emails upon a purchase, so there’s no mod necessary for that.

My client isn’t going to come online with ecommerce for a few months, so, I’ve got time to plan either way. In the meantime, I’ll get installed on one of my dev sites, and I’m sure I’ll have lots of questions after I do that.

Great name by the way... a little bit Justin Timberlake inspired?


John

Great. Feel free to pop onto the FoxyBack Google Group to chat, or post questions here.

And yes, we’re totally bringing sexy foxy back

hello

I am about to integrate my MODx site with Foxycart and am a little confused as to what to install to assist me.

We are creating an information resource with free-to-access and subscription areas. In addition, by New Year, subscribers will be able to purchase online training modules.

To what extent does FoxyBack overlap with FoxyCart Webuser Paid Subscriptions?
http://www.modxcms.com/FoxyCart-Webuser-Paid-Subsciptions-1682.html

I am hesitant to go with FoxyCart Webuser Paid Subscriptions if FoxyBack can handle subscriptions but need something fairly quickly. I would like to avoid losing my New Year vacation in order to re-engineer the site for the later product sales.

Clarification would be most welcome.

Thanks

L

Good question. FoxyBack does pretty much entirely overlap the functionality of the Webuser Paid Subscriptions, but it also does a LOT more, and at this point is a much more manual install requiring you to "get your hands dirty" to get it configured properly.

If I was doing it I’d use FoxyBack, fwiw. If you have problems on the install please join the Google Groups mailing list and ask there, or ask on this forum. As more people use it and ask about it we’ll put more time into cleaning it up (particularly the install).

Thanks for getting back so quickly - four minutes must be a record.

I am going to go with FoxyBack for a day and see where I am then. I will definitely need assistance along the way, however until I start.....

Thanks

L

hello

trying to get past first hurdle installing FoxyBack. Using INSTALL document in package file as guide.

Action so far:
INSTALL doc item 1) Uploaded to /assets/modules
INSTALL doc item 2) Refers to editing sql/foxyback-install.sql inserting "the ID of the parent document to create all of the manager documents under". This infers creating a new page in the modx document tree so I created a new blank doc, ID number 568. Edited the SQL file accordingly.
INSTALL doc item 3) Executed sql/foxyback-install.sql. Hit an error: "ERROR 1146 (42S02) at line 16: Table ’modx_dev4.modx_foxyback_status’ doesn’t exist"

It is of course true. The SQL file does not create a new table modx_foxyback_status and therefore fails. I cannot create the table manually - I do not know the schema.

As an aside - I also see another SQL file ’sql/patch.sql’. What is this for? Do I need to run this also?

Please advise on both modx_foxyback_status table schema and patch.sql.

Thanks

Leapy

Just realized I missed it back in september, great addition Brett !