Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

veganline

Members
  • Content Count

    267
  • Joined

  • Last visited

  • Days Won

    7

veganline last won the day on August 8

veganline had the most liked content!

Community Reputation

46 Excellent

About veganline

  • Birthday 05/17/1964

Information

  • About Me
    https://veganline.com - I sell shoes among other odd jobs. My short term memory and concentration get better each year, but I do tend to revise posts. Hope this is harmless! My list of modules is on https://forum.thirtybees.com/topic/5114-modules-lists/?tab=comments#comment-41019
  • Website

Recent Profile Visitors

1,300 profile views
  1. You've solved it! I had BCC all emails turned-on under Advanced Parameters > Emails When I turned it off, the error message was gone. I'll PM access to the back office in case there is anything you're curious about.
  2. Might be relevant: I have some override files. I do not know where they came from. AuthController.php 33.4 KB Today, 12:10 PM OrderOpcController.php 39 KB Today, 12:10 PM ContactController.php 3.1 KB Sep 17, 2021 ------------------ Swift_RfcComplianceException: Address in mailbox given [] does not comply with RFC 2822, 3.6.2. in /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php:345 Stack trace: #0 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php(261): Swift_Mime_Headers_MailboxHeader->_assertValidAddress('') #1 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php(106): Swift_Mime_Headers_MailboxHeader->normalizeMailboxes(Array) #2 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php(63): Swift_Mime_Headers_MailboxHeader->setNameAddresses(Array) #3 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMimeEntity.php(592): Swift_Mime_Headers_MailboxHeader->setFieldBodyModel(Array) #4 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMessage.php(432): Swift_Mime_SimpleMimeEntity->_setHeaderFieldModel('Bcc', Array) #5 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMessage.php(412): Swift_Mime_SimpleMessage->setBcc(Array) #6 /home/veganlin/public_html/classes/Mail.php(293): Swift_Mime_SimpleMessage->addBcc(NULL) #7 /home/veganlin/public_html/classes/module/PaymentModule.php(1099): MailCore::Send(1, 'order_conf', 'automatic ackno...', Array, 'shop@veganline....', 'John Robertson', 'shop@veganline....', 'Veganline.com', NULL, NULL, '/home/veganlin/...', false, 1) #8 /home/veganlin/public_html/modules/stripe/classes/PaymentProcessor.php(208): PaymentModuleCore->validateOrder(434, 1, 1.51, 'Stripe: Credit ...', NULL, Array, NULL, false, '98dc27777291456...') #9 /home/veganlin/public_html/modules/stripe/classes/PaymentProcessor.php(116): StripeModule\PaymentProcessor->processCharge(Object(Cart), Object(ThirtyBeesStripe\Stripe\Charge), Object(ThirtyBeesStripe\Stripe\PaymentIntent)) #10 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(153): StripeModule\PaymentProcessor->processPayment(Object(Cart), Object(ThirtyBeesStripe\Stripe\PaymentIntent)) #11 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(127): StripeValidationModuleFrontController->processPayment(Object(Cart), Object(ThirtyBeesStripe\Stripe\PaymentIntent)) #12 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(98): StripeValidationModuleFrontController->processPaymentIntent('pi_3JkooXGngIXh...') #13 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(59): StripeValidationModuleFrontController->validateCreditCard() #14 /home/veganlin/public_html/classes/controller/Controller.php(197): StripeValidationModuleFrontController->postProcess() #15 /home/veganlin/public_html/classes/controller/FrontController.php(255): ControllerCore->run() #16 /home/veganlin/public_html/classes/Dispatcher.php(852): FrontControllerCore->run() #17 /home/veganlin/public_html/index.php(33): DispatcherCore->dispatch() #18 {main} END
  3. Swift_RfcComplianceException: Address in mailbox given [] does not comply with RFC 2822, 3.6.2. in /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php:345 Stack trace: #0 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php(261): Swift_Mime_Headers_MailboxHeader->_assertValidAddress('') #1 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php(106): Swift_Mime_Headers_MailboxHeader->normalizeMailboxes(Array) #2 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php(63): Swift_Mime_Headers_MailboxHeader->setNameAddresses(Array) #3 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMimeEntity.php(592): Swift_Mime_Headers_MailboxHeader->setFieldBodyModel(Array) #4 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMessage.php(432): Swift_Mime_SimpleMimeEntity->_setHeaderFieldModel('Bcc', Array) #5 /home/veganlin/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMessage.php(412): Swift_Mime_SimpleMessage->setBcc(Array) #6 /home/veganlin/public_html/classes/Mail.php(293): Swift_Mime_SimpleMessage->addBcc(NULL) #7 /home/veganlin/public_html/modules/mailalerts/mailalerts.php(702): MailCore::Send(1, 'new_order', 'new order: #168...', Array, 'shop@veganline....', '', 'shop@veganline....', 'Veganline.com', NULL, NULL, '/home/veganlin/...', NULL, 1) #8 /home/veganlin/public_html/classes/Hook.php(769): MailAlerts->hookActionValidateOrder(Array) #9 /home/veganlin/public_html/classes/Hook.php(471): HookCore::coreCallHook(Object(MailAlerts), 'hookactionValid...', Array) #10 /home/veganlin/public_html/classes/Hook.php(288): HookCore::execWithoutCache('actionValidateO...', Array, NULL, false, true, false, NULL) #11 /home/veganlin/public_html/classes/module/PaymentModule.php(967): HookCore::exec('actionValidateO...', Array) #12 /home/veganlin/public_html/modules/stripe/classes/PaymentProcessor.php(208): PaymentModuleCore->validateOrder(431, 1, 1.51, 'Stripe: Credit ...', NULL, Array, NULL, false, '98dc27777291456...') #13 /home/veganlin/public_html/modules/stripe/classes/PaymentProcessor.php(116): StripeModule\PaymentProcessor->processCharge(Object(Cart), Object(ThirtyBeesStripe\Stripe\Charge), Object(ThirtyBeesStripe\Stripe\PaymentIntent)) #14 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(153): StripeModule\PaymentProcessor->processPayment(Object(Cart), Object(ThirtyBeesStripe\Stripe\PaymentIntent)) #15 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(127): StripeValidationModuleFrontController->processPayment(Object(Cart), Object(ThirtyBeesStripe\Stripe\PaymentIntent)) #16 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(98): StripeValidationModuleFrontController->processPaymentIntent('pi_3Jknq0GngIXh...') #17 /home/veganlin/public_html/modules/stripe/controllers/front/validation.php(59): StripeValidationModuleFrontController->validateCreditCard() #18 /home/veganlin/public_html/classes/controller/Controller.php(197): StripeValidationModuleFrontController->postProcess() #19 /home/veganlin/public_html/classes/controller/FrontController.php(255): ControllerCore->run() #20 /home/veganlin/public_html/classes/Dispatcher.php(852): FrontControllerCore->run() #21 /home/veganlin/public_html/index.php(33): DispatcherCore->dispatch() #22 {main} END
  4. Thanks! The payment worked, but the screen took me to Example.com/module/stripe/validation?type=cc headed "payment error". I suppose I could change it somehow. It shows this error message and a button to go back to the shopping cart An error occurred: Failed to validate order
  5. No such payment_intent: is the current error message, with no transaction. Any ideas welcome. Meanwhile I'll try Paypal
  6. Still failing on version 1.2 and PHP 7.4 unfortunately. Stripe shows the payment initially "incomplete", which I suppose triggers the error, and then as complete. It might be relevant that my email notifications haven't worked since late September; I don't know what I did to break them. ---added The Stripe site has an error message next to the first failed payment " The PaymentIntent requires a payment method Set an existing payment method on the PaymentIntent or have the customer enter a new payment method. Learn more" Then a couple of seconds later, the payment goes-through after triggering the error message. If you click on the links to find out more, your find a blank page on the Stripe site. ---added After changing back to 1.7.0 and forward again to 1.7.1 I get a different error message in black under the inline Stripe form: No such payment_intent: 'pi_3JklsDGngIXhdSwB05cBtIoo'; a similar object exists in live mode, but a test mode key was used to make this request.
  7. Failed to validate order Has anyone else found a solution? I got this error message after ordering myself something with a live card. The card was charged and the order shows in the back office. The same thing happened to a customer this morning. I'm on bleeding edge version 1.3 and PHP 8.
  8. hostknox.com/tutorials/prestashop/1.5-1.6/products/pac describes default software for product packs and there might be other guides. Product Packs. Packed products can't have combinations of attributes, and I don't think a customer can change them, so I don't know how a customer could choose the types of coffee in the pack this way. From memory, there are limits to do with stock control; you cannot combine one product with stock control like 25 shirts, with another product like 1,000,000 combinations of ebroidered lettering, which would clock clog the database if you tried to treat them as stock , even if that is possible, and there is no need. You just have to count your shirts in some other way if you sell embroidered shirts and use the default product packs. You can keep stock control for other products, like un-embroidered shirts, and do something by hand to the stock levels if you embroider one. Attributes Another from-memory thing: the default software can show product attributes as drop-down menus, radio buttons, or colors (which can have an image file to present a texture, or whatever you want like a picture of coffee). (There isn't an option for check-boxes, although this might be quite easy to change and the css files allow for check-boxes. ) Adapting the CSS for all pages from the back office Whatever you choose might involve some small changes to the product.tpl template to make it intuitive and pretty. If you use the "texture" option to show pictures of coffee, you might want them larger than the default CSS allows for example and do something-or-other to the template file to make the pictures bigger. This can be in example.com/backoffice/preferences/custom code/css ...if you want the css code at the top of every single page of your web site. Maybe that's OK for color/texture icons because the css code is probably quite specific, but you can also change the product template file. Adapting the product template selected for this product Talking of boxes, there are boxes you can put round a parts of a form. https://www.w3schools.com/tags/tag_fieldset.asp There is already an example of a changed product template called product-wide.tpl that you can select for any product, and you can choose it from backoffice > products > example > template manager ...which is near the bottom of the list on the left hand side of your product editing page. If you want to find this file on your server, it is at example.com/themes/niara/templates/product-wide.tpl You can add any template file next to it in the same directory and select it from the back office for one or more products.. The default product.tpl template on github is at https://github.com/thirtybees/niara/tree/master/templates/product ... and you might want to adapt that one. If it's awkward to get access to the server files, there is a module from https://dh42.com/free-prestashop-modules/that lets you add or edit server files from the back office. I forget which one, but ask if important. Customization The software has an option called Customization built-in, but it's just a start. It makes a text box at the bottom of the product page with its own "save" button, that the customer has to remember to press before pressing the "buy" button. You can't move the box above the "buy" button just by changing the template; it doesn't work. Customers might as well use the comment box on an order form when ordering. There's a module I use for pressing both buttons at once, and there's a more advanced one for charging according to the customisation as well: it's on https://store.thirtybees.com/shop-modules Afterthought: cart rules? There might be some way to write that any 4 coffees from a list get a lower price, or any order over £200 gets free UK delivery, or something like that. It might be the cart rules part of the back office that sets this. I haven't tried but there might be a guide online somewhere. Suppose that all eligible coffees were presented on a page with your special offer written above them, that would come a bit closer to the select-a-gift-pack idea. Cart button for gift wrap There are some tick-boxes on the shopping cart that you'd usually want to cover-up just to simplify it, but you could leave one on for "gift wrap". Or it might be "recycled packing", but you can change the text to what you want on the backoffice translation menu. I wrote this for anyone who finds the thread rather than checking-out the person who asked. Hope this helps anyway
  9. @jollyfrog was there a particular problem with Niara for your client? I'm happy to hack templates around if I know how, and put them on the "tips and tricks" page if that's what's needed. I don't know if I'd do it well but Haylau made the same offer.
  10. Blocklayered.php : state limitations and... Don't index zero-stock attributes. I've glanced as some Prestashop threads and it looks as though the module didn't or doesn't work with Multishop Multiple variations Zero-stock attributes, which it indexes as though in-stock That last problem applies to my current Thirtybees layered navigation as well. A PS Forum post https://bit.ly/blocklayered-php suggests a couple of lines to add, but they don't work on my TB version. Any way of improving the module would be a good thing (unless there is an easy work-around which I've missed)
  11. Niara on modern technology would be a great target, and resting-point. Till then, I am a back-seat driver with no skills to offer, but there are some ideas further up the thread.
  12. I can see a purpose for customer-selectable features: an alternative to customisation. Belt lengths for example, when belts are cut to size and there's no need to track stock by length. Then you can use stock control for the buckles and have a drop-down menu for the length feature. Anyone who customizes stock has this problem. Silver cups for example. You want to have stock-control turned-on for silver cups because they're expensive and take time to get delivered and you can't make them up as you go along. But the lettering on a silver cup has ka-zillions of combinations, so the database would fail if you tried to make every combination of letters into a product, and you don't need that anyway because you just wait for an order and then carve the cup. But maybe I am missing the point.😀
  13. My core updater > database tab didn't mention features. My catalog > product features > add a new feature doesn't change to the one on the datakick demo; there are no new switches. Same on a fresh demo site as on my real site. Maybe this doesn't matter. When the new module updates the database automatically, it will do it better than me.
  14. The default Niara theme gets the Raleway font all the way from a google server linked from the header template, about line 51 Example.com/themes/niara/header.tpl You can delete that line or put comment tags round it like {*...*} {*<link href="https://fonts.googleapis.com/css?family=Raleway:400,500,600,700" rel="stylesheet">*} Example.com/themes/niara/css/global.css - the main style sheet - chooses Raleway, or Helvetica font as a backup. Helvetica is a web-safe font already in most browsers, so your site now reverts to Helvetica and becomes a bit faster. You can see the difference on the waterfall section of a gtmetrix test. If you follow the fonts.google link you can see why: it loaded every known weight of the Raleway font for three different alphabets. If you want to keep Raleway, at least for modern browsers https://google-webfonts-helper.herokuapp.com/fonts/raleway?subsets=latin shows you how to download just the bits you want, such as latin default 400 weight , 500, 600 and 700. It lets you download them as a zip file with a name like raleway-v22-latin.zip. Download the zip file. Upload to: example.com/themes/niara/fonts/ Extract (unzip) the font files there. If webfonts helper isn't online, you can see the names of the latin fonts to download in the file below; they come from https://fonts.googleapis.com/css?family=Raleway. You just have to save them with the same name that the lines below call them. The same page of webfonts helper has lines starting @font-face which you can cut and paste to the top of Example.com/themes/niara/css/global.css /* raleway-regular - latin */ @font-face { font-family: 'Raleway'; font-style: normal; font-weight: 400; src: local(''), url('../fonts/raleway-v22-latin-regular.woff2') format('woff2'), /* Chrome 26+, Opera 23+, Firefox 39+ */ url('../fonts/raleway-v22-latin-regular.woff') format('woff'); /* Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ */ } /* raleway-500 - latin */ @font-face { font-family: 'Raleway'; font-style: normal; font-weight: 500; src: local(''), url('../fonts/raleway-v22-latin-500.woff2') format('woff2'), /* Chrome 26+, Opera 23+, Firefox 39+ */ url('../fonts/raleway-v22-latin-500.woff') format('woff'); /* Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ */ } /* raleway-600 - latin */ @font-face { font-family: 'Raleway'; font-style: normal; font-weight: 600; src: local(''), url('../fonts/raleway-v22-latin-600.woff2') format('woff2'), /* Chrome 26+, Opera 23+, Firefox 39+ */ url('../fonts/raleway-v22-latin-600.woff') format('woff'); /* Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ */ } /* raleway-700 - latin */ @font-face { font-family: 'Raleway'; font-style: normal; font-weight: 700; src: local(''), url('../fonts/raleway-v22-latin-700.woff2') format('woff2'), /* Chrome 26+, Opera 23+, Firefox 39+ */ url('../fonts/raleway-v22-latin-700.woff') format('woff'); /* Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ */ That's it! After the usual cache clearance, your Helvetica site should now revert to Raleway, but be a bit faster than before. Next time you update the theme with the core updater, it will show a list of manually changed files including header.tpl as a reminder to copy the changed bits over to the new version. It keeps copies in the directory you use for the back office. There are probably neater ways of doing this or explaining it and suggestions are welcome. I haven't tried using other fonts. ---------edit: I'd forgotten Modules > Themeconfigurator > Displayliveconfigurator YES > View lets you choose some other google fonts without changing any code at all. They still take a fraction of a second to download from another site, but some might have fewer alphabets and weights than Raleway.
  15. https://forum.thirtybees.com/topic/3593-tip-default-one-page-checkout-shortened-from-the-back-office-css-panel/ ... gets close. The order form still asks for buyer first name second name, followed by delivery firstname second name. I don't know how to change that as covering-up the form doesn't work. I've left email in.
×
×
  • Create New...