Kryptronic Software Support Forum

Thanks Nick. That's got me on track.

Can you give me some pointers on the Custom Data fields in Inventory/Options. Not sure if I could use this option.

The problem with using options is that the Add To Cart button is hidden when viewing Catshow. I am sure I can overcome this...
However, I think it would be easier if I just add some fields that I can retrieve in addcart_internal and add to $addcartreq['addparams'].
Adding fields to prodlistitem.php don't seem to be passed to addcart_internal??

Very nice.  Like I said, there's a ton of ways to do it.  I assumed the adds were happening on the offer detail page.  I did eliminate the forms on those and went to a quickadd link, so as to clean up the HTML, as well as give options to add items from outside URLs using simple links (ala remote add to cart).

Concerning that filter, it wasn't very apparent to me at first how to change the sizing of the frames I was viewing and the filter seems to be the only way to do that.  If I were you, I'd move those inputs into each product offer list display, and allow editing right there, or make a big bold callout at the top.  Just a suggestion, awesome work so far.

I've been working on V9 for a few weeks now and am very disappointed to read from this post that Remote Add has been removed.

Remote add was very useful for our purposes because it allowed so much flexibility. Even though I haven't fully dived into the alternative solution, I can see how it can be made to work from an option selection that dynamically changes the price. However, one of the things that made remote add great for our purposes was once an option was selected, not only did it allow us to change the price but we were able to change the shipping parameters based on the inputted selections. In other words, remote add essentially allowed having a dynamic price and dynamic shipping fields (box dimensions, weight, number of items in a box, zip code it was shipping from and shipping method).

I don't see how the dynamic shipping aspect would be obtainable with the solution offered. Do you have any suggestions Nick?

Thank you.

Nick,

We use remote add in two ways:

1st Method - Very simple remote add of samples for the product. Code for remote add is in "product display" and pulls information from the database item to generate code. You can see it live in action  under the product image. I think this should be achievable with Inventory Item AddOns.

2nd Method - More complicated because product is made to order and has 4 tiers of options with each selection impacting the price and shipping. I was working on it in V8, before deciding to upgrade to V9. You can see a work in progress example . In this method, the database holds the first tier option (design) as a "display" item. The rest of the options are built out with remote add code in the "product display" based on the information of the "display" item.

In V9, I can see the first tier (design) being the product offer, and the 2nd tier (size - impacts shipping & cost) being inventory items. The third tier (finish - impacts shipping & cost) would be options to the inventory items. This is where it gets tricky because I can have the cost change, but not shipping. The forth tier (2nd finish option - impacts cost).

Ideally, all of this would need to be presented in a clean way too, as it can't just be a list of options running down the whole page. In V5.1 we did remote add and it was easy for customer to navigate, in V6 we went to a database format, which resulted in creation of too many items and being confusing. In V8 and V9 I was hoping to use remote add with an item as "display" to make it very easy.

What are you thoughts and suggestions? How hard would it be to mod back in the remote add?

Also, I can't seem to find min and max quantities in V9, did they get dropped too?

Thanks.

Method 1: I think setting those samples up as inventory items then using them as addons on product offers is exactly what you want to do there. 

Method 2: Look at custom packages of inventory items.  You can group them and make different selections.  Might be what you want to do.  I'm not sure if those particular panels are inventoried by finish or not, but if not, then those custom panels could use options for finish to do what you need to in a different way.

I have created a product offer and inventory item for each picture frame.

The frame designer page you we're looking at is a completely custom web page, but the frame lists are all pulled from the ecom_prod table.

The web page basically builds an add to cart form based on user selections. All the data and dynamic price is passed to ECOM_Cart when the form is submitted.

It requires major hacks that I certainly wouldn't encourage and would be frowned upon by Nick! but it can be done.

You can create a basic remote add form with a few extra hacks. Code below is for a basic add to cart form. You must create a product and inventory item with the correct id(I used 'custom1')

<?php

$this->globals('core.quickform_margin_none',1);
$formid  ='ecom--addcart';
$fields = array('SUBMITVALUE' => 'CART',
                         'referns'     => 'display',
                         'referref'    => 'custom1',
                         'offerid'     => 'custom1',
                         );

$this->xhtml_quickform_header('ecom--addcart','ecom','addcart',$fields);
     
print '<input type="hidden" name="pricecalc" id="ecom--addcart--pricecalc" value="111111" />';
print '<input type="hidden" name="ecom--addcart--pricemapid" id="ecom--addcart--pricemapid" value="DEFAULT-custom1-DEFAULT-custom1" />';
print '<input type="hidden" name="ecom--addcart--quantity" id="ecom--addcart--quantity" value="1" />' . $eol;

print '<button type="submit" id="' . $formid . '--SUBMIT">Basket</button>';


$ajax_extras = '{\'ecom_skinwidget_minicart\': {\'app\': \'ecom\', \'ns\': \'skinwidgetsid\', \'ref\': \'ecom.skinwidget_minicart\'}}';
$ajax_params = '{\'primary\': \'' . $this->xhtml_encode($formid) . '\', \'modal\': thisModalName, \'extras\': ' . $ajax_extras . ', \'formid\': \'' . $this->xhtml_encode($formid) . '\'}';
$js_docready = 'jQuery(\'#' . $formid . '\').submit(function(){var thisModalName = \'Shopping Basket\'; if (jQuery(\'#' . $formid . '--SUBMITVALUE\').val() == \'WISHLIST\') {thisModalName = \'My Gallery\';} return ajaxExec(' . $ajax_params . ');});';

$this->append_global_array('core.js_docready',$js_docready);
print '</form>';

?>

Post 2 above details the hack you need to make in ECOM_Cart.php to get the pricecalc field to override the inventory price when it is added to cart.

When you submit the above form, custom1 will be added to the cart with a price of 111111.

I have got lots of hacks for lots of different things. Prodlist has extra controls for maximum frame sizes, my own stock control system which is automatically updated every 30 minutes, different prodfilter system & a completely different wishlist system. Far, far too much for me to even remember what I modded them for in the first place.
Common.js was modded for various reasons, and I replaced the v9 kmodal with bootstrap modal.
I also completely reworked the Batch Order module as the BSM didn't work for me, and the POS module has been heavily modified to work with my custom items.
Amazingly the site all works correctly and was launched today.

Just to be clear, there is nothing wrong with V9. I just found it easy to adapt it to my exact needs and wasn't in any rush to launch.

I am dreading 9.0.2. Please take your time!! I am sure it will be a hell of a lot a work for me, unless you have got a detailed change list.

Amazingly the site all works correctly and was launched today.
I am dreading 9.0.2. Please take your time!! I am sure it will be a hell of a lot a work for me, unless you have got a detailed change list.

Congratulations on the site launch! 

I have a feeling applying 9.0.2 is not going to be a big deal for you.  There are a lot of changes to a lot of files, but changes to areas which you have modified heavily are minimal.   Meaning you'll likely have to do a line-by-line compare with a utility and merge in changes, but there won't be a lot of different logic to figure out.  The areas you've modded are all new to K9 and remain pretty much unchanged as far as logic goes.  The widespread changes in 9.0.2 are mostly related to speed enhancements, resource usage optimization and security.  Session management and the account area has changed dramatically.  There are at last count 72 functionality additions and changes, major and minor.  I think you'll be pleasantly surprised, and there will be a detailed changelog.

So you can get your head around this early, the main changes were:

- SIDs were eliminated completely as far as cookies, URLs, forms and JavaScript.  They are completely missing from 9.0.2.  No URLs, forms or JavaScript reference any markers which would identify the browser.

- 9.0.2 operates with a single URL, whether that be SSL (preferred) or non-SSL.  The ability to run mixed-content was completely removed. 

- Most items which were previously stored in a generic session in core_sessions are now stored in their own dedicated cookies, generally session cookies, but there are a few exceptions with time-based cookies.  Items like breadcrumb history, sort choices, etc. are all now stored by the browser in a cookie.

- User accounts now have all session-based storage in the core_users table tied directly to their account.  Items stored here include cart references, checkout information, basically anything that needs to be stored for the user account that is not present elsewhere in the core_users table.  Users get a special access token cookie upon logging in that's good for the browser session that identifies them.

- In the event session storage is needed for a guest browser, like when a cart is created or they enter information like a name or email address, start checkout, etc., that session data is stored in core_sessions.  Guests get a special session token which identifies their session and persists for 30 days.

Great lengths were gone through to optimize all storage for very busy/large sites and to provide a more secure operating environment which was faster and met the needs of current browsers and the current security environment.  You should be able to accomplish whatever you need to by simply updating the session or setting your own cookie with a gallery id.  Either way you'll be leveraging the all-new CORE_Session, but it will feel familiar.

sppars: Can't you just ceate an offer for one of the inventory item priced correctly? Everything will would work for you.  I'm not understanding why this is not an option for you.

When you say artcartquick function, are you referring to the art to cart function used in category displays whereby a href link adds to cart based on the prod id in the link?? If so, I think you would need different products for each sample as that method doesn't accept any options so you couldn't have 2 versions for the same id.

or do you mean you want to utilise the shopping cart modal pop up function?? If so, you can use this function via a form based add to cart method, or probably just by creating a ajax link with the correct params.