Child pages
  • Exploring PrestaShop's Tools

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Either as of a way of backuping your customizations, or of sharing them with other PrestaShop installs, you can create your own language pack using this form.

Note that the pacl pack will contain the theme that your translation is supposed to support.

...

At the right of each text field is a an icon:

  • Hover the mouse cursor over it to display the Google Translate suggestion.
  • Click it to apply the suggestion.

...

  • categories,
  • products,
  • versions,
  • customers,
  • addresses,
  • manufacturers,
  • suppliers.

Have a good look at the exemple example displayed on the page. You will have to create a relationshop relationship between the contenu conten of your columns, and the location of the data in the PrestaShop catalog.

...

The table above lists all backups that have already been made, specifying the date of creation, age, file name and size.
To create a new backup of the database, click on "Create a new backup". You then arrive on the following notification:The process starts, and you then receive a notification.

You are then prompted to click on the link "download the backup file" to save your database in the SQL format (and .sql file extension), archived in BZip2 format (.bz2). Put your backup in a safe place, for you might need it at any given time. Furthermore, you can find these backups directly on your server, in the /backup folder, under the custom-named /admin folder.

...

Here we find the usual fields:

  • CMS Category. You must have first have created new categoriescreated at least one category, otherwise you will be limited to the home-page.
  • Meta title. The name of the link to access the page.
  • Meta description. Used to describe the content of this page for search engines.
  • Meta Keywords. Used by search engines to understand what types of information the page is composed of.
  • Friendly URL. Appears in the browser; also, make it easier for search engines.
  • Page content. Must be entered to submit your information.
  • Enable. You can choose to have you page public only once you are done proofreading it, in which case you page is saved as draft.

Once all the fields are filled out, click on "Save." If activated, you can then view the result directly on your online
store.

Here is a sample page:

Creating a New CMS Category

...

PrestaShop's robots.txt generation tools simply creates create a file with exclusion directives for files and directories that are not meant to be public, and should not be indexed.

...

They can reach form by clicking on the box on the front-office:.

You can choose how these stores are displayed in the front-office.

...

As usual, click "Add New" to reach the following creation form:.

Fill-in as many of the fields as possible, as it will be displayed to your customers right within the map:.

Configuration Information

...

Not any app can access your store through the PrestaShop webservice: you decide which can, and what they can do. Every app as has a unique connection key, with specific access rights.

...

Errors happen. Most of the time, you are not aware of them because the system handles them silently. But you might want to know about them, in order to be able to correct the most regular ones, and insure a better stability for your shop.

The "Logs" sub-tab is were where you can have a look at the PHP errors that happen. They are logged in the sub-tab's central table, and are presented in 4 types (here with original explanations from PHP.net):

  • Informative only. Run-time notices. Indicate that the script encountered something that could indicate an error, but could also happen in the normal course of running a script.
  • Warning. Run-time warnings (non-fatal errors). Execution of the script is not halted.
  • Error.
  • Major issue (crash). Fatal run-time errors. These indicate errors that can not cannot be recovered from, such as a memory allocation problem. Execution The execution of the script is halted.

You can also receive a notification about the latest error. Notifications are sent to the shop owner's e-mail address, and you can configure the degree of importance at which you should start receiving such e-mails: use "3" if you only want to know about major issues, "1" if you want to know about everything, even the smallest notice. The default is "5": , meaning that no notification is sent.

Choose the level, and click "Save".

...

The "Modify your options" button at the bottom of the section is in fact a link to the "Options" section, at the bottom of the page.

This These options enable you to have some control on the upgrade process:

  • Don't save images: the upgrade process normally doesn't touch your images folder. If you have made a proper back of all your files, you might wish to let the process take care of that folder too, in order to have a clean install again and re-upload your files. Nevertheless, it not recommended to do this.
  • Keep theme "prestashop": the upgrade process overwrites the default theme with its latest incarnation. If you have made changes to the theme directly, you can protect these changes by choosing "Yes". As a reminder, it is NOT recommended to edit the default theme! You should make a copy of the theme, and make changes to that copy.
  • Keep translations: same as for the default theme, if you have made changes to the PrestaShop translation files, you can protect theses these changes by choosing "Yes".

...

Once you have made sure your install is still correct, active your shop using the option in the "Preferences" tab, at the top of the options list, then make tests on your front-office: browse products, sort them, try to order one, etc. In short, go through the entire buying process, in order to make sure that you won't miss a sale.

Everything Is everything working fine? Congratulations, you know have successfully upgraded your PrestaShop install!

...

PrestaShop's own backup files are saved on your server, and if it turns out your an update has gone badly, you can find them in the "Rollback" section of the "Upgrade" sub-tab.

...

The rollback's status is indicated at the same place location as the upgrade process'.