Leaderboard

https://github.com/gburton/Responsive-osCommerce/releases/tag/2341-Frozen There will be no further Code Changes. Issues will be immediately closed. What is broken, stays broken. PRs will be immediately closed. What is now there, is there. Thank You to all Shopowners and Developers who have supported the Project in the last 4 and a bit years. Personal Thanks go out to all those Shopowners who were able to support my 28d bits and pieces for 3 of those 4 years - it is you guys who have made it possible for the hundreds of other Shopowners to continue using osCommerce. A big Thank You and from me, I will not leave you guys high and dry - you have my support always, we are a Band Of Brothers. Onwards!

http://template.me.uk/frozen2bs4/index.php I still have some work to do (especially on the modules for index & index_nested & index_products). Always moving forward, even if in "hiding".

In the last few weeks; index.php made more modular login.php made more modular checkout_success.php made more modular product_info.php made more modular + product info not found module as well product_schema module introduced introduced "actions" in application_top.php + new admin page for these actions category_tree class updated to pull more category data + most areas of code updated to use category_tree class template files renamed to help solve uploading problems hooks auto registered in each page Thanks to everyone who pitched in with ideas and code

Here's what I want to get done to set the Community Version to a "Final" release; 1a. Modularisation of index COMPLETE Title Standardise Module Name and Template Name (each) 1b. Modularisation of index_nested COMPLETE Title Standardise Module Name and Template Name (each) 1c. Modularisation of index_products COMPLETE @BrockleyJohn has coded, thank you Title Description Products 2. Modularisation of product_info COMPLETE Strip Schema Schema Buttons Date Info Options Description Gallery Price Name Model Not Found Message Standardise Module Name and Template Name (each) 3. Bootstrap v4 CANCELLED Updating full shopside to BSv4 4. php7.0 COMPLETE Updating full shopside and full adminside to be 7.0 compliant. 5. getContent calls DISCUSSION Discussion needed 6. Hook calls COMPLETE @raiwa has coded, thank you Auto Register Hook for each page What I don't have plans for, so will not happen; Everything else Why go "Final" Too many shopowners and developers wanting a fixed release; almost all feedback tells me rolling updates are not welcome. After "Final" No further changes will be made. Date for "Final" I was hoping to get it done by the end of this Month, but that is not going to happen. Sorry Folks, it'll be as and when I have time.

Today I decided I got angry for the last time updating a table rate based module. Afer several tryouts to change the shipping rates just to see I had a typo in the values string -damned colons- and having to manually calculate the net prices for each row from the gross that came from the table provided by the courier... I had enough and modified the table rate module to show a real table where you can see what you're doing. Uses some javascript to update net/gross, add or remove rows and do some basic checks. It can be adapted to any other module that uses the same system. Note: The net pice is caclulated based on the tax class from the module. It will apply only to the countries in the module's zone and it's not savet to database but calculated on the fly. For this column to work you need to set up the tax rate first, save and enter the module configuration again. Here is the file: https://apps.oscommerce.com/wyYLv&sgipping-table-module-update @burt you can replace the stock one if you consider it fits the community project.

https://apps.oscommerce.com/89uS9&modular-checkout-pages

Merry Xmas to all. Hopefully we all will have a peaceful week or two off and come back in 2019 with recharged battery.

Massive changes in bootstrap structure between v3 and v4. If shopowner is using an unabused recentish Edge or Frozen... drop on the new files. When...soon. Where...undecided. To whom...people who I feel are supportive. Next two projects are lined up which will radically change osCommerce for the better.

Shop owners ... Developers ... osC junkies ... We need your help! As many of you know, @burt has been instrumental in pushing the community build of osC. We are the community. And right now, @burt needs our help! @burt does not get paid for his work on the community build! To finance all of his work, he puts out an incredible assortment of modules, such as his current 28 days bundle. The money he gets from these allow him the time to work on the community build core. He is very close to wrapping up Edge, making it a fixed base of code, with only future hotfixes as needed. But, he needs our help. We need about 10 people (shop owners, developers, osC junkies) to buy into the current 28 days bundle here: This is a great bargain, fantastic modules (just check out what he's released so far!), great code (most require NO core code changes), *plus*, he does offer support and customization! So please, let's help @burt help us! (otherwise, he'll have to take a day job <gasp!>, while we all wait for Edge to be finished)

I don't expect this will be a publicly available thing; its a showcase of what the Responsive could (and should) have been had we got as far as Final. It will be available to some shopowners if they want it, but that will only be the handful of shopowners who are the diehard supporters of my efforts. Put simply; this is made to flatten my bsv4 learning curve.

That has not much to do with this forum, wouldn't you agree? We cannot take any sort of influence on Google's search results. I think you have been provided with help here and in the other thread (advanced specials). Unless for you getting help means having everything served on a silver platter for free. True. Not so many shop owners left anymore since osC doesn't evolve as fast as other cart systems these days. Still those who are left are not code-junkies. They are store owners that try to help osC move somewhat forward in any way they can in their free time. The first guy, his name is John btw, has provided you with a link to the answer you seek. You just need to know which link to click. Just try and click on the bold text BrockleyJohn replied to a topic The other guy, also named John, mentioned Burt by name because we all know who Burt is or at least those that use his Community Edition which would include you too. He is a osC Team member so just click on the "Staff" tab at the top and you should see a "monkey with a hat" avatar guy, that's him. Just a friendly advice. I know things can get frustrating if you try to get something working as quick as possible but bear in mind there are people here from all around the globe so there is a time difference to consider and consider that those people are trying to help here for free most of the time. So keep your attitude in check please and don't try to vent it out here in the forum.

Are you a shopowner? Help make the core osCommerce software better! This is the place where you can let the osCommerce team know about an idea (or ideas!) to improve the core software. First a definition: "core" osCommerce software is the package that is downloaded and installed by default. This isn't the place to write a wishlist of addons you'd like to see in the base osCommerce. Don't forget that lots of functionality is able to be added with addons that can easily be uploaded and turned on due to the modularity of osCommerce. The last thing we need is a bloated package full of "features" that will never be used by a large majority of shopowners. If you have an idea for an app, post it here. What is welcome here is ideas that can, for instance, make it even easier for addons to be installed. Perhaps you (or your developer) have found developing and adding a particular addon is too difficult because you need to dive into core code. In that case, let the developers know! Perhaps you can't find ways to turn things on or off. Or something you want to do is way too difficult because of the way the core code is structured. We as shopowners who deal with the day to day running of stores and have the knowledge as to how osCommerce can be improved for both us and our customers. This is our opportunity to have some input into the direction of the software. Anything to do with the core code that would make your life easier as a shopowner, let the team know by posting it here.

It would be nice to allow shopowner to select which module should be selected? SQL: Use phpmyadmin or similar INSERT INTO configuration ( configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ( 'Set Default Shipping Method?', 'SHIPPING_DEFAULT_METHOD', '', 'This will make shipping selection default to the selected method.', '7', '5', 'tep_cfg_pull_down_shipping_methods(', now()); CODE: /includes/classes/shipping.php Find: return $cheapest; Add ABOVE it: if ( defined('SHIPPING_DEFAULT_METHOD') && (SHIPPING_DEFAULT_METHOD != '--none--') ) { $shipping_method = basename(SHIPPING_DEFAULT_METHOD, '.php') . '_' . basename(SHIPPING_DEFAULT_METHOD, '.php'); for ($i=0, $n=sizeof($rates); $i<$n; $i++) { if ($rates[$i]['id'] == $shipping_method) { $cheapest = $rates[$i]; } } } CODE: /admin/includes/functions/general.php Add: function tep_cfg_pull_down_shipping_methods($shipping_method, $key = '') { $name = (($key) ? 'configuration[' . $key . ']' : 'configuration_value'); $shipping_array = array(array('id' => TEXT_NONE, 'text' => TEXT_NONE)); $ship_array = explode(';', MODULE_SHIPPING_INSTALLED); foreach($ship_array as $k => $v) { $shipping_array[] = array('id' => $v, 'text' => $v); } return tep_draw_pull_down_menu($name, $shipping_array, $k); } Note: Untested, but should work. Feel free to optimise it to something more elegant. If it works, you should be able to go to admin > configuration > shipping/packaging and select which module should be used

Need help? You've come to the right place. This post offers some general suggestions on how to get the help you need, quickly and efficiently. With over 1.6 million posts, your question has likely been asked and answered already so try searching the forums first. Using Google search generally produces the best results. In the Google search bar, just enter osCommerce and a description of the problem you are having or a likely topic for that problem and see what results are returned. You may get the help you need faster than you think. If you can't find the answer you need using Google Search then perhaps someone on the forums can help. Help is provided by volunteers, so please be considerate of their time, and provide as much information as possible. Here is a list of the information you should provide. Not all of it may be applicable to your particular situation, but providing as much detail as possible will result in a faster and more relevant reply. 1. Which version of osCommerce you are using? (you can find this at Admin > Tools > Version Checker). - Please provide the full version number, which is 3 or 4 digits ie 2.3.4.1 2. Also indicate whether you are using standard osCommerce or the Responsive (a.k.a. "Community Edition", "Community Supported") version. - If you are using version 2.3.4 or 2.3.4.1 and are not sure you can check whether your site is Responsive (mobile friendly) by entering your website address here. 3. Is this a new install or an existing store? - If this is a new install please be sure you are using the latest version of osCommerce which you can get here. 4. What version of PHP are you using? (you can determine this by looking at Admin > Tools > Server Info) - If your ISP has recently updated the version of PHP they are using, it can cause a variety of problems. Fortunately, recent versions of osCommerce have been updated to work with newer versions of PHP, so if you are experiencing issues with PHP, please consider updating your osCommerce software. 5. Now you are ready to provide a detailed description of the problem you are having, including if applicable, the steps needed to reproduce it. - Providing a link to the page where the problem can be seen or if you are receiving an error message, a screen shot or the exact text of the message displayed is extremely helpful. The more detailed information you can provide the better. Be sure to obscure (***-out) sensitive information such as your server account name. If you need to show your configure.php file(s), remove or obscure the database name, user, and password! Now that you've gathered the information needed, you'll need to decide where to post it. 1. If the problem relates to an add-on that you downloaded from the apps area please see if there is a support thread for that add-on, and if so post your help request there. Often the authors of the add-on monitor their support threads, and you'll get the quickest and most appropriate response there. 2. If your problem relates to a 3rd party product or template that you acquired elsewhere, then you should go back to the author or vendor of that 3rd party product and ask for help there. They will be in the best position to help. 3. All other requests for help should be posted to the General Support forum. Start your own thread instead of posting to an existing thread, even if they seem related to the problem you are having. Your problem or the version of osCommerce/PHP you are using may be different and only serve to confuse others who are seeking help with a similar problem. Ask a new question. If all else fails or you need help updating an older add-on, or perhaps creating a new one, commercial support is also available. Requests for commercial support can be posted here.

Visually, I think everything looks better. Functionally, the code is cleaner & faster.

All New Cart Page

As a store owner, I don't want to have to visit Github (or wherever) to see if there are any patches I need to apply to my live store(s). For me, I was very happy when Edge/Final/Frozen was 'finished'. That's not to say that there aren't any bugs still in it. That's the reason for this thread ... a place to document bugs, and hopefully fixes. I am also pleased that development is still happening. Keep it up, guys. Use this thread as a source of information to improve your forks. But please, for this thread, let's keep it just for Edge/Final/Frozen, ok?

I've been thinking of doing the same. Here are some changes that should be made (not all are mistakes): 1 - In includes/modules/content/product_info\templates/tpl_cm_pi_price.php, the variables in sprintf are in the wrong order. Change <h2 class="h3 text-right-not-xs"><?php echo (tep_not_null($specials_price)) ? sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY_SPECIAL, $specials_price, $products_price) : sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY, $products_price); ?></h2> to <h2 class="h3 text-right-not-xs"><?php echo (tep_not_null($specials_price)) ? sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY_SPECIAL, $products_price, $specials_price) : sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY, $products_price); ?></h2> 2 - In languages/create_account_success.php change priviledges to privileges. 3 - In languages/shopping_cart.php change two instances of "don't" to "don\'t". 4 - In languages/shopping_cart.php change "immediate deliver" to "immediate delivery". 5 - In includes/application_top, add the deprecated flag to prevent future warnings and disable display errors since it is a security hole by changing error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); to error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT & ~E_USER_DEPRECATED); ini_set('display_errors','0'); 6 - In includes/template_top.php, change the version number to the current one because some icons being used won't work in V 5.0.6. <script defer src="https://use.fontawesome.com/releases/v5.0.6/js/all.js"></script> to <script defer src="https://use.fontawesome.com/releases/v5.0.9/js/all.js"></script>

Ive said it before and I shall say it again Thanks Gary @burt for what you have done. Its a shame that others were not prepared to help you a bit more whether it be coder, developer or shop owner. Its a shame that it has come to this, but it had to happen one day. It could have been 4-5 years ago, but you saved the project as best you could. There seems to be some support from a few coders in this thread so may be its their turn to commit and move the project forward. Lets see what happens. I expect nothing.

It will happen only if Harald (who owns osC and this site) wishes for it to happen. He has given no indication that he does. Last August he promised a 2.3.5 upgrade release of some sort, and 2.3.6 (the CE version), within a few weeks, and it's been 8 months now. No one has heard from him in over 3 months, and we're starting to wonder if he's still above the grass. Anyone holding their breath, waiting for something to happen, is very blue by now. Most people have given up and are moving on to other projects. It's unfortunate, and even tragic (given the amount of work that he and others have put in), but he just does not know how to run a major project. You can not disappear for years at a time, crafting your solo personal project to perfection, and then suddenly present it for the world to ooh and aah over. The current offering has to be kept alive and updated and supported, and this just has not been happening.

Now that oscommerce community version allows more an more addons with no core code changes I feel an uploader/installer would make things simpler and also help a lot those newcomers that does not have the knowledge to ftp files. We don't have a repository adapted to it, but we could ideate a simple system that allows to upload a zip file by browser, uncomprees it, do some preliminar checks like if the addon is currently installed and is compatible with the system and with copying files/making registry entries when user press "install". Been playing with the idea of something like the paypal app updater and came up with this: Would like to get feedback from developers about it. It would need, of course, that developers agree with packaging the addons with a certain structure and provide with a file that performs the tasks. Do you consider interesting to make a similar system?

Many of you may be thinking..."whut?" but ... I promise you ... Core Code Changes are possible. Every single change I (and others) have made to the Community Edition, is a Core Code Change. Typical examples; @Tsimi and I found a bottleneck in /includes/application_top.php. Fixed! @BrockleyJohn wanted some extra getContent calls. Done! @raiwa wanted auto included hooks. Done! more examples if you want them So long as what is asked for, makes sense...

Great, thank you. Will guarantee this goes into Core when you guys are ready to push it. We can also revisit the modular Cart (I will open a new discussion for that one in the next days).

Interesting debate ... As a shopower I learned myself the skills to maintain and develop code for osCommerce ... The past 14 years or so I have looked at different carts from time to time (Presta - Magento - osC V3 - Shopify - etc.). For most of them - started a test shop - looked into the code - and especially tried to make an analysis of the eco-system. Believe me - it doesn't get better! Off course the lack of a roadmap (time table) is killing oSC. If Harald just/only would share his direction and objectives - a lot of community members could do a vast amount of work to bring oSC to a higher level. THANKFULLY @burt started his community edition - he did a massive job. But - if I understood right - the lack of support from the community (donate money - test - give feedback etc) made Gary decide to stop further development. And that's a shame! As I said - it doesn't get better with a different cart. osCommerce is the only true Open Source Cart in my opinion/experience. Easy to maintain for different skill levels of coders. Compare this to Magento ... a nightmare in debugging ... You probably end up with a professional that's gonna cost you a lot of money. And they (also) went from V1 to V2 leaving all your extensions useless. So - off course it's important to look around and keep openminded for different carts. But as long as osC keeps developing - even at a slow / minimal pace - I prefer to stay with osC. Hope this helps to convince some people to donate @burt so maybe he will reconsider ... just look in Github what he @BrockleyJohn and @wHiTeHat Henry did the past days https://github.com/gburton/Responsive-osCommerce/pulls

I am one of those who already receive Burt addons. To be honest, I was skeptical at first because I paid for addons "mystery" since we do not know the addons in advance. Well I can tell you that I do not regret it! It's well coded, it's clean, efficient and when needed, Burt is really available. Sincerely thanks Burt!