next »

[The Man Can!]

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.

[cfn]

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

[The Man Can!]

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.

[cfn]

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

[The Man Can!]

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

[leapy]

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

[The Man Can!]

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).

[leapy]

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

[leapy]

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

[davidm]

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

[leapy]

further to my comment of yesterday. I found some help in the issues section of the FoxyBack google code pages. For those that need it, it can be found at http://code.google.com/p/foxyback-modx/issues/list

I am further down the line but need a few more pointers:

a_) Is there a comprehensive list of FoxyBack pages/snippets/chunks/modules that are supposed to be visible within the modx backend after a successful installation?
b_) Certain FoxyBack chunks call a snippet called Bounce. I have searched high and low and cannot find this snippet. Any clues?
c_) During installation a root-level page is created named "FoxyBack - Order Manager". This has no children ("This folder is empty). The contents are

Code:

[!Redirect?id=`28`!]

. Should this redirect be altered to the ID of the master page under which the Order Manager, Order Edit, Ajax Handler, test - atlast fulfillment, and Datafeed Processor pages were created? Alternatively, to one of the above named pages?

Thanks for any further advice.

L

[ChuckTrukk]

Bounce Snippet

Code:

<?php
// Name:&#160; &#160; bounce
// Version: 1.0
// License: Public Domain
//
// Description:
//&#160;  "Bounce" over the content of a page via a temporary 302 forward without rendering
//&#160;  the content. Useful during development to send "regular" users to "coming soon" page. 
//&#160;  A Manager session by default skips the bounce and allows viewing the page content.
//
// Usage:
//&#160;  [!bounce?docId=`XX`!]
//&#160;  [!bounce?docId=`XX` &mgrBounce=`1`!]
//
// Required Parameters: 
//&#160;  docId: integer, the Document ID of the destination page
//
// Optional Parameters: 
//&#160;  mgrBounce: boolean (false), bounce even with a validated manager session

$mgrMode= isset($_SESSION['mgrValidated']) && $_SESSION['mgrValidated'];
$mgrBounce= (($mgrBounce==true || $mgrBounce=='1') && $mgrMode) ? true : false;
$docId= ($mgrBounce==true || ($mgrMode!=true && isset($docId))) ? intval($docId) : 0;

if ($docId) $modx->sendForward($docId);
?>

For the document's, the easiest way it to go into phpmyadmin and edit the 'parent' of the docs foxyback created. The parent is hard-coded and their parent probably doesnt exist right now (so you cant see em in the tree). Set the parents of documents created by foxyback to 0 so you can see them in the main root. Then you can move em.

[leapy]

wonderful! Thank you, Chuck

[The Man Can!]

We know the install process needs some work, and that'll be the next thing we work on. Sorry in the meantime, and thanks Chuck for giving that tip.

[leapy]

An expansion of my earlier post - I need some clarification if possible:

Following the INSTALL documentation, I used sql/foxyback-install.sql to create a number of pages.

One of these was named "FoxyBack - Order Manager". This was an empty folder at root level that contained just

Code:

[!Redirect?id=`28`!]

.

I changed this to refer to the document under which the FoxyBack pages were created,

Code:

[!Redirect?id=`568`!]

However I then realised that I did not have a snippet named "Redirect".

I found one here on the modx wiki that seems to the trick:

Code:

<?php
$url = $modx->makeUrl($id);
ob_end_clean(); // this will end the output buffer and discard silently what ever was in it
header('Location: '.$url);
?>

a_) Am I right in believing that this code will do the trick?
b_) Which document is this page supposed to be redirecting to? and why?

Many thanks for further help

L

[stevesunderland]

1. would anyone be willing to briefly explain how to create a simple login page for webusers to view their orders? i have foxyback up and running but i'm a bit lost in all of these snippets... thanks in advance.
solution: create new "display orders" and "order view" documents for your "customers" web user group and apply this fix

2. are we required to enable "friendly alias paths" in order to use foxyback?
solution: manually modify file paths and form actions in chunks/snippets

3. i would like to use the integrations for foxyback, foxycart_inventory, quickbooks and campaign monitor using the XML data feed. anyone willing to help me with this final step?

[echaland]

Hello,
I installed Foxyback. Thanks for the preview.
 What is the use of the document "FoxyBack -Order Manager" that was created during the install? It only has a snippet

Code:

[!Redirect?id=`id`!]

For id I used a root document containing Oder Management, Order edit Ajax Handler and so on.
Thanks for any input...

[leapy]

hello

That's exactly what I did. An alternative is to move the other pages created to be children of the FoxyBack -Order Manager page.

L

[echaland]

Ok, thanks got it now.
Another question, I'm using a test script to mimic FoxyCart.com and send encrypted and encoded XML to a URL. However when I run the script I keep getting an mysql error:

Code:

mysql_connect() [function.mysql-connect]: User xxxx already has more than 'max_user_connections' active connections

Does anyone know how to get around this?
Thanks   

[leapy]

hello

you need to check your mysql config for max connections.

probably in /etc/my.cnf if you are running your own server and have access