i think i have spoke too soon... the following has started to happen only after installing the gird add-on
now on test purchases i get this pop up warning when i add something to the cart
Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party.
and also when i go to the checkout
i get this.. Payment Method
Sorry, we are not accepting payments from your region at this time.
Please contact us for alternate arrangements.
any ideas?... would like to clear this up before i add it to the list
mysql = 5.2.9
site = 1.3.9b
Are you sure you want to continue sending this information?
Shane78:
i have just had a small heart attack!
In rebuilding my main live shop, i require my customer settings to be
Admin>Configuration>Customer Details>Customer Shop Status - View Shop and Prices = 2
and
Admin>Configuration>Customer Details>Customer Approval Status - Authorization Pending =2
as it's a closed B2B site...
i installed Product_Attributes_Grid 1.1.1 on three test sites and all worked... then on my main site and i was returned this on the product page
1062 Duplicate entry 'CONFIG_ATTRIBUTE_OPTION_GRID_INSTALLED' for key 2
in:
[INSERT INTO configuration (configuration_title, configuration_key, configuration_value, date_added) VALUES ('Attribute Grid Installed', 'CONFIG_ATTRIBUTE_OPTION_GRID_INSTALLED', 'true', now())]
after a small heart attack and a small mess in my pants and letting the sadness and rage pass.. i tested my other stores, changing the customer setting to those above.. realising that it worked i went back to my LIVE site, turned those setting off and reverting it back to a normal B2C type site.. tested it worked... then turned those setting back to a B2B type site and it works as it should...
I have learned three lessons
- make your test site identical in every way, right down to the smallest of admin settings
- dont panic
- dont drink so much coffee in the morning, as the PC almost went through a wall, along with my chair and desk when I seen that SQL error!