Drupal Commerce Issue Queue

A little background: we play tug of war with the number of fields (fields not instances) ever growing on our site and the performance of having those fields specifically in the checkout process for a commerce order. I was curious if defining these field within the specific .tpl file would 1) Alievate this problem with drupal and the fields vs performance tradeoff, and more importantly 2) Not break the drupal commerce order.

Such a field would be added to the order array as $order->my_field. I guess I am asking how commerce order would react and if the data would still be saved properly, such that the field does not possess its own tables and is almost invisible to the overarching drupal.

Hello there,

I'm running in a very strange 'bug' with the javascript in commerce checkout which disables the button to avoid it's clicked twice.
It seems this javascript also reacts on pressed 'enters'.

This conflicts with an autocomplete in the checkout-pane's. When you use an autocomplete (to be precise, for an entity reference) and you type some first letters, the autocomplete shows some options. If you choose an option with key arrows and press enter on the selected option. The commerce checkout javascript is also called, which disables the option to goto to the next step.

Selecting the autocomplete option by mouse, doesn't trigger the javascript (which is offcourse good). Using an enter in a textfield, also doesn't seem to trigger the javascript.

I have absolutely no knowloedge of javascript, but seems an extra check to see, if the pressed key comes from the submit button may be the solution.

Hopefully my issue is clear.

At the top of the view for admin/commerce/orders we have a button to create an order in the admin backend as opposed to through the checkout process. Where is this button generated? My issue is when using the order types module in conjunction, each order type gets its own create X button at the top which can pose a problem. I would like to override this to limit the buttons to a particular set or possibly change the button to a select list.

My hunch is that this is drupal core generated, but where do I find / hook to override it and restore the clean nature of commerce order?

Hello,

I don't know this is the right place to ask it. I have to build a inventry for a library system. Where I will have different copies of same title, so I want to keep unique identifier for each copy and keep that as SKU for the item. I will have some other atributes too.

My all book will be listed even if no item of a title is in inventory, user can add it in his/her wishlist(my account) section. But when he try requesting the bundle( 2 items one time), only available title will be shown to him from the wish list.

At admin side I want the request to be listed and for each title available SKUs in select list. I will select one SKU & close the request & it will make that SKU unavailable from the inventry to be requested next time till I update this to be available.

Any body can suggest me anything regarding this...like how it can be done with drupal commerce? Whether it can be done or not by available modules? If I get to code...how much things I am already having in this contributed module for this kind of system..

I am newbie to Drupal commerce so I am not able to figure it out..

Thanks

I am writing a module called Commerce Product Add-on that puts products as add-ons on the Add to Cart forms of other products. It works for the most part.

Part of what it does is add another view mode for product entities. This view mode is used for this context.

We call this to add the displayed product to the form.
entity_view('commerce_product', array($product_add_on->product_id => $product_add_on),'commerce_pado');

However, for people without the View Product permissions, like anonymous users it throws an error.

Now, this might be related to the entity api module. Not sure exactly.

But is there a way to bypass the access permission for just this view mode? Because the error goes away when I set the permission I. I'd rather not make that a requirement. Just asking for insight.

Thanks!

•I am setting up a site using Drupal Commerce with three different product groups defined by both product and content type
•Each type has 80 individual products
•A portion of these products are variable – meaning that I am consolidating them by allowing multiple values in the product reference
•When I was in Drupal core version 7.19 I was able to see all 80 product references to select from when creating display nodes
•Now that I am in Drupal core version 7.2 the list of available product references cuts off after 50 items
•So for example if I delete product #1 then product #51 becomes visible – and it doesn’t seem to matter how many different product and related content types exist
•However if I create the products via a feed they still create just fine with all the relevant information
•I can see a work-around by fiddling with the sequence of the products listed in my .csv so that the “individual” products come after the 50 item cut off, but it seems less than perfect

This appears to be related to the file at: commerce/modules/product_reference/product_reference.module

at this line:
function commerce_product_reference_options_list($field, $instance = NULL) {

changing the line to this:
foreach (commerce_product_match_products($field, $instance) as $product_id => $data) {

addresses the problem on my local server, however does not work when attempted on a development site on a shared server

I have just upgraded to commerce 7.15 and Drupal 7.20 and have noticed the following issue when trying to set the default product display type to my commerce product - the quick reference default collapsible block is no longer present (see screenshots before and after) - /admin/commerce/products/types/product.

I have an old version of the site running on 7.15 and commerce 7.x-1.3 which does have the functionality present (not sure at which point I lost it).

I have approx 16 product content types - a simple original one with standard fields that is for products that do not have attributes so therefore 1 to 1 relationship commerce product to product display, all the other templates are for various attribute driven products that have different fields e.g. colour, length, grade, height etc etc. This has all been working well and I have been using commerce feeds + tamper to import approx 10,000 products of various types.

Today I went to create a new product manually and noticed that when choosing the standard product display from content > add content > product display (also using inline entity form 7.x-1.1) when I go to create the commerce product from within the inline entity form it is not showing me the standard commerce product type but one of my custom commerce products with additional fields instead. As the quick reference default option has disappeared I cannot check and rest the relationship between my product display and my commerce product.

I am using an omega responsive sub theme and also have a multisite attached which uses its own database but shares the same codebase.

Also using many contrib modules but very little template customisation. My modules are mostly up-to-date with only a few out of date. Unfortunately I cant display a link as its on our dev box and firewalled. Included contribs (not extensive):

• inline entiy form
• commerce UPS
• commerce extras
• postal code filter
• sagepay direct
• commerce Checkout Progress
• Commerce Extra Price Formatters
• Commerce fancy attributes
• Commerce Search API
• Commerce Wishlist
• Physical Product
• Product Attributes
• Database search
• Search facets
• Search views

I have to say I'm majorly impressed with where commerce is right now and the number of contrib modules now available...

Due to go live in 3 days so any help appreciated!

EDIT:
I have tried commerce repair...