Jump to content
Latest News: (loading..)

BrockleyJohn

♥Ambassador
  • Content count

    593
  • Joined

  • Last visited

  • Days Won

    21

BrockleyJohn last won the day on November 5 2017

BrockleyJohn had the most liked content!

4 Followers

Profile Information

  1. First time I set the slider to min/max 229 all products were priced 219. Second time all products 259. Then set range 229 - max (300 and something) and got no products at all. Win 7, Firefox.
  2. Perhaps 'filtered category listing' would tell people straight away what it does. It's likely a feature that will be in great demand when it's working. For this reason the ajax needs to be totally secure othewise it will be easy for a hacker to trawl for sites using it... The price slider isn't behaving predictably at the moment - it changes which products are displayed but not within the range apparently set
  3. If you set the zone in the module, it has to match a tax zone in admin config that is set up for the UK - All zones. Admin > Locations / Taxes > Tax Zones I guess you already created one, but you need to go in to edit it and make sure it's set to all zones for the country.
  4. That's a problem with your shipping method. It looks like you're using one that's not working properly. Or you have failed to configure zones properly. What shipping do you want?
  5. The line that's now failing on BUS_ENABLE_DELETE must be add-on code. My guess is that the add-on needs an installation script running to add this constant and you've forgotten to do it on your current database.
  6. The stuff that only displays in list is hidden in grid by this rule: .grid-group-item .list-group-item-text { display: none; } If you set display for the whole of this class you will also see description in grid. To pick off individual bits to show, you'll need to be more specific, eg. for model .dl-horizontal.list-group-item-text { display: block; } in your user.css But if that ends up showing other stuff that you didn't want to, you'll have to add something so you can target it exactly. Either a simple change to the php that outputs the grid, or a fancy bit of javascript that avoids you changing core code.
  7. @fleeced Lee, this'll get you started. https://forums.oscommerce.com/topic/412428-addon-facebook-pixel/
  8. [Addon] Facebook Pixel

    Apps area: https://apps.oscommerce.com/Apps&ZT4uG&facebook-pixel
  9. [Addon] Facebook Pixel

    Facebook pixels feed tracking information from your site into Facebook. The feature bears some similarities to Google Analytics but typically gives you more information about the behaviour of individuals and more detailed demographics. The basic pixel gives information about page views. It can be extended with event tracking. This addon implements the basic pixel and purchase event tracking with no code changes required. Compatible with any osCommerce 2.3 version including 2.3.4BS Gold and Edge. Designed to be compatible with stores implementing multiple currencies with different formats. Download link to follow shortly...
  10. We can't help much with theme-specific questions, especially without even seeing the web page! All the blue options in the admin snapshot are part of the theme. It's a shame you didn't follow the advice to base your site on the community responsive versions of oscommerce 2.3.4 - we could help with that. I suggest you ask the theme author for guidance.
  11. I did a last-minute thing for Black Friday, and have the first cut as a complete module. This adds the facebook pixel to whichever pages you select, which gives you tracking of clicks through the ad to the site. I have yet to add event tracking into this (doing it properly needs some extension of the brand new data attributes in Edge) but this could be left for a version two - I just need to do some documentation and it's fit to upload as is if you're interested.
  12. Paypal Sandard - Customer receives message could not verify Paypal trans.

    @jordi "could not verify transaction" is not a bug, it is an error message. There are several things that can lead to it, and most of them are failures to configure the module properly. Reverting to an earlier version of the module using less verification is not a solution, it's really avoiding the problem that you hit by doing less checking. I have seen several kinds of attacks on websites payment modules over the years usually with the aim of hijacking payments but sometimes trying to steal goods. I think it 's best to set up as much automated checking as you can.
  13. https://stackoverflow.com/questions/2447791/define-vs-const basically, const uses namespaces but define can be conditional and use expressions const outside classes is 5.3+ const using arrays 5.6+ defines and arrays 5.7+ And I think language files are going ini format, aren't they?
  14. Paypal Issue Could not verify the PayPal transaction

    @tornrawks in my client's case they were using a sandbox merchant account that had an unconfirmed email address - I think it had been created via the 'fetch Sandbox credentials' dialogue from osc. The symptoms (customer being returned to the shopping cart with the error message) were the same. If you look at the Paypal log in admin, you'll see that there's a successful _notify-validate [IPN] and a failed _notify-synch On the way to a solution, different details to the error logging were thrown up with different aspects to the resolution without PDT set up at all, there was no response to the _notify-synch with apparently all the proper settings in the sandbox merchant account and the matching token in osc, but with an unconfirmed email address in the merchant account, error response 4010. Sandbox accounts don't send actual emails and I was unable to find a way of confirming it since it was not associated with a developer account. If you sign in to developer.paypal.com and create a sandbox account there it doesn't need confirming. through carelessness in going from one setup to the other I also made it throw a 4011 error when the PDT token in osc was different to the one in the paypal account Suggested approach to configuring paypal sandbox account for testing: Log in to developer.paypal.com and create two accounts to use: a business account (to represent your shop) and a personal account (to use for placing test orders) Log into sandbox.paypal.com with your new business account. Go into the settings / My selling preferences / Website preferences / set Return to my website On, return url to http://domain.com/checkout_process.php, Payment Data Transfer to On, Encrypted payments off after saving these settings, go back in to get the PDT token fetch the sandbox credentials into osc using the new business account paste the PDT token into the configuration NB when you go live you will need to replace the sandbox PDT token with one taken from the live paypal account
  15. Paypal Issue Could not verify the PayPal transaction

    @tornrawks there's a time limit on editing a post - after a while you can't. Order status Pending is what you normally get on an order that has been paid. By default, they get created in a Preparing state, and changed to Pending on receipt of payment. Paypal [Transactions] is a logging order history that shows you the IPN has worked. Does the customer end up back at the beginning of the checkout process with the message that's the subject of the thread: "Could not verify the PayPal transaction. Please try again."? If so, that is your actual issue. The return from pp is failing and not going to checkout_success.php I have just hit the same thing setting up pp standard in sandbox mode for a client and will let you know what was causing it for them when I have sorted it out. It's likely a configuration thing.
×