Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Failure to order issues using the wholesale printing sites Navitor.Com; ASAP.com and stickeryou.com sites

  • 1 reply
  • 1 has this problem
  • 5 views
  • Last reply by WestEnd

more options

All three sites have had issues (navitor.com) not so bad, but ASAP and stickeryou.com and sadly one other I can't recall basically said stop using Firefox and use Chrome or Safari, we would get to the order entry area and the submit would be gone...they blamed Firefox upgrades

All three sites have had issues (navitor.com) not so bad, but ASAP and stickeryou.com and sadly one other I can't recall basically said stop using Firefox and use Chrome or Safari, we would get to the order entry area and the submit would be gone...they blamed Firefox upgrades

Chosen solution

I tried both those sites Chrome and FF and I have no issues getting to the site and then when I go to choose the product and final. Wholesale requires a account and Stickeryou require uploading image. Also I found there are popups from those sites and if your using some kinda Popup blocker this will prevent you from completing the site access. So either you have a over active A/V or Firewall or your using some kinda of Ads Blocker causing them to block your access. So at this point it's neither a Chrome or FF problem.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

I tried both those sites Chrome and FF and I have no issues getting to the site and then when I go to choose the product and final. Wholesale requires a account and Stickeryou require uploading image. Also I found there are popups from those sites and if your using some kinda Popup blocker this will prevent you from completing the site access. So either you have a over active A/V or Firewall or your using some kinda of Ads Blocker causing them to block your access. So at this point it's neither a Chrome or FF problem.