GLWalker

So the old version is.... blah, blah, blah. We get it, we know that. The new version is... blah, blah, blah. Still get it, still know that. So the >v4 addons are gone because the old version is... or is it because the new version is...? Makes no sense either way. There actually are users that actually realized the old version's of osCommerce were at EOL status, many who were probably weighing business decisions on how and when to change software. Some of those many users were probably keeping an eye on the new V4, waiting until they feel they can change and build up to meet their shops already existing requirements that there existing osCommerce shop has been customized to meet. Do you not realize how many existing users may want to look back at the old contributions they have had installed through the years? Maybe they have an issue and want to see the original code for debugging, upgrading it to work on modern server setups, etc; Maybe they want to see what it would take to "modernize" an older contribution, or completely make a new addon based on just the "idea" of an old contribution. Anyway you look at it, you alienated countless established users when taking down the old addons. You can repeat how the old version is "...", and the new version is "..." all you want, it doesn't help. People here are not dumb, they're smart enough to already know that. They're smart enough to make changes when their business allows, and they're also smart enough to find another software that will meet their business needs when the time for that change comes. Now all that was primarily the shop owner point of view in me. So how about the developer standpoint? With a quick look, on the surface, the new code shares a lot of the old code. Even makes use of a modified theme system that was an old addon, looks like maybe BTS? or something similar. So that says, hey I can take some old addons, redevelop them, and release them as new addons! But, maybe like, y'know, Holbi had the same idea. So lets just cutoff access to all those old ideas and maybe release the most popular as new and improved paid addons! You have every right to do it too. I feel like your going to push more away than you attract by removing the addons. Such a nonissue just to restore them, such a shit move not too. And believe me, people who know who I am, know I am all too familiar with shit moves and osCommerce. Either way, best of luck.

Meet the new boss, same as the old boss...

MAN have I missed this place!

Hi everyone, thanks for the input thus far, I probably rushed into getting it ready for the BS Community edition, and overlooked a few things. If anyone is using the standard 2.3.XX download, use the first version I uploaded, should be fine. I'll make more changes and upload, I've been n the middle of a move, so this was my first chance back online since the last time I posted. As for the GitHub recommendation, I have been thinking of that too, so expect to see a repo soon. Existing order editing - this doesn't do that - but if there's enough interest it could.

New update addressing errors here uploaded. Another update will come addressing specials price. The price does show as special while in the cart, just not in the product listing.

Just searched around on this file and it appears that it was only being used with USPS module, and it's outdated as well, so it was removed from the BS version.

Code has been updated for compatibility with Bootstrap Community version. Please report any further bugs.

Ahhh, yes.. forgot about those changes for the BS edition - my most recent testing was on the standard 2.3.4.1 download. I'll make changes and update. Thanks for the feedback.

This is the support thread for the Customer Service Portal https://apps.oscommerce.com/xihXD&customer-service-portal The primary goal of the Customer Support Portal is to allow osCommerce shop owners to allow their employees to work on order fulfillment and customer support inquiries without having to allow direct admin access. Additionally it serves as a full fledged order placement system that will work with a shops existing payment methods, as well as a couple of new payment modules that could be useful in case alternate means of payment processing are desired, or in person cash sales are needed. The Customer Support Portal also allows a true guest checkout option. No customer is created if this option is used. All customer information is stored only in the actual order information. There is a quick link in the Customer Portal Header menu that allows guest orders to be viewed separately from the rest of the store orders. Please note that in the ht_customer_service module settings there is an email field to fill out, by default it uses the store owners set email address. This email is used for certain functions within the Customer Service Portal, such as a placeholder email in guest account creation. It will always be populated on the guest customers information field, just to skip the additional step of gathering an email address from a guest. Whenever done with guest accounts, or even logging into an existing customers account always go back to the dashboard. This resets the session for that particular customer. If you are in a customers account, then you have to take on a session allowing you to access their info, the dashboard kills any sessions that are not related directly to you the customer service agent. If you are using the cash payment option, you will need to adjust the sort order of you order total module sp that the order totals and cash back amounts are computed correctly. Helpful Videos: https://www.youtube.com/watch?v=cwaid91cp1A&feature=youtu.be https://www.youtube.com/watch?v=dLgiD1FoTj4&feature=youtu.be Known issues: This plugin has been used in working shops for a number of years and proven to be stable. There are howver 2 issues I am aware of. 1) If a product in the cart has attributes, the update quantity field wont work properly. If a different quantity is desired, just delete it and add the correct quantity from the product listing itself. 2) I have not noticed this until testing on PHP 7.0, when using the cash payment option, the update button needs to be clicked twice. Feel free to post with comments or suggestions.

Thats pretty sharp looking. Good job.