CartThrob Bug Tracker

I’m using Solspace Super Search with CartThrob and Solspace calls the CartThrob extension, and the extensions gets its settings (calls _get_settings). SS calls cartthrob for every product. All fun and well. but this makes my template load about a second(!) slower.

If i uncomment the two commented rows, everything works as expected, but i dont know about any problems this may cause?

The Sage US gateway plugin is missing a language line for the newly added “test mode” setting. The radio box for settings displays properly in the CartThrob settings view but there is not language line showing what the radio box is for.

This is specific to the custom tweak Chris emailed me a few days ago but I thought it’d be good to put it in the bug tracker anyways.

Hi,

If you specify extra required fields either in the payment gateway plugin or in the required attribute of the exp:cartthrob:checkout_form tag, these are not checked at all.

It appears that if you enter an apostrophe in the ‘from name’ field when setting up a notification everything including and after the apostrophe will be deleted when you hit save.

For example, if you specified that emails should come from “Ted’s Widgets” then the from name would be saved as simply “Ted”.

When clicking the Preview button (or pressing ‘Enter’) when filling out the entry form for a product in Edit mode, the Carththrob Price Modifiers field type loses all input values.

The tax countries use 3 letter codes in the dropdown, but at least one customer was not using our country select tag, and was having trouble matching his 2 letter country codes to our 3 letter ones. We shoudl look at the US state codes, and see if any of them conflict with country codes. If not, our tax system shoudl look at 2 & 3 letter comparisons. Otherwise, at a minimum, we shoudl document that 3 letter codes are required.

_get_shipping_option()

does not return the default selected shipping option. It only returns an option that you’ve set using the front end.

{item_options:select:YOUR_OPTION_NAME }

also, there’s no example of a radio button