@newme154 - It appears that your error is due to an incorrect file name; you have 55 at the end instead of the53 that @mikepadiernos used. i.e. What you've pasted here show the file as https://www.drupal.org/files/issues/2024-04-01/simple-sitemap-files-support-for-version-4-2947456-55.patch, but it should have been https://www.drupal.org/files/issues/2024-04-01/simple-sitemap-files-support-for-version-4-2947456-53.patch (the later being the link from comment #55).
emanaton → created an issue.
Ha! Sorry about that. Thanks for the cleanup of me file-piddle there, murilohp.
emanaton → created an issue.
This should fix the issue!
emanaton → created an issue.
Proposed simple patch to fix this issue:
emanaton → created an issue.
Aaaaand here's a re-roll of the #70 for use in 10.1.5:
Reroll of the excellent work in #49 for the 4.1.7 branch, this time without bugs!!!
Reroll of the excellent work in #49 for the 4.1.7 branch:
laura.gates → credited emanaton → .
Here's a reroll of #24 for core version 9.5.11
I'm having this issue as well, but have a solution which I'm pasting here for posterity and to help the next coder who's still having this issues.
My fix is to add the following as an additional submit function on the Views Exposed Form (i.e. adding this function to the `$form['#submit']` array within a `hook_form_views_exposed_form_alter` implementation):
/**
* Set the default sort from the BEF filter in the $form_state.
*
* This is being done so that the view's pagination URLs have a default value
* set. Without this, click on pagination before executing a sort results in
* an error message being displayed: "An illegal choice has been detected.
* Please contact the site administrator."
*
* @param $form
* @param \Drupal\Core\Form\FormStateInterface $form_state
*
* @return void
*/
function my_theme_fix_bef_filters(&$form, \Drupal\Core\Form\FormStateInterface $form_state) {
if (
// if there's "sort_by" then the user hasn't explicitly set the sort order.
!$form_state->getValue('sort_by')
// check that the better exposed filter combined sort option has been set...
&& !empty($form['#info']['sort-sort_bef_combine']['value'])
// ... and get whatever key it's configured under for ease of reference...
&& ($combined_sort_key = $form['#info']['sort-sort_bef_combine']['value'])
// ... and check if the sort options are exposed to the user...
&& !empty($form[$combined_sort_key]['#options'])
// ... and that there's a usable key set as the first sort option.
&& !!($sort_value = array_key_first($form[$combined_sort_key]['#options']))
) {
$form_state->setValue($combined_sort_key, $sort_value);
}
}
Thanks for the updated code, tostinni! I need this now and don't want to wait for the release, so I'm adding your changes as a patch. Looking forward to this excellent module as it develops! =o)
Of possible interest, we solved this issue on our suite of sites by applying the patch found at: https://www.drupal.org/project/drupal/issues/2845144#comment-14574850 🐛 User can't reference unpublished content even when they have access to it Needs work
Of possible interest, we solved this issue on our suite of sites by applying the patch found at: https://www.drupal.org/project/drupal/issues/2845144#comment-14574850 🐛 User can't reference unpublished content even when they have access to it Needs work
Stick with me -- I'll get this right yet! I had a request come down that the various windows characters be preserved, so I've added yet another line to the mix to cover that.
Not only will I provide you with a problematic file, I'll give you yet another patch! My users are now including characters that cause whole fields not to be imported. In this case, it's the "OPA Findings" column that's borked - revery record past the third row comes in with that field blank.
The attached patch is for the current version of the module (i.e. 8.x-1.15), and cleanses both the headers and the fields.