keat

Premium Member
  • Content count

    1,175
  • Joined

  • Last visited

  • Days Won

    18

keat last won the day on October 20 2017

keat had the most liked content!

Community Reputation

18 Good

1 Follower

Profile Information

  • Gender
    Male
  • Location
    Leeds UK

Recent Profile Visitors

4,944 profile views
  1. Lost CC6 login details

    In PHP admin, forget the encrypted password, but take a look at the email address asscociated with the admin account. Try to log in to cubecart and use the forgot my password link. Input said email address and await futher instructions from the cart. If you don't have access to that email, change the email address in PHPadmin to one that you do have access to, and repeat the above. Alternatively, you may be able to find who hosts your original site by using something like this. https://gb.hostadvice.com/tools/whois/ Of course, this relies on you remembering the login details for the hosting plan.
  2. Lost CC6 login details

    Sorry, I assumed you might have known what PHPMyadmin was. Your hosting plan, (where the web site resides) should have a log-in to Cpanel or Plesk. Log in to this control panel and find PHP Myadmin application. When in PHP MyAdmin, locate the databse, and when inside the database find the table CubeCart_admin_users. Inside that table should be the login details that you're looking to find. If your'e not familiar with PHP-MyAdmin, don't make any changes.
  3. Lost CC6 login details

    Its in the databse. Connect to PHPMyadmin, take a look at the admin_users table, this will give you the logoin name and asscociated email address. Then use the 'Forgot my password' link.
  4. Rich Text Editor missing?

    In the short term, you could try uploading RTE from a different version, if you can find a different version still. I thought I had cpies of V3 on my PC, but it seems that I may have removed them. Maybe I might have some at home still.
  5. Customer records

    I can see GDPR being a right pain in the backside. The Act does not set out any specific minimum or maximum periods for retaining personal data. Instead, it says that: Personal data processed for any purpose or purposes shall not be kept for longer than is necessary for that purpose or those purposes. This is the fifth data protection principle. In practice, it means that you will need to: review the length of time you keep personal data; consider the purpose or purposes you hold the information for in deciding whether (and for how long) to retain it; securely delete information that is no longer needed for this purpose or these purposes; and update, archive or securely delete information if it goes out of date. We send customers regualr emails and catalogues, so I could argue, that I need to retain this data for the next 100 years. here's just one prime example. Look at the dates these orders were placed. 17-08-01 16-07-30 14-11-11 12-10-21 At what point do I determine that we should not retain this customers data.
  6. Rich Text Editor missing?

    PM sent. I'm guessing that this is verion 3, which version and revision is this.
  7. TLS1.2 compliant

    All present and correct.
  8. TLS1.2 compliant

    I received the following email from Pay360 this morning regarding updates to TLS. My server is TLS1.2 complaint (that i can gather) However, will this affect the payment gateway plugin at all. ?? Overview We are contacting you today to inform you of some upcoming changes to our infrastructure that may require action on your part. From May 2018, we are removing support for TLS 1.0 and 1.1 ciphers as they will no longer be considered PCI compliant transfer protocols. We are also moving to a new IP address range for both inbound and outbound communications. What is changing? We will be upgrading our external connection protocols by deprecating support for TLS 1.0 and 1.1 and enforcing TLS 1.2 communication for all inbound connections to Pay360. TLS version 1.2 has existed since 2008 and is supported as standard by most network devices and supported versions of all major operating systems. As part of the upgrade to TLS 1.2 we are increasing the size of some cryptographic keys that we generate - this is explained in more detail below. At the same time as the above changes, we are also moving to a new IP address range. This will affect both inbound and outbound requests. There will be more to follow on our new IP space in January 2018. And it goes on and on and on.
  9. Problem with Product Images

    nothing to see Phil In your cubecart admin panel, find a product with a missing image and temporarily allocate an image that you know works. for example, allocate the black retractable lanyard image to the cab carabiner keyring (as per your image in post 1)
  10. In Robots.txt I see Disallow: /images/cache Is there any reason why cache is disallowed. It seems to be having some sort of issues with google fetch and render.
  11. Blank products

    Session_gc_maxlifetime is 20 minutes by default. Any session that's opened and the mouse not moved or a click generated within a 20 miniute period is deemed stale by PHP and subsequently deleted. Although the 20 minutes has a second variable which could make this more like 40 - 60 minutes. I increased session.cookie_lifetime and session_gc_maxliftetime to 7 days (604800), which cured one problem relating to null products, but not all of them. I still see them. I guess it's possible that your customer added the two items to his basket and left his session open but untouched, PHP would then remove this as a stale session. The customer then came back finding his cart empty, and re-added them. Although, the experiments we ran a few months back, didn't show an empty basket. To the end user, nothing appeared wrong. If your customer will talk to you, it would be interesting to learn what those 2 items might have been, although in my experience I've yet to find a customer techy enough to understand the issue. @Al Brookbanks do you think reducing session.cookie_lifetime to a value slighty lower than session_gc_maxliftetime might help, or could this make matters worse.
  12. Blank products

    I see this quite often, and have no idea what's causing it. I think I have it narrowed down to one or two scenarios, maybe something to do with sessions or cookies, but i'm unable to recreate it. 1. Customer using a mobile device, adds items to his cart, minimises his session, (which is really easy to do on a mobile device) and then comes back to it after sessions_max_lifetime has elapsed. (sessions_max_lifetime is another story.) 2. or Customer adds items to his cart, proceeds with checkout and closes his browser. Something in the session doesn't clear down properly. When he later returns these become null items and are still lurking somewhere. I had one customer recently, says when he opened his browser, he found his previous order still in his basket, despite him checking out, and paying for this order, days previous. He cleared the items out manually. As far as he was concrened, these items had now gone. However, his order came through to us, with a dozen or so null items.
  13. Problem with Product Images

    If Bsmither has picked up on something technical, then I'd take his judgement over mine any day. However, I took a sneaky peak on your web and can see that some product images portray ?? Maybe if this was a database error, would it not affect all images. ??? Do the missing images exist in the images/source folder (view using ftp or cpanel/plesk file manager.) What size were those images, there's a limitation of about 350mb IIRC. if you exceed this limit, the cart will appear to upload them, but then put a X in the upload box, which is really easy to miss. I've fallen for it a few times. Did you move any images to another folder.
  14. It would give your customers a greater feeling of security and trust when buying from your site if it was https. Also, Google will soon start to penalise none https sites. I guess also with the new data protection changes coming this year, it wouldn't be a bad thing to buy. 1&1 offer ssl for £7.99 and then £23.99 per year after.
  15. being found by google

    Create a google webmaster tools account. You'll need to verify your URL with a small file download, and you'll also need to create a sitemap.xml file then submit this to Google via webmaster tools. Google may very well find you eventually, however, creating a webmaster tools account will reduce the process down to just a few days (maybe even hours) Don't expect to be No1 though unless you have some really unique search criteria.