The default schema would trigger an error if the wrong schema.xml was there. The correct schema is being read and it exists in the same location as this file.
I am having the same 500 response from Solr. Indexing and search are working as expected.
solr 9.4
drupal 9.5.11
seach_api_solr 4.3.1
I am confirming the same behavior on a fresh Drupal 11.0.0 install
shadysamir → created an issue.
shadysamir → created an issue.
The article/post is already calling the composer recommended flow "wrong" which really irks me. But beside the attitude, having one developer use composer to pull packages code and committing them while other developers merely pulling the downloaded code would create a mess. Why is one developer responsible for composer managing the project? And why bloat a repo with code that's already hosted in other repos and we're not managing it in any way? And for production there is a good use for --no-dev. Using composer was a major step towards modernizing the DX in Drupal. I don't understand why anyone would want to take it back.
I wouldn't even commit development css and js theme files built from sass and js. I build minified and uglified production versions as part of production deployment flow.
I applied #270 to an exposed filter on a timestamp field. I get this warning once I apply the filter:
Warning: Undefined array key "value" in Drupal\views\Plugin\views\filter\NumericFilter->acceptExposedInput() (line 426 of /home/shadysamir/work/almanassa/almanassa/web/core/modules/views/src/Plugin/views/filter/NumericFilter.php).
followed by
Warning: Undefined array key "value" in Drupal\views\Plugin\views\filter\Date->acceptExposedInput() (line 161 of /home/shadysamir/work/almanassa/almanassa/web/core/modules/views/src/Plugin/views/filter/Date.php).
both are trying to read this->value['value'] when the array is:
date: "2023-05-01"
time: "00:00:00"
type: "date"
The filter is not applied (not added to the SQL statement)
Drupal 9.5.3