saleor / saleor Goto Github PK

GET with a valid token should be enough to log user in and set an unusable password. The optional POST should check that the password is indeed unusable and change it to a valid one.

Then get rid of the second form in the template and instead provide a “Not now” link next to the “Set password” button.

Currently, even though I'm logged in via Facebook's OAuth, the /profile page still lets me change my e-mail and password.

It would be nice to have a variant system for products. Not sure if it's already possible, but from what I saw, it seems a bit complicated. I'd assume it would have to extend the 'Ship' model, but other than that, I'm not sure which way I'd go about building that.

With Django 1.6 sessions are serialized to JSON by default. We should only store necessary data in session and use the middleware to construct request.cart instead.

Some views should be available only via https. In most cases, that is, e.g. during development on local host that is NOT the case.

Suggested solution:

• view decorator that sets property "ssl expected"
• middleware that resolves path and check for the property on found view, and possibly redirects with appropriate protocol

The logic in registration module should be moved out from views to more suitable place we can test it more easily.

• Create order after success step,
• create processor for payments,
• save payments state into order.

Add simple push states:

• on order finish (addTrans),
• on cart add (addItem).

Anything not meant to be forked should be an external dependency so you can still upgrade them in the future.

• Add status changing in order,
• separate status between steps.

e.g. to "expiration" field of payment's form:
"01/15"

Hi,

Thanks for the repo. Please help me figure out how to use models inherited from Subtyped class. Any simple use case would be much appreciated.

Django error page has a lot of tidy warnings. They cover the traceback in the console.

No requirements.txt

ImportError: No module named payments.signals

How fix it?

We've tried to avoid it to make the store simpler but many people find this to be a disadvantage.

Currently we show a huge confusing form that allows you to both enter a new address and pick one from the list of existing ones.

We need an order handler object that decides what checkout steps are needed, validates them and returns the first step that needs user interaction (the next step to proceed to).

There should only be one choice field that offers "Enter a new address below" as the last option.

• Remove User relation form Addresss model
• add ContactBook model,
• replace billing address fields by relation to Address.

As the title states, you can set any address as default but it does not do a thing.

Use partition as a group class in create method.

I'd like to implement per user prices (or groups) in saleor. I'm not sure how I'd go about doing that. As a base, I'd probably attach a related table PricedItem that contains a reference to the user and a price field to my Product class. Then, I'm assuming I'd simply have to override the 'get_price_per_item' method of my Product class, so that it takes in consideration the currently logged in user. My problem is that I don't know how I could obtain the currently logged in user from within get_price_per_item and how I'd need to modify the codebase and templates to properly go about that.
Any suggestions ?

We should also make sure the demo site is nice and responsive.

We need to make sure saleor/saleor directory contains only installation-specific modules like settings, urls, wsgi, etc.

I'm not sure about where statics or templates should go.

Django forloop templatetag removes partitioner from context because __len__ returns 0.

To consider: https://developers.google.com/gmail/schemas/

Ideally you should only have to do:

$ django-admin.py startproject --template=https://github.com/mirumee/saleor/archive/master.zip myproject

Simple use get_delivery_methods from BaseDeliveryGroup.
Also create delivery group class for each delivery type.

RC1 was published today.

When your order exceeds maximum price that django-payments can handle, you get python decimal's error.

We need to watch total price for order in saleor and disallow to exceed it.

And lots of them.

Add order view in UserProfile.

When I use ForeignKey with the subtyped model I don't get suptyped classes in related_name query set.

Add simple user profile page with order list.

Use new communication model.

Currently they resemble breadcrumbs:

Lorem » Ipsum » Dolor » Sit

The problem with that is a short browser tab will only display the site's title so it would be impossible to tell two tabs apart. Ideally the favicon alone should be enough to recognize the site, we should make sure the title starts with the actual name of the page in question.

Add simple order admin page with grouped items.

https://www.easypost.com/

API: https://www.easypost.com/docs/python