harmsmitsdev

Curious to hear why you think Adyen is shit?

Random API outages (without any reporting), bad SDK's available, no developer support. It makes it a nightmare to integrate and maintain. Besides that, the sales representatives are complete bullshit. Communication takes ~2 days to respond to a simple inquiry, for an essential part of someone's business that is just way too long.

On the other hand, Pay.nl has always responded to us within 15 minutes or so. They report outages directly to us (although they have not had one in a very long time), and keep us unformed when e.g. the api changes.

You all don't get it, new features and more features is the priority for cs-cart. Their mentality revolves around more and more bells and whistles so they can say our cart is capable of 1,2,3 and a.b.c and also x.y.z. Quality of product, good design decisions is not something they are interested in, and classic example is lite checkout. They tried to reinvent something as critical as checkout and messed it up big time. I am still running old checkout.  

Or really really maybe because writing a proper checkout is just hard and people don't report anything during the *beta* releases of these things. Who ever looks at dev.demo.cs-cart.com and checks if there is an issue or not with the checkout when they update it? They have asked for your thoughts many times already but no-one bothers to check it out, which is a shame really.

Of course both are to blame, but not like this. *YOU* want to upgrade without blinking. At least test it before you put it live, backup your database, etc. This is a *completely normal procedure* for any company that updates their software. No company thinks on a friday evening, 'hmm let me just update my main source of income because it got release yesterday'.

Nonetheless, CsCart should test their software more, especially with regards to things like order calculation. But the fact remains they can not account for *every* single variable. Even when using fuzzing or something, they will not iron out every bug you might encounter, as it is simply impossible with all variables that you have to account for.

It is one of cs-cart's shortcomings.  They will pay attention if you make a report against the most recently released version (maybe - new features get higher attention because they are more fun to work on).  But if you report an issue that is for any prior release, it can take months.  Cs-cart is not effective in evaluating newly reported defects to even get to confirmed/unconfirmed in a reasonable period of time.  The only solution is to contact helpdesk. But then the answer may be that "it will be fixed in a future release or looked at in 45 days".

 

This has been "normal" for the more than 10 years I've been working with cs-cart.

 

Good luck.

Then you should also know that as a developer you can submit patches for bugs.

It is `block_manager` not `block-manager`. Besides that, you should also clear your cache after changing those files or enable development mode and disable block caching.

app/addons/addon_name/schemas/block_manager/blocks.post.tpl

Furthermore, your schema should look as follows:

<?php

$schema['banners']['templates']['addons/addon_name/blocks/addon_name.tpl'] = array();

return $schema;

why we need this ? google analytic cant do that ?

Because ad blockers exist.

Great, thanks. 

 

That makes sense.   So you run the command line migrations on production prior to pulling in code changes?  I didn't realise you could run the database migrations separate to the code updates. 

 

The reason I wanted to use S3 was that we have custom addons, one of which is for our product brochures.  All brochures have 1 page, but in special circumstances, some products have a second page with more detailed product specs on them.  If a file is found in a particular folder that matches the product SKU, then this second page is appended to the PDF.  The reason I wanted to use volumes was so that management could FTP directly into the folder and drop the second page PDF files as they were generated...   But I gather the same would work for EFS.... 

 

How about deployment, do you use ECS for your containers?

 

I am trying to think of the simplest deploy method to aws.   Traffic to our site is about 20K users per month with session times of about 4 minutes which is pretty modest.   I keep thinking of dockerizing and using ECS, but maybe that is overkill. 

 

Currently i run mysql on the same instance as the website.  Although I think it makes sense to possibly push the database to its own VPC..  

 

I would be interested in your thoughts.... thanks again

For deployment we use EKS and ECS. It depends on the needs one customer might have. Kubernetes works amazing for websites that only need 3 or 4 application servers, whilst something like ecs is generally more robust and is used along with amazon rds & elasticache to build a store able to withstand the traffic of a few thousand sessions at once.

Besides that, kubernetes also works way better for cross-cloud. As you can easily take your business to azure / google cloud within a few hours. Which is something that a lot of customers also prefer.

Regarding the simplets method to deploy to aws. Just create an aurora database (serverless), with elasticache, and install cscart on a single server. If time comes for autoscaling, its not even that hard to set up at that point. As you will just need to create a docker container for your application and register it accordingly.

hi i have a product created with variation so its now 150 products different sizes and colors

see screenshot

 

how to change de color shirt in 1 time for a color

i tryed to select all sport grey and then change image all but then it change also for the rest of the products in the variation even the ones not selected

 

to do all 1 by 1 wil take alot of time when you have then 50000+ products

 

hope you have a eazy way to do this

This is a known bug in CS-Cart, will be fixed in 4.12

Hello,

About one and a half week ago, an SQL injection vulnerability located in the `Product of the Day` add-on caught my attention. Since then, the according changes have been made to the `Product of the Day` add-on from AlexBranding. Therefore, it is of the utmost importance that you update the `Product of the Day` addon.

My research has shown that this vulnerability has been present since at least version 1.4, therefore all those affected are urged to either disable/update the addon or contact AlexBranding at the earliest convenience.

Exploit details and research will be published later next month to give all those affected a fair chance at patching their vulnerable software.

Kind regards,

Has 7.4 now got offical support from cs-cart? I see there are compatability changes in 4.11.5 for php 7.4 - but I cant find any documentation on IF its officially supported and if so, what modules we need to enable.

No its not, there are still a few changes that need to be done before 7.4 compatibility. Most likely 7.4 support will come with 4.12, but don't take my word for it.

This is custom theme created from scratch.

Well, not entirely, you are literally using all the javascript provided by CS-Cart. But then again, rewriting all the frontend javascript is quite a hassle. I have been busy on a project for a while now where we are reworking the entire for frontend to vanilla js, and performance is significantly better than using something like jQuery.

Hello,

 

We upgraded to the newest version of CS-Cart Multi Vendor (V.4.11.3), but now our Checkout page is messed up. All of the content is hidden/blank. (See Attachment)

 

Is anyone else having this issue? Currently our entire marketplace is broken since nobody is able to purchase any products from checkout.

 

I hope someone here has an idea what is wrong. We can really use the help.

 

Jon

There is no attachment.

For anyone that stumbles up this in the future, the problem was SSL had to be enabled for NGINX on every server the request goes through before getting to CS-Cart.  CS-Cart gets confused if you try to do plain text behind, say, SSL termination at an AWS Elastic Load Balancer.  So, I installed my SSL certs on all NGINX servers and the crazy re-directing went away.

I went back through my git history and found that I changed the following in `app/Tygh/Bootstrap.php` at line 226. I changed 

self::detectHTTPS($server) && define('HTTPS', true);

to

define('HTTPS', true);

No offence but with 2 posts, can you post some examples of your work.

Depends, I could, but then I would have to chase all companies that just blatantly copy and paste code (if I were to open source it) without reading the license. Therefore, if you are interested in such things, shoot an email and I would be happy to help you out.

Regarding companies who use my solutions, I'd first have to check if they are okay with me making public that I manage their AWS cloud infrastructure.