> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/xoops-install-upgrade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/xoops-install-upgrade/upgrading/upgrade/ustep-04.md).

# After the Upgrade

## Update the System Module

After all needed patches have been applied, selecting *Continue* will set everything up to update the **system** module. This is a very important step and is required to complete the upgrade properly.

![XOOPS Update System Module](/files/-L_EkQUdOYP9Toxj1D35)

Select *Update* to perform the update of System module.

## Update Other XOOPS Supplied Modules

XOOPS ships with three optional modules - pm (Private Messaging,) profile (User Profile) and protector (Protector) You should do an update on any of these modules that are installed.

![XOOPS Update Other Modules](/files/-L_EkQUfw-non_j9735U)

## Update Other Modules

It is likely that there are updates to other modules that might enable the modules to work better under your now updated XOOPS. You should investigate and apply any appropriate module updates.

## Review New Cookie Hardening Preferences

The XOOPS 2.7.0 upgrade adds two new preferences that control how session cookies are issued:

* **`session_cookie_samesite`** — controls the SameSite cookie attribute. `Lax` is a safe default for most sites. Use `Strict` for maximum protection if your site does not rely on cross-origin navigation. `None` is only appropriate if you know you need it.
* **`session_cookie_secure`** — when enabled, the session cookie is only sent over HTTPS connections. Turn this on if your site runs on HTTPS.

You can review these settings under System Options → Preferences → General Settings.

## Validate Custom Themes

If your site uses a custom theme, walk through the front end and admin area to confirm that pages render correctly. The upgrade to Smarty 4 may affect custom templates even if the preflight scan passed. If you see rendering problems, revisit [Troubleshooting](/xoops-install-upgrade/upgrading/upgrade/ustep-03.md).

## Clean Up Installation and Upgrade Files

For security, remove these directories from your web root once the upgrade is confirmed working:

* `upgrade/` — the upgrade workflow directory
* `install/` — if present, either as `install/` or as a renamed `installremove*` directory

Leaving these in place exposes the upgrade and installation scripts to anyone who can reach your site.

## Open Your Site

If you followed the advice to *Turn your site off*, you should turn it back on once you have determined it is working correctly.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://xoops.gitbook.io/xoops-install-upgrade/upgrading/upgrade/ustep-04.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.