• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Upgrade 6.1.0 to 6.1.5

    Big Smile...... V 6.1.8 downloaded and unzipped. Admin files renamed. Upgrade completed. All seems fine. No problems.....thanks Al and team. dave
  2. Upgrade 6.1.0 to 6.1.5

    Thank you Ian. I look forward to the new release. Dave
  3. Upgrade 6.1.0 to 6.1.5

    I must admit to being rather concerned about the number of problems that are reported. I was looking at manually upgrading v6.1.1 to 6.1.7 but do not want to risk losing all. I see that my admin folder has the new .xxxxxx suffix. Is it possible to do a new 6.1.7 install and tie this in to my existing database without losing the data? thanks Dave
  4. Need installation or upgrade assistance?

    Hi, Upgrade or update? My store is currently v6.1.1. Which plan would I need for you to carry out an update to the latest v6.1.7 ? Thanks
  5. SSL

    Noodleman & ian, Thank you both for your advice. I will go through each item suggested (woorank and google) to see if things improve. Thanks again. Dave
  6. Hi noodleman, Thanks for the reply. Your suggestion does work OK so many thanks. Dave
  7. SSL

    Hi All, I have recently activated an SSL certificate for my site and changed Dashboard>settings>enablessl : to yes. I hope it is a coincidence but my online sales have since bombed. Is there something I should check? Thanks Dave
  8. Hi Ayz1, Thanks for the reply. This was the first thing I tried but it didn't work. Dave
  9. Hi All, Would apreciate some advice. I use Galaxy skin but code is the same in Foundation skin. in: templates - content.checkout.confirm line 206 - contains <input type="checkbox" name="register" id="show-reg" value="1" {$REGISTER_CHECKED}> This adds a checkbox option "I would like to create an account." (checked by default.) to the checkout page for unregistered users. Assuming this does not break something else I would like this checkbox to be unchecked by default. If I delete {$REGISTER_CHECKED} this does the trick but I am not sure if this is acceptable 'codewise' or may cause other problems? Thanks Dave