x97wehner

Just found this post. I'm curious, were you able to get rid of the last "after" navigation arrow as well? I followed your directive and it did remove the product correctly, but it left the last arrow. Thanks.

@the.rampage.rado, did you modify the breadcrumb to Schema.org for warehouse? If so, curious how you did it?

I tried that loyalty module a couple years ago, and even when working with them, they couldn't get it working right and, of course, the support time eventually ended. Definitely don't recommend them or that module either.

You could try this one as it says PS 1.6 https://addons.prestashop.com/en/legal/25037-age-verification.html

I seem to need to do this irregularly and always have to look up how to do this again each time. I figured I'd just post the directions below for everyone else's benefit so they can do the same without scouring the internet. This is taken from old prestashop blogs from 1.5, so while not 100% accurate, it's still very, very close and will get you through it. The pictures on the old blog site are broken so that's why they are not included here. Here is the link to the site (Content is pasted below) https://www.prestashop.com/en/blog/set-up-a-test-server-for-your-online-store ---------------------------------- Do you have a test server? If not, you're taking an unnecessary risk. Modifications on your online store will modify your databases and their connecting files.These modifications need to be fully tested before you implement the changes to your live server and Ecommerce website. It’s crucial that you know how to manually copy your database and files from your live store to create a duplicate test server. After you create the test environment feel free to try any upgrade, theme or module to see how it would look on your real store, without wasting any downtime on your live online store. Don't be left in the dust by not taking the proper online store management procedures, these extra precautions will save you both time and money. We will be working with Ecommerce platform PrestaShop, FTP client like FileZilla, phpMyAdmin, and MySQL. If you don’t know what those are, you can Google it for more info. Test Server Assumptions For this Tutorial, I’ll have these assumptions, your URL's will be different but the concept stays the same. I have a LIVE PrestaShop store at www.presta4live.com (Live Store Domain) I have a test domain, and blank directory within FTP. I created a blank database (Click to learn how) for my TEST URL www.presta4test.com (Test Store Domain). [TIP: Remember the Name, Username and Password of your newly created database, you'll need them after] I want to COPY my Database and Files from my Live Domain to the Test Domain, to replicate my store on my test server. Backing Up Live Store Let's get started. First, we need to Back-Up or Export your Database and Files. This tutorial will give you the basics of what we need to accomplish today. (Click for Tutorial) Import Database to Test Server After you backed up and exported your Database and Files of your live store, you are ready to import your Database that your exported from your Live Store. Follow these steps: Log in to your cPanel of your test domain Navigate to phpMyAdmin Find and click the Test Database that you made. Now click “Import” Click on "Choose File" and Select the exported database from your Live Domain and import. Leave all settings as default and click Go. When you have finished importing the database from your live store to your test store directory, open up your test url database and click the table ps_shop_url After clicking the table, click on Edit. You want to change the URLs in domain and domain_ssl from your live store’s URL's to your test stores URL. [TIP: Make sure to put a forward slash at the end of the URL's.] In the screenshot you'll notice my test URL, yours will be different. Copy PrestaShop Files to FTP Once that is completed you can log into your FTP of your test store and import the files (not the database) that you copied from your live store via FTP. Simply copy and paste the files into your blank directory you created in your Test Server. After you import your files, the next step is to change some data in config/settings.inc.php via FTP . You need to make sure that the DB _NAME is the name of the test database that you created. DB_USER and DB_PASSWD is the username and password of the database define('_DB_NAME_', 'presta4test'); define('_DB_USER_', 'root'); define('_DB_PASSWD_', ''); [TIP: Make sure to manually delete your htaccess in your test server's directory via FTP. Next, regenerate the htaccess by toggling "Yes" "No" in Preferences/SEO & URL's/Friendly URL in your test store's back-office] Final Touches That's it! There are some housecleaning chores you can do in your Back-Office if you want. You can configure the modules with the test API credentials. Because this is a test server, you don’t want Google to crawl it as you may incur duplicate content penalties after a while, so be sure to keep your store in Maintenance Mode. You now have an replica of your store on a test server. This is useful to test any upgrades to the software, updates to modules and theme changes. Testing first will minimize your downtime and avoid any potential issues that might cause you lose sales. Manage your online store the right way by creating and using a test server. Feel free to comment below with your thoughts. Thanks for reading and happy selling! --------------------------- How to Manually Back Up MySQL Database and PrestaShop Files August 29, 2013 This article is part of our Guest Blogger Series. Its content was created by Lesley Paone, a PrestaShop Global Forum Moderator (Dh42) and the owner of Nashville-based Designhaus 42. How to Manually Back-Up MySQL Database Have you ever wanted to know how to manually back up your Prestashop store? This can be really useful if you are going to upgrade your site, load a new csv file, or just to have in case anything happens to your server. Backing everything up manually is a great idea, most developers do it. Below I will show you how. Backing up the database The first step is to back up the database. For this you are going to need to login to the cpanel for your site. Normally they are located at either cpanel.yourdomain.com or domain.com/cpanel. When you access it you will see this screen. From that screen you can login to your cpanel. Usually your cpanel login is the same as your ftp login, but that is not always the case. If you are unsure of your login refer to the email your host set up when you created your account or email them and ask them for the login information. Once you are logged in, you want to scroll to the bottom and look for the phpMyAdmin icon. It is under the headings databases. Click on that icon and your database management will open up and look like the image below. Click on the database that you want to backup from the left column. When you click on your database it will open up in a view that shows all of the tables in your database. From that view click on export in the top menu, like the image below. Once you click on export the next screen will ask you if you want to do a quick export or a custom export. Due to the size limitations of hosts and that Prestashop 1.5 databases can get large, select custom and press ok. The only thing you really need to select during the custom export is the compression. I recommend using gzip as the compression format, as it is universally supported. Now press Ok at the bottom of the screen and your database will start to download. Now you have a complete backup of your Prestashop database. So if anything happens to your site, you will be able to reload the database and restore it from when you last downloaded it. ----------------------------------------------------------------------------------------------- How to Manually Back-Up PrestaShop Files via FTP What happens to your site if your server crashes? You could lose all of your and it might take months to rebuild your store again. Never fear, I will show you how you can back up your files manually in case anything happens. I would also suggest using this in conjunction with our article on manually backing up your database. Downloading your site First things first, you are going to need the ftp information to log into your site. When you signed up for your web hosting you should have received an email with all of this information in it. You are also going to need an ftp program, I recommend Filezilla, it is the most popular these days. Once you have it installed, open it up, it should look like this. As you can see in the image above I have highlighted where you will enter your server information. Once you have it entered you can click quick connect. Normally you will not have to enter anything for the port number, you can leave that blank. Once you are logged in, depending on how your host is set up, it should look like the image below. All you have to do to back up your site is to right click on the public_html directory in the left pane and select download. If your site is very large this could take several hours. The only time that your files will ever need to be backed up again is if you Add new products to your site Install or remove any modules Install another template Edit your existing template Upgrade your shop Or if you make any changes to core files People placing orders or contacting your customer service will not affect the files on your site, all of that information is installed in the database. So if you never do any of the above mentioned things you will only have to back your site up once, which is awesome.

Man, if you can get this working, you will be even more my hero. I'll try and find some time to test this.

The only value in doing this would be for lead generation that I can speculate. If so, keep in mind that TB and just about any other cart tool are designed to be transactional ERP systems, not customer nurturing CRM systems. If you need lead generation, you'll want to explore other CRM and marketing apps. Hubspot has a nice free CRM tool you can start as a smaller business. If you're trying to track your ads to sales directly, Google Tag Manager and Analytics are the better choice. There are modules out there that can assist you with this setup.

I'd love to see a modern flexible theme like Panda or Warehouse that focuses on TB. Niara is good, but not very flexible without a ton of custom code.

I use both. I try and used predefined, but I get one offs pretty often that are just easier to manually override rather than jump between screens.

It ended up being an issue with how TB was rewriting my htaccess via apache. My server company helped with the adjustment so all is good now.

I haven't updated PHP in quite some time. Been on 7.3 for very long now. I will attempt to find and check the logs in cpanel.

Actually, I just spun up a fresh tb instance off of softaculous and I get the issue there as well.

Debug doesn't show any error. Not sure how to check the server log.

Actually, I went to my old dev server that's on 1.3 stable and I'm getting the same issue.

Hello, Testing out bleeding edge and after updating my dev server instance, whenever I do updates to things like friendly URL, robots.txt, or .htaccess, I'm getting a 404 error. It's this URL /index.php?controller=AdminMeta&token=....... Any idea how to resolve this issue? Thanks.

MigrationPro: PrestaShop to PrestShop Migration Tool

This won't help you with your migration the way you're going, but I did this a couple years ago and did get it to successfully migrate but there was still a bunch of buginess from old code in there. Within the year I ended up just spinning up a fresh TB store and then using a data migrator module to copy over my theme and customizations to the new TB store. It ended up working pretty flawlessly and got rid of a ton of old code that was causing issues.

We have a similar situation, but the overhead of trying to manage that kind of complex logic is not worth the extra 5% that a few people actually ever take advantage of.

I really haven't explored for a module that could do something like this. The only way I think you could do it natively is by having unique cart rules that are specific to that customer group for only 5% discounts and then unique cart rules for everybody else that offer the 10% discount.

Appreciate it. Please to let us (me) know as soon as you do. It's a big customer headache at this point to have to leave the cart and login elsewhere and then come back.

Five minutes after I posted this, I found the answer. Figured I'd leave the article link here since it's pretty descriptive. https://www.prestashopmanager.com/useful-articles/additional-features/setting-up-taxes-in-prestashop/

We are facing the need to change how we do taxes on our site. We currently only charge tax on products being delivered within our home state. It is setup correctly and works fine. We are now needing to charge different tax rates based upon all of the other U.S. states where the product is being delivered. I cannot figure out how to achieve this setup given that the product allows just one tax rule applied. The example needed is below: 1) Product sold in New York has New York sales tax applied 2) Product sold in Michigan has Michigan sales tax applied 3) Product sold in state n has state n tax applied. Is there a way to do this?

I am on bleeding edge and have had Chex module for years. Always has worked great until recently. Today, I found that customers cannot login on chex module at all anymore. The interface scans their email and allows them to type in the password, but it will never authenticate. Just keeps showing the invalid email or password message. Only way around is for customer to use the native store login first and come back, which is not the desired path for our store. How can this be resolved @datakick?

Appreciate the clarification

I'm testing bleeding edge right now and after my update, if I go to any product and make any update at all, I see this error at the top. Are you two seeing this also @toplakd or @SLiCK_303