Jump to content
Kuuzu Forum

All Activity

This stream auto-updates     

  1. Yesterday
  2. piernas

    Design by Committee

    Hi Frankl, I suppose you're still busy but I'm wodering (I'm not the only one) why the project does not start - There's been some dicussion and a vague roadmap set up but does not seem to be final. By reading the forums it looks like there's no team and nobody is working on the project - you've been absent for months and does not help to clarify the current status of the project. Are you willing to continue with it?
  3. Earlier
  4. Dan Cole

    Guest checkout

    I think that's the ticket. Dan
  5. ArtcoInc

    Guest checkout

    @MrPhil No problem. As I initially suggested, if a "guest Checkout" is not built into Kuuzu (perhaps as an option?), the 'logic', or work-flow, of the checkout process needs to be modular, so that an alternative route could be added. Malcolm
  6. MrPhil

    Guest checkout

    Yes, I was trying to consolidate previous discussion into a summary, along with some new ideas. Didn't mean to sound like I was taking credit for your ideas!
  7. ArtcoInc

    Guest checkout

    @MrPhil That's pretty close to what I suggested in the first post in this thread (abeit, with a little more detail) Malcolm
  8. MrPhil

    Guest checkout

    OK, I can see customers as being reluctant to create an "account" because they're afraid it gives the store permission to keep data around for a long time (reality: most data needs to be kept for business/tax/regulatory reasons anyway) they're afraid that having a "long term" relationship with a store (an account) will mean they're innundated with spam (reality: most mailings should be controlled by explicit opt-in selections that can be revisited at any time) remembering yet another account name and password is a PITA (using their email address is better than an arbitrary account name they'll forget) Almost all of the information you would collect for an account is needed anyway for processing an order, so it's not that much more work for the customer the first time around. Giving keys or tokens to a "guest order" to access order status, write reviews, make returns, etc. is a possibility, but the big prize (for customers) is not having to enter everything again, once their email is recognized. You can't keep credit card numbers, etc. without going full PCI-DSS compliant, but does keeping the shipping address, phone number, etc. violate any regulations if access is not password-controlled? An email address is fairly public knowledge, so would it be a security problem to prefill fields based on an email address that the store has seen before? Or should it require a password to retrieve such information? How about allowing access to writing/editing reviews, and checking order status? The confirmation email could have links in it (with tokens) to perform these actions, which could be used as passwords. Or, the customer could create an account at any time (by giving a password), and streamline their interaction that way. So, the basic checkout interaction could work this way: enter your email first, and if it's known, ask for a password if there is an account. If the customer does not log in with a password, ask for all shipping information. If they do log in, prefill the shipping information, etc. Ask (if they do not have an account) near the end if they'd like to create an account by giving a password. In the confirmation email, give links with long tokens to check order status, enter a review, or create an account with a password (if they did not have an account). If the customer realizes later than they did in fact have an account (or had forgotten their password), and had checked out as a guest, they would need some way to pull that order into their account (another link, if the email is recognized?). It gets more complicated to merge two accounts if they used a second email, or otherwise created another account, but it should be possible. Would this work, as a normally guest checkout that allows account creation (with a password), and access to various functions via link with token regardless of whether they have (or used) an account? To encourage account creation, what sort of functions or goodies should be available only to those with accounts (cross selling, upselling, "you also viewed", a formal wishlist, prefilled shipping address, etc.)? For "guest" checkouts, what should be the protocol if the shipping address or contact information changes? The email address should receive a copy of the order anyway, plus the changes, just in case something fraudulent is going on. Checkout flow: ask customer to enter their email not seen before? ->(A) seen before: account for this email? Yes: ask for password declines to log in, or gives wrong password? ->(A) gives correct password within 3 tries prefill shipping address and contact info (if customer changes anything, note that in conf. email) No: no account associated with this email (and repeat customer) (A) merge point enter shipping address and contact information if no account for this email, ask if want to create an account Yes: enter password twice, store hash in new account entry ask customer to enter payment information
  9. MrPhil

    What the software should be

    Some things that keep coming up on osC, over and over, need to be thought about in the architecture of Kuuza. These are things like pricing, shipping costs, and taxes; which have so many ins and outs and special cases that simple solutions just can't handle. While no store owner wants to write their own custom modules for these, it may be necessary to do so, or at least we can provide some sample code that can be customized and plugged in. There's also how to handle incorrect or inconsistent addressing (affecting shipping, taxes, and interfaces to payment systems). From a customer point of view, they want to see all the correct shipping costs presented (that the store supports), with the cheapest listed first. Every shipper/post office has its own way of doing things, that needs to be accommodated, as well as "buy X amount, ship free" deals, multibox shipments and drop shippers, and restricted shipping lists (e.g., physical goods by US Mail only to US addresses, downloadables to any place worldwide not embargoed). Every US state has its own idiosyncrasies on what tax class to apply on what product, and how to map addresses to tax jurisdictions and their own set of rates for tax classes. Simple solutions such as "item -> national tax class, state -> list of rates per tax class" simply don't exist. Of course, the proper solution is to impose a national rationalized system (consistent tax classes, consistent state+ZIP mapping of rates, one-stop payment) but like that's ever going to happen... And pricing gets ever more complicated with "member" or "buying club" discounts, "buy N, get M free", volume discounts, repeat customer discounts, coupons, credits, etc. Buyers would like to see prices update "live" depending on what they've already got in their cart ("regular price: $X.XX, member price: $Y.YY" sort of thing), and their buying history and knowledge of coupons and credits the buyer is holding. It gets very complicated very fast, and an architecture that allows new modules to be plugged in to take care of these cases could be useful, rather than grafting more and more cruft on to the side of what once were simple modules. Oh yes, and make it simple enough to work with that a non comp-sci business person can easily do it. Granted, it's a lot on the plate, but at least we should be thinking about how it could be done. Do other carts out there do anything like this?
  10. timray

    What is the planned release date?

    Thats great news.
  11. frankl

    The Plan

    Hi all. I've been away on vacation but now back. Been busy so far hiding posts which aren't constructive Let's see if we can get the initial iteration of Kuuzu out very soon.
  12. frankl

    What is the planned release date?

    Stay tuned. An announcement will be made soon.
  13. timray

    What is the planned release date?

    Hi, No, i was hoping there would be a beta so something because what I've been reading seems very interesting. Will just keep an eye out for any releases. Thanks
  14. OSCOMMARKET

    The Plan

    it can only work if do it together!
  15. OSCOMMARKET

    So where i landed?

    And i do not have to.
  16. OSCOMMARKET

    So where i landed?

    So, i try to get it back. But now it is up to you. Like everyone seems to get a chance in building up a new kind of e-commerce system, regardless if based on oscommerce or not. It's work is what should be measured, right? So, regardless my not so subtiel approach. (yet, even if it is not "completed", The admin BS4 became a favorite). So.......... let's first work on an admin, before even considerate work on the front-end. It is a known mistake to work first on the "oooeeesss and ahhhhhs, with a cool dimension given to it" , before make the front-end actually to work. The front-end will be worked out. And what i am saying now, it is not ment sarcastic, @burt have the expertise + much more, he know i know. I worked with him on it, and he know that. And if he remember.... THAT was fun to do. So why cannot work anymore like that? Is there no middle way to find? I feel i am made look like stupid. Just let's work together and see what comes out of it , it is all i ever asked. Before all my anger started, all that was already on the table. I was "Good before" , i became "angry" after. For none reason, i became ignored. It hurt'ed when kuuzu/kuuza was anounced, the ones you counted on most, choosed for it. But i was invited to, and that had a reason. My personality might not suit you. Yet............... my work speaks for itself. It does not matter if finished or not. For that we now we (I), have a so called team. That means we need to put our heads together. And it not matter to me if you are an as-hole, a good guy............. we will get along. We all have our "behaves" , and we all need to deal with them. Now it is me. In time, it will be some other guy. It is always gonna be like that. You cannot serve them all.
  17. OSCOMMARKET

    So where i landed?

    i for sure alienated (some) people. Yet i miss the old oscommerce chat where we knobbing together on posts made on osc. And where we both actively worked on the CE edition. Where i regularly helped people out via "TeamViewer", learned them how to code, or "how to see". Encourage them to use the code "we" worked on. Yeah yeah, of course you owned the link to that repository. And for sure 100% the most result is comming from your achievements. And i love that, i really do. Just not forget how it started, as i was always by your side. No one need to worry for me, i alienated only the wolfs. Not to much fortunately here on kuuzu. I respect the responses telling me i should stop now with this kind of posts. They are right! Working together is all i wanted, since the beginning. If that becomes hard, or not follow the line, HEY....... you have a word in let it know, right? Be clear in it. Working together is what the world makes bigger. But you have to give your voice. If that is not permitted, the chance to fall into a (?????) pit, is to big. Voices need to be heard, even from the unwanted. But have to listen to them. Sometimes to calm a person is to just tell the they are right. I did that for many voices on osc forum. They are not readable anymore, as i all deleted them. But i did that. I told H , like this not can work. I supported many "rants" against H. I also covered H many times against any rants. Regardless what anyone thinks. I also have to respect all the work and ideas i came up with. And i did and offered a lot. There is no one who can decline that. So where where you then? But the idea of a alternative osc, in the shape of "Kuuzu/Kuuza" looks acceptable for you. Same could have been achieved ON oscommerce. I cannot blame the founder of kuuza. I like @frankl , but what exactly is given to you by him, in what i not already gave you? For now i figure @frankl, as he understand my idea's, he likes them. He even wanna adopt. (sure, nothing is for sure, even i keep the door open, everyone is welcome). But he is the only one who NOT ignore my work. Yeah, my latest attitude not worked out in my favor. But i had good reasons for it! I was really pissed. So.... how do you build respect? I only learned from all of you how quickly you loose it. That is for me personally a shame. That's to easy for me.
  18. MrPhil

    What is the planned release date?

    No. There is still a lot of discussion going on over some very basic design decisions. I don't expect to see a release 1.0 any time soon (and if the pace doesn't pick up, ever). If you want something now that is production-ready, use osCommerce 2.3.4.1BS Edge/CE/Frozen for now (not the official 2.3.4.1 release). There should be an upgrade path to Kuuza 1.0, whenever that's ready.
  19. Hi, Just wondering if there is a planned release date for the first version? Thanks Tim
  20. burt

    So where i landed?

    You've alienated too many people because you cannot control your mouth. Worst of all, the ones you've alienated are the ones who were always on your side, even though you could not see it.
  21. OSCOMMARKET

    So where i landed?

    2.4: especially the link saying: Legacy That is what should be talked about. It is already stated that it is unwanted code by H.
  22. OSCOMMARKET

    So where i landed?

    and now................. delete my account please! I have nothing to say to this audience anymore. Few guys left only here for me.(the ones who know to shut up if they do not understand).
  23. OSCOMMARKET

    So where i landed?

    As a advice if ever wanna use the code i putted: Learn to make relations. Lol, that is actual a good advice............even for real life.
  24. OSCOMMARKET

    So where i landed?

    I asked to do that already 3 times. And i warned the owner of kuuzu for it. No one of you can shut up me, untill that happens. Keep in mind, i read 20 years of posts on osc, so i know each of you. The old guys on osc, the BIG talkers................ Where to find you in the addons section? I told F he made a big mistake inviting people who have nothing to offer. All the ranting from these can be read on oscommerce already. From the positive people, even these did not had to be invited. In 20 years, the forum on osc is stucked with information that can be used, infact, should have already been used. These main lesson: STOP USE OSCOMMERCE for your projects. But same story will keep continuing here. Like i said........... to much oscommerce involved. The code above i just posted, could change that. But hey.... the coders have 0 tme, so go take how long, 1 or 2 years? And the world will stand still in the mean time......... right? Just for you osc users.
  25. OSCOMMARKET

    So where i landed?

    Here........ take my UNFINISHED BREAD builder: breadbuilder.php Ask @frankl for the working DB structure, he even have a working copy for the admin/manufacturers.php I just giving a hand to start see things. Do with it what do you want. If i cannot get any support in my ideas. only thing is left to do things on my own. YET, keep in mind, 90% you talking about. I have an answer or can answer to it. It is about others incapability, not mine.
  26. OSCOMMARKET

    So where i landed?

    To @14Steve14 , go to the osc forum, read back your own posts. If i remember one person complaining, it is you. I did stuff, i have a full right to complain. But you see it all wrong. i complain to kick ass, i do it on perpose, i WANT to IRRITATE. from 2.2 to 2.3.4.1 and the adopted 2.4 for kuuzu. The addons section consists of many many good ideas. Many of these should be in core. Sure, not as they are written. But NOTHING is been done to "simplify" the code. Not even today, any new class is introduced. Not even today 2.4 is full OOP, not even speak of 2.3.4.1 BS If no one complain or POINT to these problematics in the code, nothing will change. Ive read all posts here, for now i come to the conclusion it will be a loaded fork. Something that no one wanted. And what work is done? -Introducing bootstrap 4 to front-end -introducing bootstrap 4 to the admin (moi) -And yay, introducing bm_*,cm_*,ht_* to the admin.(moi) That won't gonna do it. it is not enough.
  27. OSCOMMARKET

    So where i landed?

    What happened to the support that should have given to the initial idea? The idea was in favor of all osc users. The selling of an item , all $ would go to the dev. Why you ask if never was interested in the first place? You hold a leading role in the osc community, i offered 50% if wanted to join. You declined. I did enough to keep the peace, i reached out my hand many times. I hope you find your sparring partner(s).
  1. Load more activity
×