jnsgioia

@Havouza Remebering from ps 1.7 uploads you need to check for # and ; in your titles as well. I had to remove all three before it would work correctly.

@Havouza I think if you fix it with a csv import the urls will be rewritten automatically.

@Havouza I think it is save of the product. Are you needing to mass update all your urls or just as you change the product?

If you go to Preferences - Products there is a button to force update of friendly urls on every save.

At the top of the preferences - Geolocation page there is is this message: In order to use Geolocation, please download this file and extract it (using Winrar or Gzip) into the /tools/geoip/ directory. However there is no geoip directory in tools. There is one in vendor. And that has another file in it named geoip. Please see the screenshot below. Should I put the Geolitecity.dat in the first one, the second one or create a file geoip in tools?

Sometimes that makes things more complicated :)

I think that is basically the same as libreoffice Calc which I do use. Access is comparable to Base but has a lot more ooph and is a lot more complicated :|

@alwayspaws It may be a cookie thing. I have my browser set to clear all history everytime it closes.

I haven't heard of that one. I tried the db application in libreoffice and looked at filemaker, neither worked for me. I guess I am just used to Access.

I export out of Microsoft Access. If I need to work with a spreadsheet I use libreoffice Calc. I don't mind having to change the default but it would be nice if we could set the selection and it would remember it.

I have tried other databases but none will do what I need it to do. Access is the only MS application I use though :)

@mdekker I honestly don't remember what the problem was when I first set up the file. I think it had to do with ps breaking fields where it shouldn't because of ; or , in my descriptions. I had to find separators which I did not use anywhere in the file, except as separators.

It was a problem with the original install. I have no idea what the problem was, SiteGround could not determine the problem either. I created a new testsite exactly the same way as I did the first and everything is working as it should. I am back to square one as far as design but at least the foundation is secure :).

It was a problem with the original install. I created a clean TB testshop and everything works! Now I have to customize it for LJsBooks!

Ok it looks like I must have a write permission problem. The new theme is not on the server anywhere. I looked and all folders are set to 755 and files to 644. Do I need to do a clean TB testshop or is there some way I can fix what I have? I must have done something wrong with the initial install.

I uploaded theme 3 (not quick install) through the back office. It said it successfully uploaded, but it doesn't show anywhere. What I am doing wrong or is it a bug?

Now I am wondering if it is a problem with Thirty Bees. I re-enabled the module on the Prestashop site (I had disabled it because it broke the css of the custom theme). The Amazon Login button was not on the nav bar, but that was a template choice, but it was on the sign in page. I signed in using our buyer account on Amazon which has no connection to Amazon Pay and everything worked as it should. So I thought maybe the problem was because both modules were on the same domain and completely uninsstalled it from LJsBooks.com, leaving it on LJsBooks.com/Store. I cleared all caches and tried it again on the TB site and it failed. The weird thing is it is failing but does not leave an error message in any folder. I think the 503 message above was from trying to access the ipn page from somewhere other than Amazon. Ipn requests from Amazon are getting through. It seems to fail at the point where TB needs to put the information into the database. Any ideas?

From years of dealing with Microsoft Access and exporting and importing :) I have found that I need to check the settings on the import page each time because mostly it doesn't remember the change.

@alwayspaws I haven't imported any combinations but do use attributes. When I first set up the product import file I found I needed to avoid both commas and semicolons so used | for the field separator and ~ for the multiple value separator. This was for the PrestaShop 1.7 store but it has been working on the TB one too. You need to make sure you change the separator values on the import page to match your csv file.

Well, first Amazon said it was a SSL problem. It wasn't, Amazon's ipn checker was returning a incorrect response. Then they said it was a redirection problem, but we got that sorted out and nothing was fixed. I explained to Amazon that the payment part works, just not the login and they are checking on that from their end. Meanwhile SiteGround was able to see an error message that didn't show up on any of my logs. It was a 503 Error with message - header does not contain x-amz-sns-message-type header. I contacted patworx with that information and they are looking into it. I don't think it is a TB specific issue because I have the same problem on the prestashop site. But I have two different versions of the Amazon module, one for 1.7 and the other for 1.6. I disabled it on both sites for the time being. It is the free Payments Advanced by patworx.

@alwayspaws yeah! You are ahead of me there :)

I had to use the cart I had on LJsBooks.com for another site, long story, so needed something quickly that looked good. I've been building websites for years but didn't know anything about hooks and modules, just html and php :)

@Havouza I didn't think so. @alwayspaws Thankyou :) It has paid for itself since I had it up and I knew nothing about the structure of prestashop when I started so needed something quickly then.

@alwayspaws I am using the default theme right now. I have a purchased custom theme on the live site but it is a prestashop 1.7 one and has some issues that the developers have not been able to resolve, probably because it is 1.7 :). You can see the test site at LJsBooks.com/Store

I have the info on the new site. I just don't want to have to change it on the old one. Also we are majorly purging inventory and I would have to disable a bunch of categories in the old site (they are already disabled in the new one and I have a system in place to enable them as I need them).