Hello , I am very happy to say you that, saleor is very good option for small stores. but i want some more features like multi vendor, multi sellers in single site. multiple sellers can sell the products in one site, As amazon, ebay. Please try to develop these features in simple way, and easily anyone can understand.

Thank you..

Proof of concept implementation that limits the cost of paginated connections unless totalCount is explicitly requested.

⚠️ WARNING

• Not fully tested.
• Not sure if it's used by all connection classes.
• I likely don't have the time necessary to bring this into a mergeable state.

Fixes #4652 Fixes #2377

Pull Request Checklist

1. [ ] Privileged views and APIs are guarded by proper permission checks.
2. [ ] All visible strings are translated with proper context.
3. [ ] All data-formatting is locale-aware (dates, numbers, and so on).
4. [ ] Database queries are optimized and the number of queries is constant.
5. [ ] Database migration files are up to date.
6. [ ] The changes are tested.
7. [ ] GraphQL schema and type definitions are up to date.
8. [ ] Changes are mentioned in the changelog.

Is it possible to add guides for deployment on alternative cloud services?

I really like Heroku but I have an issue with how pricey it is to have SSL with a custom domain. Ideally, I would also like to host my Saleor instance on a different cloud provider, say Digital Ocean or Google Cloud Compute.

Does anyone have a written guide for alternative cloud deployments?

This is only a request. Thank you.

I am getting this error: ImportError cart: No module named prices

I found the source of the error: from prices import Price

this line is found on the following files: https://github.com/mirumee/saleor/blob/25adc3c8e840c81418833290a89e240baf7833e1/saleor/product/models/discounts.py https://github.com/mirumee/saleor/blob/fcf982842c2ad9f9795efe4b11d9dc3f9a251fba/saleor/product/models/variants.py https://github.com/mirumee/saleor/blob/214138810c1722f1b61e01c115eeecb362f93fb9/saleor/cart/init.py https://github.com/mirumee/saleor/blob/25adc3c8e840c81418833290a89e240baf7833e1/saleor/order/models.py

and I see that I cannot find this module anywhere as I did do a search. This is preventing me from syncing to the DB and getting this running successfully.

Let me know what is missing as I am still searching.

Hi,

I am trying to install saleor on my local machine. I followed the instructions carefully here http://saleor.readthedocs.io/en/latest/installation.html#installation. I even have a virtual environment as recommended by the Docs.

However, I cannot seem to have it up and running. I am using python 2.7, Django 1.10, pip 9.0.1. The first time I ran a migration, I go this error

ImportError: No module named dj_database_url. I proceeded to install it and other several modules that appeared as an import error when I tried to migrate but could not. I finally reached this module dj_cache_url but I get this error when i try to install it via pip

Could not find a version that satisfies the requirement dj_cache_url (from versions: ) No matching distribution found for dj_cache_url

Now I cannot pass the migration stage because this module has an issue. What could be the problem?

Add Avalara Avatax Excise (ATE) Plugin. ATE is an Avalara product that is effectively a wrapper around Avatax with some additional fields and logic.

Interesting things

• ATE REST API Docs
• ATE architecturally is a wrapper about Avatax. However it uses none of the same conventions between ATE and Avatax REST API's even though many of the fields are the same. For example ATE uses CaseLikeThis. This makes it almost but never quite like Avatax.
• ATE returns currency only on Tax Lines and not at the Transaction level. We assume the first line currency is the one to use.
• Some day we could consider refactoring Avatax and possibly writing it's init file with classes so that Excise can better extend it. ATE would then only need to override a few functions.

Limitations / work in progress

• ATE ProductCode is being mapped to Saleor's SKU. However ATE ProductCode has a very small max character length of 10
• Commit is not available yet due to limitations on ATE. A second PR will be submitted for this later once Avalara addresses this.
• Public documentation coming soon (Shared our internal docs with you already)

Using this plugin

ATE is a very new and enterprise focused product. Our design philosophy was to avoid any of our specific client business logic. However in practice, ATE must be integrated for each client. There's a lot of set up that happens on the ATE side such as mapping API custom fields, setting up SKUs etc. This plugin is not plug and play. However any changes necessary should include only adding additional ATE features and working with an ATE contact to set up.

Impact

• [ ] New migrations
• [ ] New/Updated API fields or mutations
• [ ] Deprecated API fields or mutations
• [ ] Removed API types, fields, or mutations
• [ ] Documentation needs to be updated

Pull Request Checklist

• [ ] Privileged queries and mutations are guarded by proper permission checks
• [ ] Database queries are optimized and the number of queries is constant
• [ ] Database migration files are up to date
• [ ] The changes are tested
• [ ] GraphQL schema and type definitions are up to date
• [ ] Changes are mentioned in the changelog

I'm not sure why this error is thrown. I can't find any account_user relation.

What I'm trying to achieve

To install the master branch ...

Steps to reproduce the problem

as provided by the documentation

(Please include a stack trace if this problem results in a crash.) [email protected]:~/saleor$ python3 manage.py migrate /usr/local/lib/python3.4/dist-packages/psycopg2/init.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psyc opg/docs/install.html#binary-install-from-pypi>. """) System check identified some issues:

WARNINGS: saleor.W001: Session caching cannot work with locmem backend HINT: User sessions need to be globally shared, use a cache server like Redis. Operations to perform: Apply all migrations: auth, contenttypes, django_celery_results, django_prices_openexchangerates, impersonate, sessions, sites, soci al_django Running migrations: Applying impersonate.0001_initial...Traceback (most recent call last): File "/usr/local/lib/python3.4/dist-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) psycopg2.ProgrammingError: relation "account_user" does not exist

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "manage.py", line 10, in execute_from_command_line(sys.argv) File "/usr/local/lib/python3.4/dist-packages/django/core/management/init.py", line 371, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.4/dist-packages/django/core/management/init.py", line 365, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.4/dist-packages/django/core/management/base.py", line 288, in run_from_argv self.execute(*args, **cmd_options) File "/usr/local/lib/python3.4/dist-packages/django/core/management/base.py", line 335, in execute output = self.handle(*args, **options) File "/usr/local/lib/python3.4/dist-packages/django/core/management/commands/migrate.py", line 200, in handle fake_initial=fake_initial, File "/usr/local/lib/python3.4/dist-packages/django/db/migrations/executor.py", line 117, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.4/dist-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.4/dist-packages/django/db/migrations/executor.py", line 244, in apply_migration state = migration.apply(state, schema_editor) File "/usr/local/lib/python3.4/dist-packages/django/db/backends/base/schema.py", line 90, in exit self.execute(sql) File "/usr/local/lib/python3.4/dist-packages/django/db/backends/base/schema.py", line 117, in execute File "/usr/local/lib/python3.4/dist-packages/django/db/backends/base/schema.py", line 117, in execute cursor.execute(sql, params) File "/usr/local/lib/python3.4/dist-packages/django/db/backends/utils.py", line 100, in execute return super().execute(sql, params) File "/usr/local/lib/python3.4/dist-packages/django/db/backends/utils.py", line 68, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/local/lib/python3.4/dist-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/local/lib/python3.4/dist-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) File "/usr/local/lib/python3.4/dist-packages/django/db/utils.py", line 89, in exit raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/local/lib/python3.4/dist-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) django.db.utils.ProgrammingError: relation "account_user" does not exist

I've been trying for several days now to set up saleor under Amazon Web Services' Elastic Beanstalk. I am getting the following error most of the time:

ERROR: Your requirements.txt is invalid. Snapshot your logs for details.

Here's directory structure:

├── .ebextensions
│   └── django.config
├── .elasticbeanstalk
│   ├── config.yml
├── .git
├── .gitignore
├── manage.py
├── saleor
│   ├── __init__.py
│   ├── settings.py
│   ├── urls.py
│   └── wsgi.py
└── requirements.txt

Here is django.config file inside .ebextensions:

option_settings:

aws:elasticbeanstalk:container:python:
   WSGIPath: saleor/wsgi.py
packages:
 yum:
   gcc: []
   python36-devel: []
   gcc-c++: []
   libffi-devel: []
   postgresql93-devel: []

Error:

-------------------------------------
/var/log/eb-activity.log
-------------------------------------
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 47, in _execfile
          exec(code, globals, locals)
        File "/tmp/easy_install-q1ck81sr/cffi-1.11.5/setup.py", line 240, in <module>
        File "/usr/lib64/python3.6/distutils/core.py", line 163, in setup
          raise SystemExit("error: " + str(msg))
      SystemExit: error: command 'gcc' failed with exit status 1

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1101, in run_setup
          run_setup(setup_script, args)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 251, in run_setup
          raise
        File "/usr/lib64/python3.6/contextlib.py", line 99, in __exit__
          self.gen.throw(type, value, traceback)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
          yield
        File "/usr/lib64/python3.6/contextlib.py", line 99, in __exit__
          self.gen.throw(type, value, traceback)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 169, in save_modules
          saved_exc.resume()
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 144, in resume
          six.reraise(type, exc, self._tb)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/pkg_resources/_vendor/six.py", line 685, in reraise
          raise value.with_traceback(tb)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 157, in save_modules
          yield saved
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
          yield
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 248, in run_setup
          DirectorySandbox(setup_dir).run(runner)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 278, in run
          return func()
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 246, in runner
          _execfile(setup_script, ns)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 47, in _execfile
          exec(code, globals, locals)
        File "/tmp/easy_install-q1ck81sr/cffi-1.11.5/setup.py", line 240, in <module>
        File "/usr/lib64/python3.6/distutils/core.py", line 163, in setup
          raise SystemExit("error: " + str(msg))
      SystemExit: error: command 'gcc' failed with exit status 1

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "<string>", line 1, in <module>
        File "/tmp/pip-build-y4onvdfc/cairocffi/setup.py", line 51, in <module>
          'test': ['pytest-runner', 'pytest-cov'],
        File "/usr/lib64/python3.6/distutils/core.py", line 108, in setup
          _setup_distribution = dist = klass(attrs)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/dist.py", line 315, in __init__
          self.fetch_build_eggs(attrs['setup_requires'])
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/dist.py", line 361, in fetch_build_eggs
          replace_conflicting=True,
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 850, in resolve
          dist = best[req.key] = env.best_match(req, ws, installer)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1122, in best_match
          return self.obtain(req, installer)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1134, in obtain
          return installer(requirement)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/dist.py", line 429, in fetch_build_egg
          return cmd.easy_install(req)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 665, in easy_install
          return self.install_item(spec, dist.location, tmpdir, deps)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 695, in install_item
          dists = self.install_eggs(spec, download, tmpdir)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 876, in install_eggs
          return self.build_and_install(setup_script, setup_base)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1115, in build_and_install
          self.run_setup(setup_script, setup_base, args)
        File "/opt/python/run/venv/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1103, in run_setup
          raise DistutilsError("Setup script exited with %s" % (v.args[0],))
      distutils.errors.DistutilsError: Setup script exited with error: command 'gcc' failed with exit status 1

What I'm trying to achieve

Install and run Saleor on Docker in production

Steps to reproduce the problem

1. docker build -t mystorefront .
2. docker run mystorefront:latest

What I expected to happen

Launch the store on port 8000

Screenshots

System information Operating system: UBUNTU 18.04 Browser:

General questions: What are the env variables that docker is using and how can I change them?

• refactor checkoutComplete mutation
• extract whole checkoutComplete logic to separate file
• use checkout_complete logic to create order from Adyen notification
• apply lock for handling the adyen notifciation and mutation checkoutComplete

npm run build-assets

missing script: build-assets did you mean;

build-schema build-mails

and when i typing python manage.py runserver only show me

http://127.0.0.1:8000/graphql/

what happen?

What I'm trying to achieve

Split up big queries like the ones for a product overview page with 100 items into many smaller sub queries that load data async.

Describe a proposed solution

Add new graphql @stream and @defer support to the saleor graphql server

Other solutions I've tried and won't work

Split up into individual queries would work but would increase the amount of work on the client tremendously.

I want to merge this change because it solves the issue described here: https://github.com/saleor/saleor/issues/11649

Impact

• [ ] New migrations
• [ ] New/Updated API fields or mutations
• [ ] Deprecated API fields or mutations
• [ ] Removed API types, fields, or mutations
• [ ] Documentation needs to be updated

Pull Request Checklist

• [ ] Privileged queries and mutations are guarded by proper permission checks
• [ ] Database queries are optimized and the number of queries is constant
• [ ] Database migration files are up to date
• [ ] The changes are tested
• [ ] GraphQL schema and type definitions are up to date
• [ ] Changes are mentioned in the changelog

What are you trying to achieve?

Order with two payments, where only one is active can show incorrect value as an outstanding balance. Order creation can cause an exception that products are out of stock. Because of this, we can have a payment fully paid, but without an order. Saleor will immediately refund the funds, but if Saleor receive the authorization notification for not active payment it will create a new transaction for it, and increase the payment.captured_amount

Steps to reproduce the problem

Reproducing is hard without touching the code.

• Saleor needs to capture the funds for the checkout
• it needs to raise an exception that the products are out of stock, and we cant create the order.
• The out of stock exception will trigger the refund.
• The notification from Adyen, about authorization, should not increase the amount of payment.captured_amount
• After receiving Authorize + refund notification, the payment.capture_amount should be 0

What did you expect to happen?

Payment.captured_amount should be 0

Logs

No response

Environment

Saleor version: 3.1.38 OS and version: …

I want to merge this change because it fixes an authorize-handler that was crashing when Saleor tried to create the order but it failed after processing the payment due to missing stock. Currently, we assume that we shouldn't try to create the order if we already stored the transaction with the same pspReference as the one from the notification.

It covers https://github.com/saleor/saleor/issues/11644

Impact

• [ ] New migrations
• [ ] New/Updated API fields or mutations
• [ ] Deprecated API fields or mutations
• [ ] Removed API types, fields, or mutations
• [ ] Documentation needs to be updated

Pull Request Checklist

• [ ] Privileged queries and mutations are guarded by proper permission checks
• [ ] Database queries are optimized and the number of queries is constant
• [ ] Database migration files are up to date
• [ ] The changes are tested
• [ ] GraphQL schema and type definitions are up to date
• [ ] Changes are mentioned in the changelog

What I'm trying to achieve

I want to allow a customer to provide inputs to the digital product they select, fields which conditionally cause next fields to show/hide, allow file upload, file download based on options.

Describe a proposed solution

Order should contain bundles of inputs, per customized product (downloadable). So that potentially an asset created, based on corresponding inputs, can be sent back to the user in fulfillment of the order.

Other solutions I've tried and won't work

It is potentially possible to extend using a plugin. If so I will attempt and link here. Otherwise can't think of any other option.

Screenshots or mockups

Demo of similar feature in shopify https://www.variantoptionproductoption.com/collections/examples/products/custom-jersey

Preparation to merge https://github.com/saleor/saleor/pull/11417

Issue: https://github.com/saleor/saleor/issues/11337

Impact

• [ ] New migrations
• [ ] New/Updated API fields or mutations
• [ ] Deprecated API fields or mutations
• [ ] Removed API types, fields, or mutations
• [ ] Documentation needs to be updated

Pull Request Checklist

• [ ] Privileged queries and mutations are guarded by proper permission checks
• [ ] Database queries are optimized and the number of queries is constant
• [ ] Database migration files are up to date
• [ ] The changes are tested
• [ ] GraphQL schema and type definitions are up to date
• [ ] Changes are mentioned in the changelog