Jump to content

tannerS

Members
  • Posts

    136
  • Joined

  • Last visited

  • Days Won

    1

tannerS last won the day on February 9 2013

tannerS had the most liked content!

Profile Information

  • Activity
    User/Merchant

Recent Profile Visitors

7,028,864 profile views

tannerS's Achievements

Newbie

Newbie (1/14)

32

Reputation

3

Community Answers

  1. I had two customers say they could not check out because of a "no carrier for address" error. All other orders were fine. I realized both customers wanted the same item, so obviously the issue was specific to that item. Scratched my head a few times and thought I would adjust the item weight, and that was the issue. If a product weight matches the carrier weight range exactly it will cause an error. In my case the item weighed .8125 or 13 ounces. My USPS First Class weight range maximum is also .8125, Presatshop didn't like it. Lowering the product weight slightly below 13 ounces fixed it and the item still ships on the cheaper First Class Mail rate. I just lowered it slightly. So if its just one product thats giving you issues and everything else ships fine, make sure the weight is not exactly at the weight range limit of the carrier. I didn't notice the issue untill those two customers chose that exact product alone, most of the time people order multiple items and it took a while for the single orders to reveal the weight problem.
  2. Since upgrading to 1.6 I have one customer who can't get a shipping carrier, existing account, known valid address. Yet the 1.6.0.9 cart says no carrier for this address. Tried changing up the address, verified the information and product shipping settings. Nothing has changed, it just won't ship to the address, this is the 3rd order from the same customer. No errors in the back office? Only affecting one customer account so far. He is using Chrome, cleared his cache, still can't check out and I can't create an order from his cart either. It won't give me a carrier in the BO either. Any ideas? Thanks.
  3. I tried a Web Site Speed test here: http://tools.pingdom.com/fpt/#!/c4oZnu/http://www.hancke.be/metaal-staal/ You have some cookie and cache issues with your images, yet the load times are okay. Your load times also depend on the distance from the server. A shared host can be really fast and then bog down during peak loads when the server is getting lots of traffic. I would set up a web site speed test software and check it for a few days and see what the average performance is over a specific time period.
  4. Another thought; When my site got really sluggish my host told me everything was fine on thier end till I insisted the availble memory was not there. Then they finally admitted the server was in need of repairs, this went on for two weeks and GoDaddy would not move my site to a better server without a fee. So, i moved to InmotionHosting. I was with GoDaddy since 2004, the customer loyalty really was horrible with that company.
  5. Ping your site and see whats up. There are browser tools that you can use for testing, you can ping it from your computer using the command prompt. Google is your friend and you'll see guides on how to judge your site's performance. Depending on the browser you may have what you need by using the F12 key. On Fire Fox its called "performance". Its probably either a slow host or a lack of RAM memory. I just went through that problem and it was my host. I was only getting 64mb of RAM at times. You really need 256mb to be safe. 128mb is ok and very common on a shared host. I use shared hosting without too much trouble, but some limit you severly on a shared server and they love to pack in way too many sites.
  6. CarlosC fixed the issues, he is prompt and professional. Thanks!
  7. Thanks for the offers guys, I got all sorted out by CarlosC just now. He fixed the SSL issues very quickly and made a modification for me.
  8. Wish I could help. I've been using a LeoTheme that Elpatron's services installed, the live editor has some flexibility and you can create custom widgets. I just upgraded from 1.5 to 1.6, still learning what I can do with the module hooks and the LeoTheme page tools. Upgrades are a headache no matter how much research you do.
  9. Probably not much help, but try resetting the module and make sure the site cache is in force recompile under the performance tab. I haven't tried using that module yet, its on my to do list.
  10. I've had good success with this easy to use page maker: http://presta-theme-maker.com/maker/ Its just an wasy way to customize the default Prestashop theme and make it your own without any coding. Its cheap and effective for people like me with no design talent. I've have tried a paid theme twice, and really don't see the advantage over keeping it simple. The paid themes always need tweaking and I have to hire it done. So the little Presta Theme Maker is nice for a simple design and you subscribe to it for a time period. Plenty of time to make changes at a resonable rate, plus its really easy to use. I used the maker a few times and had no problems making the shop functional and and somewhat unique.
  11. Thanks for the responses, I've replied to a couple. Waiting on the replies.
  12. To get specific, my recent 1.6 upgrade came up short, it needs secure SSL on the account and check out pages: The LeoBlog images are causing a SSL error The footer payment image is causing a SSL error The google fonts are causing a SSL error The prestashop search module is causing a SSL error Thats what I see, obvously I'm looking for skills I don't have. Basicly I just need the upgrade job completed.
  13. I need my site to produce a green browser lock without the errors. The devoloper I hired to upgrade my site left me with errors: sagesoutdoors.com I'm open to bids or suggestions on a reliable service to get my little site functioning correctly. It is a LeoTheme on 1.6.9..
  14. Can you guys point me in the right direction or suggest someone who can really fix these SSL issues? Obviously I would fix them myself if I knew how. Here are my Chrome errors: [blocked] The page at 'https://www.sagesoutdoors.com/authentication?back=my-account' was loaded over HTTPS, but ran insecure content from 'http://fonts.googleapis.com/css?family=Lobster': this content should also be loaded over HTTPS. authentication:1 [blocked] The page at 'https://www.sagesoutdoors.com/authentication?back=my-account' was loaded over HTTPS, but ran insecure content from 'http://fonts.googleapis.com/css?family=Oswald:400,300,700': this content should also be loaded over HTTPS. authentication:1 The page at 'https://www.sagesoutdoors.com/authentication?back=my-account' was loaded over HTTPS, but is submitting data to an insecure location at 'http://www.sagesoutdoors.com/search': this content should also be submitted over HTTPS. authentication:1 The page at 'https://www.sagesoutdoors.com/authentication?back=my-account' was loaded over HTTPS, but displayed insecure content from 'http://www.sagesoutdoors.com/img/leoblog/b/25/250_150/b-blog%20hunter.jpg': this content should also be loaded over HTTPS. authentication:1 The page at 'https://www.sagesoutdoors.com/authentication?back=my-account' was loaded over HTTPS, but displayed insecure content from 'http://www.sagesoutdoors.com/img/cms/payment.png': this content should also be loaded over HTTPS. authentication:1
  15. Decided to pay someone to upgrade, 1.5.3.1 just ain't doing it. Maybe a pro will fix it right this time.
×
×
  • Create New...