Jump to content
Latest News: (loading..)

BrockleyJohn

♥Ambassador
  • Content count

    923
  • Joined

  • Last visited

  • Days Won

    25

BrockleyJohn last won the day on January 2

BrockleyJohn had the most liked content!

6 Followers

Profile Information

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. BrockleyJohn

    Paypal App - Fee

    If you only accept paypal then you should add a handling charge in the shipping module(s).
  2. BrockleyJohn

    Paypal App - Fee

    There is not this option in the app because your agreement with paypal expliclitly excludes you from applying any fee that's different to the fees using other payment methods. If one of your clients complains to paypal that you are doing this they may close your account.
  3. BrockleyJohn

    Login with PayPal - changes required?

    Thanks - that's just a link to the api call for user info and has nothing about what has changed. However, when paypal make a major breaking change there's typically lots of info so it seems reasonable to infer that they aren't changing too much - they're not saying that the integration needs to use a different call or that it works differently, just flagging up that fewer attributes will be returned. Big changes have previously been made available in the sandbox before live for testing purposes, that doesn't seem to be the case here so I don't think there's a way to test the change before it's applied to the live endpoint. My advice is: check your settings and be sure that you're only using name, email address and postal address. If that's the case then there shouldn't be a problem. If you rely on having another piece of info (eg. a site that only sells to adults and requires data of birth) then you may need to do some other work to ensure this data is provided outside the integration.
  4. If it's only ever been osc BS then the password handling hasn't changed
  5. @RAC is this a new store or a migration from an earlier version of osc? The password algorithm changed many moons ago and field lengths might have too...
  6. BrockleyJohn

    Login with PayPal - changes required?

    OK - what I've gleaned is that the "identity API" has been rebranded from Log In with Paypal to Connect with Paypal. I haven't found anything that actually compares them and highlights the differences. If the PP message is to be believed and everything will keep working unless you're trying to use an attribute that's not supported, you shouldn't need any code changes. You may need to change some settings, though. The only list of attributes I found in my quick trawl around is quite a lot shorter than those available in the module settings in osc. I got them here: https://developer.paypal.com/docs/integration/direct/identity/attributes/ but the context is a bit different so it might not be exhaustive. This is the list there: Full name Personal Information profile Email address Address Information email Street address Address Information address City Address Information address State Address Information address Country Address Information address Zip code Address Information address so if you use things like date of birth it may not be available any more. If you are taking things off the list in your module settings, you may still get problems if your app has permission set on them (in developer.paypal...) - or you may not, finding that out is a future joy.
  7. Password reset worked fine for me. It is possible that you have a higher-than-average proportion of customers that aren't very tech-savvy and are using old hardware / software to access the site and emails. The password link spreads over 2 lines and if it's getting split it won't work. If they read emails in plain text it won't help. If they are using old browsers some of the site might not work properly either. A tangential resolution would be to implement PWA (purchase without account)
  8. BrockleyJohn

    Login with PayPal - changes required?

    I'll try to have a look into this in the next couple of days and see what the impact is.
  9. ...here's one I prepared earlier - a test site that has English and Danish: http://bromleybr.co.uk/bsbo/
  10. enable error display in includes/application_top.php so you can see the problem: // set the level of error reporting error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); ini_set("display_errors", 1);
  11. Something must have gone wrong with your installation - the bs version does support multiple languages. I don't think I have ever tested the box module for switching language though, I have always used the navbar module which I think is a much better place for it anyway. As a box it's just using up screen space that could be selling something.
  12. Most obvious clue: the price shows $nan (nan = not a number, an error returned by javascript when you try to do an arithmetical operation on a string or empty variable). My guess is that the shipping module is failing to get the quote properly - in the first instance try the module support thread in case someone already hit the error.
  13. @nedragdnuos The warning message is indeed related to php7.2 in that you wouldn't have got it on a previous version of php. However, I think you shouldn't actually hit it if your shipping modules are returning the expected quotes structure. What shipping modules are you using?
  14. As Dan says: it means that you can add a simple rule to user.css to change the appearance of the breadcrumb only, without needing to edit any other file. There's a different mindset when it comes to setting up your own implementation of osc with the responsive version; instead of diving in and tweaking the code here and there to get it just so, you can make radical changes with admin settings and css. Many of the addons make big changes to the appearance and function of the store without changing the core code (on the catalog side at least). Jquery can manipulate the content in the browser after it was generated by the server. This is made easier by adding in extra classes identifying logical parts of the page which can then be picked up and used in css or jquery scripts but which aren't necessarily used in the code you get when you install your shop.
×