Jump-start config not updated with release giving mismatch schema error message in status report

Created on 11 December 2023, about 1 year ago
Updated 24 January 2024, 11 months ago

Respect the submission guidelines above! Drupal.org issue forks cause additional work for the project maintainer!

Setup

  • Solr version: 8 (but note issue is in 7)
  • Drupal Core version: 10.1
  • Search API Solr version: 4.3.1

Issue

An issue is being reported in status report of a mismatched configuration between server and module when using the jump-start configuration.

Schema not up to date
There are some configuration elements missing in the Solr server schema Lagoon Solr. This is likely due to using an outdated version of either Drupal or Solr. The recommended version is: drupal-4.3.1-solr-8.x. An updated config.zip should be downloaded and deployed to your Solr server.

This is caused by the jump-start config not being updated to the latest version number before the release was created:

https://git.drupalcode.org/project/search_api_solr/-/blob/4.3.1/jump-sta...

Looks the same for solr 7 config as well - nothing that can be done about it since it's version dependant - unless maybe decoupling the jump-start configuration version away from the module release version.

🐛 Bug report
Status

Fixed

Version

4.3

Component

Code

Created by

🇦🇺Australia RichardGaunt Melbourne

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024