requiring us to use the clunky storefront template for the checkout process is not a good solution. There needs to be a better option
People spend lots of time building their own branded storefront but we have to redirect our customers to a completely different site for the checkout process. Then while they are at checkout, if they want to add other products, they are viewing product pages from the storefront template, which are not branded the same as the primary site. We basically have to maintain 2 different sites, and the storefront site is not very customizable. Godaddy has offered other sites that use the plugin, as reference, and these sites have managed to customize the checkout pages to be branded like the primary site like maddogdomains.com, but Godaddy still says this is not possible.

All reseller storefronts have been migrated to the new cart. Updating ticket status to completed.
-
Will commented
The Store seems to be redone as of March to me. The sites like maddogdomains.com use the plugin, don't offer servers (or other products not listed in the plugin either), but I have seen that they are adding these functions soon. I eagerly await, and I believe you can copy some coding from the reseller php functions / products to create other add to cart buttons etc. Short codes work as well. You can also skin your storefront. However, I do agree, the plugin will be amazing once all products are added!
-
fletch22 commented
We now have the same cart as MadDog, or perhaps you could say they have the same cart as we do -- in fact, their logo is equally squished into the upper-left teensie space we have been allotted. As for the site, it's a well-functioning but entirely off-the-shelf WordPress site. Two weeks of studying WordPress by anybody who has developed websites with any other tool would be sufficient to construct such a site, and I can find no functionality in it that we can't build into our own WordPress sites using the plugin.
Never mind the fact that WordPress is the most delicate, fragile, NON-robust, NON-scalable, easily corrupted, easily hacked/cracked/breached, and difficult-to-backup/impossible-to-restore, piecemeal, cobbled-together, server-resource and bandwidth hogging, clunky, faddish, easy-to-spot-as-WordPress-built, slow-loading, juvenile/blocky/kindergarten-toy looking dev platform ever to grow out of the public's need to build "cool-looking" sites "easily" combined with the widespread desire of half-competent coders to create slapdash, non-standard, works-gumming temperamental plugins and templates that are always version sensitive, typically abandoned years ago, and rarely cooperative. And then there's the support from all the CSS-stylesheet lovers who crave uniformity and "clean coding" (though Google's algorithm DESPISES and down-ranks both such things), but that's OK by them, since rather than allowing we common rabble to use sensible and easy and friendly WYSIWYG and nested tables (with styles for reasonable uniformity), we're all now told that's out the window -- we need to use "containers," which of course can and do nest as many layers deep as we wish, like matryoshka dolls, but alas we can't do it from a split text/html editor any more -- we need to dig into a cryptic Cascading Style Sheet and figure out ITS own nesting system lest we affect the wrong text. And even then we're causing dis-uniformity, right? Nooooo, can't have that. Better everything looks huge and stupid with 22-point paragraph fonts in no more than 6 typefaces, until we wretch and choke and vomit on the blandness and WordPressyness of it all...
Oh, and even when all the WordPress plugin/template/theme/widget/builder pieces are selected specifically to work with each other, they still error on a regular basis just saving a few changes on a not even moderately complicated page.
But that's fine, since it keeps the know-it-alls happy -- the ones who want everything crammed into a fragile, corruptible database rather than having actual .htm files on a server we can work with on our client side, sans need of constant server activity just to build and maintain the site, and then upload to the server which would, in a world without WordPress doing what a server is SUPPOSED to do -- serve out files to requesters, and not function as some kind of online building/updating/maintaining platform where one feels surrounded by thin china that will shatter lest we dare experiment. Yeah, WP wasn't really the ideal platform for the plug-in, but given the dearth of much else in the way of choices, that's what we got.
And MadDog's site, while competent and reasonably attractive, is something any of us can, and do, build for our front end. GoDaddy did nothing special for itself that I can find. They're playing by the same rules we are on MadDog and DomainsPricedRight. And for that, and for the fact their plugin is fairly solid, I can see no grounds to criticize them.
-
uzthegeek commented
Is this your site -> maddogdomains.com i am ready to pay for such design can you quote me for this?