clustersolutions

@JcMagpie yea, cultural change is next to impossible, I always say to give the customer what they want and not what one think is right. Also, I think with any implementation, its cost should be close to 50% of the total. A lot of small businesses do not realize that putting money aside for implementation is equally important as software/infrastructure cost.

Who remember Oracle's $1million challenge and it was about taking the canned codes as it and altering your corp workflow rather than implementing expensive customizations? That's is! Customers just hv to understand that one do hv to pay to play, and one should really try making COTS software works before any customization. It is not true that with Shopify you cannot customize. You can and it just cost money. We got a general quote from them once and the cost varies--$500 to $8k to start. In the grand scheme of things $8k is cheap when you compare it to an annual F5 load balancer contract, ~$4k per month...and that's just the load balancer...coloc, aws, or whoever, it can easily be another $10 to $20 k per month... Try using SW as it is best... And I've been saying let the framework people do frameworks...devs just focus on functionalities and codes...

Yeah, I ran a few Magento stores on an AWS micro or Digital Ocean $10 instances. Yeah, you want something more powerful during the development, but once it goes production with cache configured you can run them in micro instances. In a sense it is no more difficult than any carts. But should you need to run them in a cluster, it is a whole different ball game especially in terms of costs. Also, hiring a "good" Magento engineer/developer most likely will cost more than other carts. And as much as Magento has an awesome upgrade feature, but there are a few changes between V2 and V1 that are not making it easy on V1 with lots of customized features when it comes time to upgrade. So enter Shopify...running an eCommerce site is just that, and it should not be about "builiding software"...and let's pay someone else to worry about keeping my cart running in the cloud....

Laravel to me has borrowed a lot of concepts from Rails, but for PHP instead of Ruby. I remember all the talks about Ruby on Rail back around early 2000. Since Magento 2, I found a few Magento stores had went to Shopify instead of Magento 2. It probably make better sense in terms of total cost of ownership...just my guess...

Laravel, good stuff...

You can't do it. It needs the product id unique key. Now, you can put a unique index on the column that you want to use as your permalink, and then you should be able to convert the "permalink" desc to product id "upstream" of any "product_id" requirements and use it that way...that would be the easiest hack. But if you get a lot of errors as you are creating that unique index...you would have some cleanup work to do...by then you should know what I mean "it needs an unique key..."

@milerwan Ok, I have to check my Paypal setting... IPN disabled. PDT - Website payment preference -> auto return -> on -> back to checkout_process.php URL, PDT -> on. These should be the minimum, I may have to modify checkout_process to work with PDT...

@milerwan, hey, what verion of OSC and Paypal and etc. that you are using? Mine was on BS, probably Edge, and I had to reinstall Paypal somehow. Also, it seems that I had to setup IPN and PDT on Paypal to get it to work. Did you do that? I will have to look into it some more when I have a chance to remember what I did...LMK. Thx!

Well, I once heard in a TIM: "WHAT!? Engineers going off the tangent!?" It's really not as complicated as getting that damn CCGV to work!

I think it's a matter of store policy and work flow...the customer wouldn't owe anything until the time of purchase of the new "lesson." For us the store credit was the original order value minus the shipping and restock fee, and the customer was free to use it to buy whatever next.

@jimlongo , ah, you need a credit/voucher module. Someone was just asking about CCGV in this forum. Your customer is returning a "product", which you can issue a "pro-rated" refund to the account, a store credit. Now let them know the credit is in their account so they can go purchase whatever lesson it is that they want and apply the credit at checkout. That's how I had dealt with return/exchange, credit in the account, and cut another order and apply the credit at checkout. No mess...

I know, but it may give you an idea on what needed to be changed if you compare mine with the canned version.

PM me your email or something and I can send you a copy of my Paypal_standard.php file. You do have to hack it to work with CCGV.

CCGV, but I don't know which version is the best to start with, but you can hack the gift voucher side to generate credit for customers, once your get the module to work. The hack is simple. The gift card feature was never useful for me, sold zero gift cards anyway...I had used it for give me your email and get $10 credit in your account as well as for return/exchange and etc...

Hmm...true, clean code is important... I don't know if this banaid is better than the previous one, but they both offer a similar solution. I would really do a var_dump($text_array) or print_r($text_array) just before the foreach statement to get a stack trace of the argument. You really need to know why PHP was complaining. In fact, the foreach statement wasn't just looking for an array, and it was expecting an associative array. FWR is a smart dude, I would definitely understood why before deciding on a fix. That would be my approach...some upstream setting may just fix the warning.