Jump to content

Dirty Butter

Moderator
  • Posts

    6,634
  • Joined

  • Last visited

  • Days Won

    139

Everything posted by Dirty Butter

  1. I created the order by logging in with a test customer account. I took it to PayPal, but then went back to the store. Then when I tried to change it to Processing, as if it had been paid - I get the error message.
  2. I thought the idea was to get a BCC, so I could easily reply to the customer to any email the admin received. I un-commented the debug lines in the snippet and tried Pending to Processing again. I still get the string of characters on a blank page, but there's more in the error log: Here's the snippet_3afa312cdc3acf2182d2144a8cfac7be.php as it reads now: <?php $this->_mailer->SMTPDebug = 2; $this->_mailer->Debugoutput = 'error_log'; $addBCC_notify_admins = explode(',', $this->_notifyAdmins()); foreach ($addBCC_notify_admins as $admin) { $this->_mailer->addBCC($admin); }
  3. I tested your code snippet today with emails as a customer contacting us, with good results. One plugin email did not BCC, but it actually only emails the admin, anyway, to notify of a new testimonial waiting for approval. So I would think it's outside the logic of your snippet. Going to test with some fake orders now. No such luck on orders. I get a string of nonsense characters ( PD9waHAKJHRoaXMtPl9tYWlsZXIgPSYgJG1haWxlcjs= ) on a blank page when the snippets are enabled and I try to change from Pending to Processing on my fake order.
  4. We only allow returns if our description is wrong - so rarely an issue for us. But I understand you would do it frequently. I'm not sure if this extension would give you what you want, but it's worth looking into: https://www.cubecart.com/extensions/plugins/return-merchandise-authorization-rma SemperFi may be able to modify the plugin to fit your needs, if stock is not sufficient.
  5. Well, Bsmither will be of help - me - not so much.
  6. YOU are not causing problems, lol, but something sure is!
  7. Note there's a section Bsmither provided that is supposed to keep Google from seeing those v4 url's. It has helped, but I sometimes still get warnings about the v4 url formed pages. I've guessed that it's a hosting blip that lets those old formed url's show momentarily.
  8. That sounds like your htaccess file does not have the Redirects working properly. Rename your existing .htaccess file. CC will create a new one with the appropriate standard values. Compare the entries in your own re-named one and the stock one CC creates. Maybe that will help you spot the issue.
  9. I have some core edits that add BCC to specific emails. I'll test commenting those out today and try the Snippet - hopefully it works!
  10. Put this wherever you want it in your print invoice: {if !empty($order.note_to_customer)} <p align="left"> <div id=" "> {$order.note_to_customer|nl2br}</div></p> <br> {/if} My orders.print.php is totally non-stock, but it fits our product and customer needs.
  11. Hi @Kent181 Welcome to the forums! There are huge changes in the coding from v3 to v6. What skin are you using? Could you provide a url for your store? Also, please create the error_log. https://forums.cubecart.com/topic/51550-how-to-create-the-error-log/
  12. There are free language packs in the Extension Market that take care of CC's own wording. Each Product Listing in Admin has a tab for Translations, so you can translate your product title and description as desired. The default language for the store is set on the General tab of Store Settings.
  13. LOL I didn't see an issue either, but I figured I just didn't understand what you didn't like about it.
  14. I was surprised with the admission as well! When I talked to them live, I played up being a Moderator on the forum and passing along info about other users as well as my own problem. It helped that Bsmither had an explanation of what was wrong!
  15. Got a reply from PayPal's tech support today. I had sent them a copy of @bsmither's explanation of the ampersand issue and solution, plus the data about the orders of ours that did not work. I also told them there were others on the forum here having issues. Here's their reply today: I've removed Bsmither's edit to see if we get any more IPN related issues, while I still have a PP support ticket open.
  16. There IS a message box per ORDER that saves to the database, shows in packing slip (I think that's stock) and customer's Order History, and can be added to customer Order Confirmed email. I print packing slips before order is completed, so I don't have the message in ours. If that's not sufficient, maybe someone will be able to help you code a better solution.
  17. So.... how do I do that? Would "escaping" solve the trailing space issue I have posted in another thread?
  18. You'll know soon enough if you keep watch on Google Webmaster tools: Add your store url to the end of this: https://www.google.com/webmasters/tools/html-suggestions?hl=en&siteUrl=
  19. My Search is not standard, but one that @bsmither worked our for me. But I've never seen this error message before. I can't find an entry for this time in our Users Online for bots and customers. It's the "Got error 'parentheses not balanced' from regexp " part that I am concerned about. Any idea what happened to cause that message? File: [catalogue.class.php] Line: [1901] "SELECT I.* FROM CubeCart_inventory AS I LEFT JOIN (SELECT product_id, MAX(price) as price, MAX(sale_price) as sale_price FROM CubeCart_pricing_group WHERE group_id = 0 GROUP BY product_id) as G ON G.product_id = I.product_id WHERE I.product_id IN (SELECT product_id FROM `CubeCart_category_index` as CI INNER JOIN CubeCart_category as C where CI.cat_id = C.cat_id AND C.status = 1) AND I.status = 1 AND ((I.name RLIKE '[[:<:]]puffalump[[:>:]]' AND I.name RLIKE '[[:<:]]cat[[:>:]]' AND I.name RLIKE '[[:<:]]for[[:>:]]' AND I.name RLIKE '[[:<:]]purchase[[:>:]]' AND I.name RLIKE '[[:<:]](not[[:>:]]' AND I.name RLIKE '[[:<:]]sold)[[:>:]]') OR (I.description RLIKE '[[:<:]]puffalump[[:>:]]' AND I.description RLIKE '[[:<:]]cat[[:>:]]' AND I.description RLIKE '[[:<:]]for[[:>:]]' AND I.description RLIKE '[[:<:]]purchase[[:>:]]' AND I.description RLIKE '[[:<:]](not[[:>:]]' AND I.description RLIKE '[[:<:]]sold)[[:>:]]') OR (I.product_code RLIKE '[[:<:]]puffalump[[:>:]]' AND I.product_code RLIKE '[[:<:]]cat[[:>:]]' AND I.product_code RLIKE '[[:<:]]for[[:>:]]' AND I.product_code RLIKE '[[:<:]]purchase[[:>:]]' AND I.product_code RLIKE '[[:<:]](not[[:>:]]' AND I.product_code RLIKE '[[:<:]]sold)[[:>:]]') OR (I.seo_meta_keywords RLIKE '[[:<:]]puffalump[[:>:]]' AND I.seo_meta_keywords RLIKE '[[:<:]]cat[[:>:]]' AND I.seo_meta_keywords RLIKE '[[:<:]]for[[:>:]]' AND I.seo_meta_keywords RLIKE '[[:<:]]purchase[[:>:]]' AND I.seo_meta_keywords RLIKE '[[:<:]](not[[:>:]]' AND I.seo_meta_keywords RLIKE '[[:<:]]sold)[[:>:]]')) " - Got error 'parentheses not balanced' from regexp
  20. This does NOT sound like a good idea to me! As for hiding the Billing Address section - maybe that is possible. But just commenting out that section would not be enough. There are fields there that have code in other places that verify the entries the customer makes.
  21. Title is not a required field, so you should be able to go into the appropriate skin file and comment out that section.
×
×
  • Create New...