Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update upgrading search #6385 #1843

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

alhambrav
Copy link
Member

Ticket reference or full description of what's in the PR

Update upgrading search section for:

  • upgrading 3.1.x to 4.2.0
  • upgrading 4.0.x to 4.2.0
  • remove the section upgrading 4.1.x to 4.2.0 since the error that appears is now resolved in the OpenSearch version used in 4.2.0

craftercms/craftercms#6385

Copy link
Member

@sumerjabri sumerjabri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about upgrading from 4.1 to 4.2? Even if there is nothing to do, we should have a section that says that.

@sumerjabri
Copy link
Member

@yacdaniel bump


#. Run the ``post-upgrade.sh`` script from the install that's being upgraded. Before starting CrafterCMS, you'll need to configure the installation root directory to use Java version 17. Remember to read the release notes or any relevant upgrade articles and make any necessary manual changes before running the `post-upgrade.sh`` script
#. Before performing the post-upgrade, please upgrade the DB in the install that's being upgraded.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmendeza isn't the upgradedb now removed from the upgrade scripts and done automatically? related to https://github.com/craftersoftware/craftercms/issues/1010

Copy link
Member

@jmendeza jmendeza Oct 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes @yacdaniel, DB upgrade would happen on startup. The command itself is not removed though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants