- Issue created by @akalam
- Merge request !165Issue #3413405: Fatal error when importing configuration with new facets and... → (Open) created by akalam
- last update
almost 2 years ago 424 pass, 2 fail - Status changed to Needs review
almost 2 years ago 10:42am 9 January 2024 - last update
almost 2 years ago 424 pass, 2 fail - 🇪🇸Spain akalam
Created a MR against 3.0.x branch, and uploading a plain patch version to apply safely via composer.
The last submitted patch, 3: facets-3413405-3.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- Merge request !166Issue #3413405: Fatal error when importing configuration with new facets and... → (Open) created by akalam
- last update
almost 2 years ago 424 pass, 2 fail - Status changed to Needs review
almost 2 years ago 2:04pm 10 January 2024 - 🇪🇸Spain akalam
The MR 165 wasn't solving the issue. I created a new MR with a different approach. The problem seems to be during the creation of the view, not during the creation of the facet. Seems like the depends on the view (this is correct) but view is having the facets as exposed filters so the facet source is being initialized at that time. The new approach is to skip the initialization during the config import.
- last update
almost 2 years ago 424 pass, 2 fail - Status changed to Closed: won't fix
7 months ago 4:31pm 24 March 2025 - 🇪🇸Spain akalam
This issue is no longer relevant as the facets module has removed the views_exposed_filters url_processor on the version 3.0.0