clustersolutions

Yes, in short, copy and restore the catalog folder and the database backup and modify the configure.php as necessary for the store front and admin you should be good to go. Of course you will run into issues, just post the error message and I think it will get sorted out by the many experts here in the forum. Oh, this is what I would normally do. Get the new instance running first before the final switchover/destroying the original instance. Do the DB restore one last time, shutdown the original site, backup DB, and restore it to the new instance. Re-point your DNS if necessary...good luck!

I haven't looked at the 2.4 core yet. I like the app/market place and no core code change approach, and I hope there's plan to implement some kinda MVC/MVVM framework. The last I heard was making the BS official, and then moving it along to 2.4. We need someone who knows 2.4 and BS and map out all the tasks to modernize OSC, I should be able to pitch in. The hardest part is to re-architect/modernize the framework and making it more inviting to users and developers, and getting all those involved to agree.

Long thread, I hadn't read it all yet. How about the App Marketplace concept that Harold had started? And the framework...I wonder how much work to get there... https://library.oscommerce.com/Online&en&oscom_2_4&developers&framework.

Name a competitive cart out there that's not from a team effort? 6 yrs ago people tell me M was the shiz and I stucked by OSC. The last several eCommerce sites I had launched this year were all M2. Well, OSC is so far behind in every perspective that I am certain that no one man could be its savior. I am a full stack dev so I have a good idea on the amount of work that'd be required. I would help but the way was not clear. I think having that modular framework released could had give OSC a better shot, but it is what it is... Yeah, you'd cuss a lot in the beginning of your next cart, but soon you'd be cussing for not given some other cart a shot earlier. I chose M2, it is just awesome. Shiz just work right out of the box.

Well, complains are good. It helps you narrow down the problem. Check you file permission and etc. for 500 IE. The web server is complaining. If you have code error, then the PHP parser will complain. U may wanna hire someone to help you with this.

@azpro, ya, as "flexible" as M2 is, I say what we learned from it is conflict free extensions will be impossible here as well. I think install via marketplace vs. composer are fine. If I were to do OSC's frontend template system I would not make it that "rigid". Well, it just need a frontend and a backend frameworks, then may be it would be easier to get involved. I lost couple clients within the last twelve months, and they were taken to M1 and not M2. One was relaunched last month, and I found that to be interesting. On the other hand, I had just launched a latest M2 store two weeks ago. That thing was features rich and ready to go, so I just spent my time digging with customizing things that were necessary. That site had left Shopify because it did not offer the capabilities that it needed.

@auster, oh, better yet, try the BS version of the database.php and it may fix a lot of the complains you were seeing... https://github.com/clustersolutions/osCommerce-234-bootstrap/blob/master/includes/functions/database.php

@auster, well, leaving HG was the best decision for me especially I was paying for dedicated servers that were old news. It seems HG did provide you with PHP and Mysqli. Now, HG uses Centos, I recall, so they could easily install what you need from the repos. The problem was probably you are on a shared host it seems, so they can't configure the server just for you. Also, you really can't install mysql for php7 as it's deprecated. http://php.net/manual/en/function.mysql-select-db.php I think you are on the right track though, I would just go through the doc. It's not that bad I think you may just have to flip the arguments for mysqli functions when applicable. For example: // mysql $db_selected = mysql_select_db($dbname, $link); // to mysqli $db_selected = mysqli_select_db ( $link , $dbname ) So in your case to make the warning go away, // just add the $link to the argument if ($$link) mysqli_select_db($database, $link); Try it, it may work...and please refer to the PHP doc... http://php.net/manual/en/class.mysqli.php The function lists are on the bottom of the page... Oh, most of the functions that you need to mod to mysqli should be in this file.../home/pXXXl/public_html/pXXXt/includes/functions/database.php Good luck!

I imagine $$$ would be steadier with a day job. @azpro, I also imagine there's a happy middle between OSC frontend and Magneto 2's layout/template/block approach. I do like their factory/dependency injection approach. It's gonna be interesting to watch how many of their shops will move to the version 2, or ended up saying the hell with the version 2 upgrade cost and go else where should it ever became terminal and unsupported.

The community did something about OSC to move it forward.. but much needs to be done to make it a contender again... A stable framework to continue building it, no core code change required for both the frontend and admin. To me, things had changed a lot since the dot com boom. Most eCommerce sites profit margin is very slim, businesses probably put more emphasis on short and long term costs then features. One of the sites I mentioned above was on Shark Tank and had an investment from Mark Cuban. My guess was the cost has some to do with the switch.

@thadson, http://erikoart.com, is this your site? From your browser, go to developer->inspect element, checkout the console and network tabs (slightly different in different browsers). Use preserve log and disabled cache, checkout the cookie, it should tell you a lot on what went on during the checkout and aid in the troubleshooting...I'd start there.

Worth trying...go upstream of the addon and redirect all port 80 traffic to port 443 (https) in the Apache stack. Add this to your port 80/non-SSL Apache config file... RewriteEngine on RewriteCond %{SERVER_NAME} =socomtactical.net [OR] RewriteCond %{SERVER_NAME} =www.socomtactical.net RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] ^^^^may not be exactly but I hope you know what I mean...oh, .htaccess may work, too...BTW, you do know that www and non-www are considered to be different urls?

I was surprised to just had found two good $10-20mil/annual+ sites had switched from Magento to Shopify. So I did a little search and found this to be interesting. https://trends.builtwith.com/shop https://trends.builtwith.com/shop/osCommerce/Market-Share I can't tell you how they got their data. Magento's unease of use may be starting to hurt it's market share (V2 had a lot of changes). I've not been following eCommerce technologies for two yrs now...recently, I had to dealt with Shopify as it made some of the pass thru variables disappear. They had wanted us to pay $500 min to have their backend engineering to fix it. I guess that $500 min is still less than the cost of Magento. Ease of use and cost are important...

I think I may know the answer to this one. No!?

It's a matter of having options and for some of those long time OSC users being able to keep indexed URL the same moving forward would be highly desirable. I would work on it because I use it, but I found it hard to try hitting a moving target. Wow, three yrs had passed since I touched this repo...I think I stopped as I was waiting for the db module to finalize. https://github.com/clustersolutions/Ultimate_Seo_Urls_5_PRO_BS