Wombat Beta 4 is out - PLEASE READ Part 1

[wcw]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

This is on the PLST page. See the page at http://www.pinemporium.com/mm5/merch...&Store_Code=PE The first item is inventory attribute. Most of the items are regular inventory. Then there are a couple that are not inventory controlled. As you can see the 1st item acts as if it is not inventory controlled at all. When I look at the raw variables it is inv_active=0 for that product, which many modules will think it means it is not tracked.

[Rick Wilson]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

Well until they pick an attribute it is untracked. If you just want to show it in stock, you can turn on inventory for that product, make sure you turn off low stock and out of stock tracking for it, so it doesn't interfere with your attribute variant tracking.

[Rick Wilson]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

Jon just pointed out to me that "he could even turn on inventory and set the "In stock" message to "Configure to see stock status" or something"

[wcw]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

More problems. Because the inv_active is not working you suggested turning on inventory tracking. So I turn on inventory tracking for the product. I put lots of stock in each of the attribute variants. But I don't want to display products that are out of stock in the PLST screen. So I select to hide out of stock. Guess what. The product does not display in PLST if the main stock level is 0, even though the attributes are plentiful. So not only is the function Runtime_Product_InventoryFields_Read not working as discussed above (so no avail message), but the query that pulls in the records is not working either.

I think what has to happen is that the variants need to be summed every time they change and they need to update the overall product inventory so it is cumulative. Then everything would be backward compatible.

Also, for CSSUI you recommended "Product List Layout template completely revamped, recommend regeneration". I have MMUI, does the same apply? If yes, how do you regenerate the page?

[Rick Wilson]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

More problems. Because the inv_active is not working you suggested turning on inventory tracking. So I turn on inventory tracking for the product. I put lots of stock in each of the attribute variants. But I don't want to display products that are out of stock in the PLST screen. So I select to hide out of stock. Guess what. The product does not display in PLST if the main stock level is 0, even though the attributes are plentiful. So not only is the function Runtime_Product_InventoryFields_Read not working as discussed above (so no avail message), but the query that pulls in the records is not working either.

I think what has to happen is that the variants need to be summed every time they change and they need to update the overall product inventory so it is cumulative. Then everything would be backward compatible.

This would create too much overhead to do for everyone as part of the core software. Especially because depending on how you're using it, especially with Kits, there may not be a definitive amount in stock. Such as using it for complex assemblies, etc... as there really is no master product in that sense.

However, Jon figured out a way today to achieve what you were looking for, with the current setup.

In the case of a "traditional" Inventory with Attributes scenario, such as say a shirt. You add the Master Product to each variant, so in essence it deducts 1 from both the cumulative master product count (which you need to set when creating this) and 1 from the specific sub product.

This way if you're buying a Black XL Shirt, and you have 25 total shirts in stock and 4 black XL's. If you set it up this way, the system would deduct 1 each from both counts and give you the control you're looking for. It would also allow you to dynamically hide the master product when all of it's sub products run out of stock.

[wcw]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

To clarify, when you update inventory with a new black XL shirt you add 1 to the master product and 1 to the black XL variant? Is that right? How does that work on flat file import?

[Rick Wilson]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

To clarify, when you update inventory with a new black XL shirt you add 1 to the master product and 1 to the black XL variant? Is that right? How does that work on flat file import?

That's right, in the flat file their 2 distinct products, so it's not an issue. In Excel you could actually write a little formula to sum all the sub parts up for you if you wanted.

[Rick Wilson]

Wombat Beta 5 is out - PLEASE READ

This stream will update Miva Merchant to Wombat-Beta-5:

We've also regenerated all of the previous Beta Streams to fix the failed updates on USPS, Google, and the encryption bug. You can now go from a fully up to date production release to the Beta and not fail or have any data encryption issues.

In addition if you have a Beta installation that has failed, please retry it now.

Finally the new LSK and Framework will be posted tomorrow morning.

Release Notes:

• Bug #4807: Edit Store > HEAD Tag Content/CSS...no validation of CSS file text field
• Bug #4928: prodimpt: "Update Existing Products" no longer creates new products
• Bug #5038: LaunchPad: "View Orders" link goes to legacy order processing screen
• Bug #5045: Orders placed from admin do not affect statistics
• Bug #5047: Orders created in admin do not trigger fulfillment modules
• Bug #5063: Default Country when adding an Admin side order is Afghanistan
• Bug #5086: Frameworks don't overwrite existing css files
• Bug #5087: Variant inventory is not properly reclaimed
• Bug #5088: Logout link appears on ORDH when not logged in
• Bug #5089: Long product codes/names make Edit Inventory dialog unusable
• Bug #5090: PLMT "Back" button goes forward, not backwards
• Bug #5091: Adding variants without having Attribute Values should error
• Bug #5092: Order History List and View Order components are missing the skins feature
• Bug #5094: Checkbox attribute with variants for only checked, possible load fails
• Bug #5096: Runtime >> Edit Product >> Textfield Inventory Variant has a timing issue
• Bug #5098: We need a better way to organize Product Variants on the Batch Edit list.
• Bug #5100: Infinite loop when no possible variants
• Bug #5101: Multiple boolean attributes can lock you out of certain combinations
• Bug #5102: Product List component not implementing it's point and click settings via framework
• Bug #5103: Category import does not allow deletion of custom field data
• Bug #5104: Import Customers from Flat File does not handle custom customer fields
• Bug #5105: Runtime g.json_url always uses secure URL
  
  
• Added the ability to configure a default variant, for products with no attributes or non-required attributes.
• Added an "Active" button to the product batch edit screen, to display only active products.
• Order History lookup by zip code and email address is now supported in MMUI.
• When importing a framework, the correct store ID and base URL are displayed instead of placeholder tokens.
• The attribute machine now has configurable text for the "Please select a valid combination of attributes" message.
• The attribute machine now displays a configurable message when a radio or text field has no value, and one is required. This message is displayed in the inventory div, instead of in the text field.
• The attribute machine now aborts in-progress state loads when initiating another one, and is more intelligent about initiating state-change requests for text attributes.
• Improved Void and Refund functionality for Innovative Gateway.
• A new tab, "Order Fulfillment Modules", on the order detail screen allows a user to manually trigger one or more fulfillment modules.
• Attribute inventory is now properly adjusted when manually adding, editing, or deleting items from an order in admin.
• In the add/edit item dialog, all attributes for a product are now automatically added when fields are auto-filled by typing in the product code or selecting a product from the auto-complete list.

[wcw]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

In the case of a "traditional" Inventory with Attributes scenario, such as say a shirt. You add the Master Product to each variant, so in essence it deducts 1 from both the cumulative master product count (which you need to set when creating this) and 1 from the specific sub product.

Rick,

Maybe I am not understanding what you are saying to do above. What does this mean "You add the Master Product to each variant"?

This is not working. I have downloaded beta 5. I put the 15 for the inventory of the master product so it would not be out of stock and would appear in the PLST. I then populated the variants and they summed to 15. Then I put 1 in the basket. The variant deducted correctly. The master product count did not change so it stayed at 15. Hence it is not deducting the way you described above. Then when I deleted the product from the basket, the variant was restocked and the master remained unchanged.

The availability messaging on the PLST, SRCH and CTGY screens is non-functional. More importantly, the ability to hide products from those screens when out of stock is not going to work either. You either need to dynamically sync the variant inventory with the master or stores will have to do it manually after each sale or there will need to be an incredibly complicated query when building the product array.

[wcw]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

Update: Rick went into my test store and setup the product so that the inventory would sync up. The PLST is working perfectly. Additionally, the Power Search is using the new inventory system to display or hide products based on stock status at the attribute level. Nice job Rick and Jon and the rest of the Miva Merchant folks. Thanks.

[Rick Wilson]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

We'll be posting some videos next week explaining some of these things, they tend to be easier to show visually then type out in a long missive.

Thanks for the Kudos Bill.

[Bruce - PhosphorMedia]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

Does this mean, that if a page has been created with the code FAQS and the customer does an update (and the default skin includes FAQS), the system would not overwrite the existing page, and/or not fail the install?

I know this tossing the life preserver out late, but this is why we always use more than four letters for our screen codes. Sort of like appending initials to functions, just in case someone else calls it the same. (And for SEO purposes, we spell out the page name. For example, frequently-asked-questions.

[Rick Wilson]

Wombat Beta 6 is out - PLEASE READ Part 1

This stream will update Miva Merchant to Wombat-Beta-6:

Release Notes:

• Bug #5107: Manage Orders >> Add Order >> Product Lookup fails to prefill the code.
• Bug #5109: Invalid selection resolution gets stuck with more than two invalid attributes.
• Bug #5110: Order_Update_Total was removed in Wombat Beta 6.
• Deployed mmui-orhl.mvt file which was missing in Wombat Beta 5.

[wcw]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

We'll be posting some videos next week explaining some of these things, they tend to be easier to show visually then type out in a long missive.

Thanks for the Kudos Bill.

I looked at the two videos you mentioned in facebook and that are posted on youtube. They didn't cover the trick you did in my test store to sync up the attribute at the main product level so that things like the product list and search would correctly hide or show based on inventory. Is that going to be in a future video?

[Rick Wilson]

Re: Wombat Beta 4 is out - PLEASE READ Part 1

Yes I'll get that up on Monday