Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by GLWalker

  1. I have applied the product_reviews updates, as well as the bugfix for the product_review content module.


    When testing everything looks as expected.  Ive tested all the markup for product info and reviews and everything is good on my end.


    I think thats all the markup needed ~ I mean it can be took further using the itemList property and applying to the product listings, and even review listings page - but I dont know if its all that. Ive had thoses areas marked up for almost 2 years on a site with no significant difference in the SERP's. The only differences seem to come from the product_info page itself.

  2. I set the random IDs to begin with 00, this way I think I can set up a search function to lookup only the guest orders using a match first two as 00 - as a real customer will never have an id that starts with 00.


    I should have known, you cannot use 0 as first character in a column that is INT - it just strips to the next whole number on insert - however - INT does allow - so the random customer_id is set to start with - followed by a few randomly generated and shuffled numbers.


    Looking in the database table it makes it very easy to see which are quest orders as the - is very easy to spot at a glance - and I like how it represents negative in the case of a non account holding customer.


    I did not realize that mySQL has built in regex checking, so it was very simple to create a search query using REGEXP  to find the customer_id starting with a  - . 






    all these hidden gems

  3. @@burt

    Ah yes, I remeber seeing your screenshot or video for that a few months ago :thumbsup:




    I have confimed a random generated customer_id will work with multiple "guest checkouts if we set the id VIA session key to  bypass any create account functions we can go to the address_book, dynamically add a session based email and phone number, then collect the standard address info - BAM! order complete, all info recorded, email updates can be sent out.


    So this bypasses any script that would want to update customer, customer_info tables, and prevents an anwanted welcome email, yet still allows for an order success email.


    I did 2 orders at the same time simutaniously running open windows of the same browser - no conflicts, 1 a COD order, the other using Stripes test CC numbbers which had to create a connection to process


    I set the random IDs to begin with 00, this way I think I can set up a search function to lookup only the guest orders using a match first two as 00 - as a real customer will never have an id that starts with 00.


    But thats not on a default install, but Im sure a little tweaking can get it there.


    Maybe next year it will see the light of day. If done correctly, it should port over to the next version with little adjustment :-

  4. Yes, you brought up a lot I overlooked on a regular customer account. For what I am building it is no problem becuase the files are all controlled within their own private area and I can bypass the update to customer info if it is a guest.


    Still though, it makes me think about better ways to achieve a guest checkout - making a temporary account is good, but Im looking into how to do it without hacking the core :)

  5. Both being on account at same time is possible, - but you did remind me of a very important aspect I overlooked - the shopping cart. Perhaps a customer_id could just be randomly generated and set by session.


    As for the customer data it is all stored in the orders table so the customer is still notified VIA any admin order updates. And of course a token for checking updates would work well.


    Overall - trying to put the concept of very little to no core updates into the process. Can it be done? I think so.


    But now I must recode my addon to try using a random ID in case 2 or more employess are taking strictly "guest" orders at the same time. +1

  6. Recently Ive been developing a very large addon for store owners to allow their employess to use without having to give them access to the store admin. A employee may view and process orders, email customers, create customer accounts, edit ordrs, and take orders over the phone using its own built in checkout process. Orders can be made for existing customers or strictly guest.


    Anyhow, while using the mod, it dawned on me that I had esencially created a method of making guest orders for customers that call in and do not want an account. Any order took this way goes into a customer account that is stricly owned by the store, and the address books can be set to a higher number than the regular customer accounts.


    So I was wondering, with the couple of guest checkouts available, - 1 deletes customer info after checkout, the other flags it as guest and allows the guest to become customer later. I think for guest you should not keep account data if you tell them they are a guest! 


    Why not create a simple flow for guest that is very unintrusive to the core code by:


    1) Have a select guest option - when initiated a session is set, lets call it guest_order. If guest_order is set, then the customer_id is the same as the stores customer account.


    2) After setting the session, the guest is then directed to the store's customer accounts address book process where they enter their address, with the session set there will also be two more fields in the address book, phone and email.


    3) After filling out complete address info, then two more sessions are set for phone and email, they would work very much like the comments session.


    4) Customer goes throught the checkout and when checkout_process is initiated it takes the session info for phone and email and inserts it rather than the stores defualt info. Then it clears the phone and email session. - Probably delete any address book entries made as well. But thats another area that would be handled by session assignment as well.


    5) On checkout success guest_order session is cleared, order is done, customer can move on.



    All the while the guest_order session is set certian things need to be disabled, such as access to account areas.


    Most of this could all be done using a header tag module. The checkout process would need some editing to tell it if guest_phone/guest_email exist then insert this else default. Unless it is possible to override it with a header tag module - but I dont think so.


    Overall a lot less code changes, no database changes, and orders page would have all the info needed for contacting customer. So far as I can figure in this scenario, - only  2 to 4 core files to change. Or 1 file, checkout_process, and then add new files for the address book/checkout new address selections.



  7. @@burt


    I'll be testing out new changes soon, then provide feedback. 


    I do agree the product listings need a tune up and strip down, it was nice at the time, but looking back, just too much extra that can already be achieved using bootstrap default classes.


    I have some markup that can help with a shopowners preferance on default view as well, but will first test with new setup.

  8. Ive been looking at this. @@Tsimi I downloaded your package, I like the screenshots showing how it looks. I only browsed the code and my initial thoughts were it could get better and be less intrusive.


    My thoughts :


    Most of the code that pulls the logic should be able to move into a header tag module




    All the code could be put into a content module and then place the markup to grab it in the shopping cart file.


    There's no need to show order totals, just shipping quotes. These type of things have to be as simple as possible, not necessarily because of all the different outcomes depending on totals, tax, weight, distance, etc; but as Gary mentioned "customers sometimes display a lack of common sense." That's a big time reason.

  9. Without looking it almost sounds as if a key is not uninstalling from the configuration table, I'll double check my code when I get a couple minutes.


    But to answer the question, only the wholesale login box should be installed - it will allow both retail and wholesale login. All it really does is set a session for wholesale user if the customers id exist in the wholesale customers table.

  10. I think this was done by me a couple of months ago: http://forums.oscommerce.com/topic/397516-2334bs-template-and-modules/

    Hi @@piernas,


    Yes I see you did write some for use with the box modules. However, I am more or less referring to the use of new content modules as introduced in osCommerce V2.3.4.


    You'll see somewhere else in the thread I have suggested removing any box modules that were previously made to display content in places other than the left/right column in favor of using the new content system.

  11. I think that approach would be a win/win situation, and it sort of falls in the same as the login form content module - but with bootstrap is better as we don't need to write any javascript for alpha or omega classes.


    I have already created content modules for everything on the product_info page - past and present. If you send me a snippet of the code you used for the footer module widths, I'll place that in my existing work.

  12. Bear in mind that the site owner (or template maker etc etc) can also go direct into the template file for the module and change things in there.  


    I can make it easy for the average Joe to go into the admin


    Those 2 statements have been my dilemma. I prefer to change the code in the module 100% over anything else. But keeping it simple for the average Joe makes it complicated. In fact, the more I think about adding before and after content spots, I'm now seeing that I have probably made it even more complicated because unless one knows bootstrap, or whatever framework, it would probably be even more difficult to arrange everything as wanted.


    I forgot a very important rule here: KISS


    Revert in process.


    SO now let me overthink again!


    Maybe the product info page could be structured in a way like the admins dashboard where everything is arranged in one slot or another grid type fashion - but that's probably BS too.


    Here we go:

    F@#*! IT - They need to be setup to look just like the default install. Then when one is building their site, they can go in and manually change the HTML in the module.


    Besides that, shop owners and themers will more than likely be putting together their own custom modules for desired presentation.

  13. Unless you modified the code in easy populate, there's no way it would have inserted the wholesale price into the wholesale table. I have not looked at easy populate in several years, but do believe it must be capable of inserting into the specials table.


    If you look at your specials table and products_to_wholesale table in phpMyAdmin, I think you will find the products_to_wholesale table empty, and specials table populated instead.


    If this is the case, then the data can still be ported from one table to the other, but will take some modifications.

  14. Just checked your site, you did not happen to use the specials form to add in your wholesale prices did you? :(


    Every product I see has the specials markup around the source. If so let me know in PM - I can help you convert the tables so you don't have to go through all that data entry again, looks like over 6000 products.

  15. I would double check the code in product_info.php to be sure it is checking that the wholesale session is there. It sounds like it is bypassing it, or perhaps your browser has the session set and you are always seeing the wholesale price, so I would also check the loggoff file to be sure the code for unregestering the session is in place.