> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/v.9-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/v.9-documentation/user-guide/configuring-shop/advanced-parameters/information.md).

# Information

This page serves as a handy reminder of your PrestaShop configuration: version, server info, PHP version, MySQL version. All these prove really useful when you need to report an issue to the PrestaShop developers, or simply your webmaster or web host.

![](https://content.gitbook.com/content/f4jUT8dUfW1PrFTeHOkK/blobs/lWOZYZlzPWrxN7Ssy0IP/51839997.png)

There is one last section, titled "List of changed files". Right after you have first installed PrestaShop, the only thing that this section displays is "No change has been detected in your files".\
But after you've installed some modules and a couple of themes, made advanced changes to some override classes or deleted files altogether, this list will show the difference between your current installation of PrestaShop and what it used to look like in its pristine state. This helps you see what changes have been made to your installation... and therefore what to take into account if you want to update your store manually, or if you are moving files to a new server.

Even with a fresh installation, this section might indicate "`.gitattributes`", "`.gitignore`", "[`CONTRIBUTING.md`](http://contributing.md/)", "[`CONTRIBUTORS.md`](http://contributors.md/)" or "[`README.md`](http://readme.md/)" as missing files. These are Git-specific files, and PrestaShop does not use them, so you should not worry about them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prestashop-project.org/v.9-documentation/user-guide/configuring-shop/advanced-parameters/information.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.