Leaderboard

Thanks Martin, that fixed it for my customer's site. @saxcbr @Cary @cdetdi @Mac Fly please try copying the above file into your shops. You can then try resending an IPN from your Paypal account (finding it is tortuous): log in to PP, hit cog > Account settings scroll down to website payments on left menu choose Update next to Instant Payment Notifications in the middle of the first line of text, hit the link IPN History page This shows you a list of IPNs, defaulting to the last 24 hours - change the period if necessary and select one to resend [fingers crossed]

Hi all!! The idea of this post is to make it easier for new users who want to migrate to Phoenix 1.0.4.0, a list of addons available for free in the market, so that users can evaluate whether it is convenient for them to make a migration to Phoenix or continue in Frozen (which is stable and already has all the addons that an average user needs). I will list all the TESTED (by me) addons that are available. You can all publish the addons that you tried and are available in the market. Its prohibited : - Request support (for this you must go to the creator of the addon or the corresponding support page) - Mention addons that are not in the market The format for posting would be: Addon Name Link in the market Phoenix version that is certified to work Brief description of what that addon does Remember that the spirit of OSC is to share. love and peace Valqui

Dear Mark, ( @mfleeson ) Based on the OSC, many branches were created. For instance: ZEN Cart, oscMAX, Solomono, WamShop and many other e-commerce applications. OSC was an open and understandable textbook for many coders who, having learned how to work with OSC, later created their own codes based on OSC. All of them have turned into independent products and are developing independently. I greatly respect Burt for his support for the OsCommers. He does everything perfectly. Phoenix - is it the development and continuation of the OsCommers? I think yes. Therefore, the OsCommers tradition must be maintained. No need to divide the community into groups. No need to do confrontation and conflict. We were a democratic community and must remain so.

I think your missing the whole point of osC! osCommerce is released under the BSD licence and is open source so basicly is, Free redistribution of the software. The source code should be publicly available. The software can be modified and distributed in a different format from the original software. The software should not discriminate against persons or groups. The software should not restrict the usage of other software. If you care to you can read the full details here https://en.wikipedia.org/wiki/BSD_licenses As far as I know this has not changed... So yes jump in and get to know the code.....

A new version has been uploaded with these changes: Added gtin as an identifier. Added code for Phoenix compatibility. Installation just requires the files to be uploaded for Phoenix. Changed count code to pass php 7.3. Found by member @yahalimu. Changed default http to https in the googlefeeder file. Removed the code to check if mysql is being used. Mysqli is now required.

this add-on combines the shipping and payment page and can bypasses the checkout confirmation page as an option. there is no core changes. simply upload and install the header tag module two folders 4-5 works up to 1.0.5. 5.5 was tested on .2 and .5 https://apps.oscommerce.com/YzQoF&exp-checkout-1-2-page-checkout thanks to JcMagpie

v1.0.7.4 is tagged and announced; https://www.oscommerce.com/Us&News=166

I was not going to post in this thread again, since I sort of chimed in with the complaints. However, my complaint was centered around the frequency and speed of updates and my inability to keep up with a live store. I've since come to the conclusion that as a Phoenix Club member, I'm more directly exposed to the development environment than ever before and that was what was frustrating. Perhaps back in the day, 99% of us would never have been exposed to that and we were happy to implement major upgrades when they were announced (or not, as the case used to be). So, I'm trying to find my place, learn along the way, and hope that I can perform the major upgrades when they occur, as in 1.0.6.0, 1.0.7.0, etc. However, I do not know why anyone would think "Access to the code is severely limited." Perhaps becoming a Supporter allows one access to certain code, but the fund-raising is absolutely necessary for any of it. The basic Phoenix is still left untouched, consistently updated, and completely transparent. Meanwhile, there are many add-ons that are universally available and some of the key Phoenix Supporters/Coders take it upon themselves to keep them updated - for free.

Its not free because of only the coders. Its free because a very limited number of store owners and developers, have invested in the project financially so the coders can keep coding. If everyone subscribed to the theory that nothing is for free and contributed, then the project would be far further forward than it is now. Of the hundreds of users on this forum only a small proportion feel the need to keep the project moving forward whilst others sit back, criticise and moan. If they are not happy why are they using this software? We have no idea, but probably because they get something for nothing that earns them money. We all cannot expect coders to invest their time into a project which is freely given away without being able to at least get a meagre sum for their time work and experience. They could be doing fully paid work if they choose. Nobody works for nothing. No its not. Everyone can download the code for free from this site or from Github. What people cant get is what they don't deserve. Non contributors get the basic code base, whilst those that contribute get something back for their contribution. Its those that contribute and get the updated code early that are doing all the testing that is required before a release is made to the core files that are available to download from this site, which everyone can download. It really is that simple. Contribute and get rewarded for doing so. Its not difficult. Some should be thankful that they get what they already get. it could and should change in the future. Change the record and stop whining.

Agree 100% just dont have the time to keep updating every add-on every time the core changes. You just have to pick a point in time when its worth moving up but untill then it's simply best to state what version the add-on has actualy been tested on. In many cases the add-on may well work fine on a newer version of phoinex but unless the add-on has actaly been tested on it you can not claim this... Add to this that the number of people using Phoinex is low.... and among this small group the number moving to the latest version every time is but a hand full.....and the number using it for a live site?? unknown if any..... The need to rush and update add-ons to the latest release is not a big pull. So I would think those doing it out side the club will just do what they can when they can. I personaly simply pick a point in time to update to ( curently 1.0.4.0) and test my (very simple) add-ons to that version. Then when I update my test sites to a new version I check which still works and any new add-ons are then done to the new version. As and when a existing add-on is raised as an issue it is added to a list for update as and when time allows.

paypal.com.crt

Finally got Phoenix live and working as I want it. Now only updating if I want to add a feature. Leave it alone if its working.

It seems like every other question posted nowadays is about how to upgrade an older version of oscommerce and the op usually references the official version. This post is meant to provide a quick reference for how to convert an older shop to the current, recommended, one. First, the version that should be used is commonly called the Bootstrap, BS or Responsive version. It can be located here. One should not use the official version. The official version can be installed via the hosts control panel so it is easy to think that is the one to use - it is not. Since the BS version is not directly compatible with other versions, the following steps will be needed: Install the BS version into a new location Convert the database. See this thread for help with that. Install whatever addons the site needs. You need to be sure the addon will work with the BS version. This thread mentions specific ones but there are many others that will work. If in doubt, ask in the support thread for the addon in question. If you intend to use paypal, then install the Paypal App. At this point you should have a working shop. Test it thoroughly, especially the payment and shipping modules, before going live with it. When you are ready to go live, Mark your current shop as down for maintenance ( a simple index.html file is fine for this purpose ). Make a backup of the current shops database and files. Convert the database to the BS version. Replace all of the files with the new shops files. Edit the configure files so they work as the live shop. Remove the blocking page. If everything has gone correctly, the conversion should be complete.

I think what people are failing to understand is that Phoenix is sticking to it's opensource roots, anyone can download and install it. Those people that are paying are getting modules in exchange but also paying towards keeping Phoenix growing and therefore keeping it opensource. In an ideal world everyone who is using Phoenix would be paying to support it, they would get the modules they are complaining don't exist and more at a faster rate as @burt would be able to outsource some of the module development out so he can focus on making a better core.

I personally have a ton of gratitude for the work and the teaching the coders have done in this forum for years. I am not a coder, but I have always patched my store myself using the information available on the forums. I've even learned to figure a lot of the stuff out on my own too. I just took a leap of faith and jumped from 234bs to Phoenix 1.0.5.0. because I like the direction that Phoenix is taking and I needed to move forward. I am getting the Phoenix core code for free. A lot of people have worked hard on it and it's still free. Part of the deal is that I have to learn new stuff. Yes, folks, it's still free thanks to the coders. Thanks, to everyone involved in the project!

I think you're under estimating the pain of a broken shop here... Upgrades that you publish are excellent, but they don't come with (not saying they should come with) a list of stuff that will break if you install the update. As another owner said, if a shipping module is just outright broken, a 10 minute upgrade might turn into 1-2 HOURS of missed sales. And those are hours you don't get back - you still need to do shipping, inventory, payroll, customer service etc. In MY experience, being completely honest, upgrades are never 5-10 minutes, but typically 1-2 hours or longer. My shop is very customized, so don't take this as a complaint. This is sharing the fact that a small .x upgrade is a BIG deal for owners like myself. I'm hopping from frozen to Phoenix and it isn't painless. Stuff you expect to work just doesn't, and I'm updating/patching most of the things I use on the daily. I appreciate the move to "Approved Add-Ons", but I think it needs to go farther. If an add-on is "Approved" it must also mean that is is updated regularly - if it falls 30 days or more behind the current release it must loose its approved status. This means that users like myself can have confidence that we can upgrade to the latest release, with all approved modules in a timely fashion.

JcM index Specials BS Carousel V1.1 Has been updated to fix a few silly error and... Updated to introduce specials count as minimum of 4 specials required to display and more that 4 to animate. If less than 4 specials nothing will show.

No one should be upset by that. It is a good thing. Shop owners and developers just need pick the version they want to use or support and go from there. You don't need to follow every update as some seem to be doing and then complain to developers that add-ons are broken. Dan

I will be very happy to try it. It would be very nice to be able to participate. I suggest you to leave the club open so that many people can participate and promote your edition. I am anxiously waiting for news! Get on with your wonderful work. regards Valqui

No problem, I you need to show it on the product listing it can be done. It will how ever need some core changes as the best way to do that is to get rid of the product_listing.php and move that in to a template file in index_products. needs a new cm_ip_product_listing add-on and small edits to 3 files. PM me if you need this.

I am not a supporter of Brexit, but I would consider this lucky for the British. We are getting mad in Europe, looking at this example. For those 100 people we have to change our software? NEVER as far as I am concerned.

I still think that a better solution to this would be to fix the DIR_FS_CATALOG value in includes/configure.php to not change with the location of the calling page. Then you can leave the files inside ext.

Has been udated to add the Ajax state select on address edit in checkout and address book. Not super critical but hey it's done. Again will require 2 more core file replacments or edits so be sure you need this. Also cleaned up hook file to remove unused code a by product of copy and paste! 🙄...........I know not the first time and probably not the last...😳

Related Products Phoenix 7.2r1 tested and working error free with Phoenix 1.0.5.1