I could not confirm this issue. Non-existent entity pages with dynamic path aliases correctly displayed a 404 error. Please reopen the ticket with additional information if the problem persists.
robbiehobby → made their first commit to this issue’s fork.
Closing due to insufficient information to confirm the issue. Please reopen when you have additional details.
I understand how comments could be useful, however, this module relies on the Drupal core conditions API, which manages path parsing. I prefer not to introduce changes that deviate from the core's behavior or add unnecessary code. Thanks for the recommendation though.
As a workaround, you could keep a plain text note or README in the project to describe the configuration.
Drupal 11 support has been released. Thanks for the co-maintainer offer.
Merged. New release will be up shortly. Thanks for the reminder.
robbiehobby → made their first commit to this issue’s fork.
greggles → credited robbiehobby → .
You'll also need to exclude the Ajax autocomplete URL. It usually looks like /ajax/autocomplete. If you're not sure, take a look at your network tab in the developer tools.
Re-rolled for 8.x-1.7
robbiehobby → created an issue.
robbiehobby → created an issue.
robbiehobby → created an issue.
robbiehobby → created an issue.
robbiehobby → created an issue.
robbiehobby → created an issue.
+1 RTBC
robbiehobby → created an issue.
Unfortunately, no because Uppy.js considers uploads as unordered. See https://github.com/transloadit/uppy/issues/1779#issuecomment-522512989. I may build an extension in the future if they don't add some kind of order support soon.
robbiehobby → created an issue.
Thanks. Merged and will be included in the next release.
+1 RTBC
Re-rolled for 10.3.x
Re-rolled for 10.3.x
robbiehobby → changed the visibility of the branch 9.1.x to hidden.
robbiehobby → created an issue.
Could you also provide the Drupal version, module version, and specify any other file related installed modules.
What does your configuration look like? I'll need more information to be able to assist you.
BramDriesen → credited robphillips → .
Took a crack at the problem. Search API Solr offers up a similar solution. Re-index is only triggered when a indexed field has changed. Tested with both in-site configuration changes and using configuration sync. There might be some edge cases. Definitely needs more eyes on it.
https://git.drupalcode.org/project/search_api_solr/-/blob/4.x/src/Plugin...
robphillips → made their first commit to this issue’s fork.
robphillips → created an issue.
At the moment it can only be added to an entity form display. Leaving this open as I might find time to convert to a form element type.
You need to re-install the module and disable the filter on every text format before uninstalling. This is a known issue in Drupal core.
robphillips → created an issue.
robphillips → made their first commit to this issue’s fork.
robphillips → created an issue.
robphillips → made their first commit to this issue’s fork.
The field definition should never be null so this patch is not correct. Take a look at the lines immediately before your changes (shown below). If the comment entity doesn't have a field something in your sites entity or configuration is broken.
$commentedEntity = $comment->getCommentedEntity();
/** @var \Drupal\field\FieldConfigInterface $fieldDefinition */
$fieldDefinition = $commentedEntity->getFieldDefinition($comment->getFieldName());
If you could provide steps to replicate on a fresh installation I will reopen.
robphillips → created an issue.
Adding D10.1 compatible patch based on latest MR.
Thanks to all for contributing. Both specific and unlimited limits have been resolved. With one caveat... unlimited is actually limited to 10,000 because the Choices.js library doesn't have an unlimited option.
robphillips → created an issue.
Sorry, I misunderstood the original support request. No, Choices.js does not support sorting of already selected items. See https://github.com/Choices-js/Choices/issues/417. Having said that, this module could add basic support using the HTML5 Drag and Drop API and the Choices.js API. I'll start to experiment to see how feasible it is.
Currently the module doesn't support custom sorting. Having said this, the Choices.js plugin has a shouldSort option and is enabled by default. Meaning all results are automatically sorted in alphanumeric order. I'm going to add a new configuration to the modules formatter to toggle the default alphanumeric sorter. When disabled one could use query or views sorting to control the order of results.
robphillips → created an issue.
robphillips → created an issue.
robphillips → created an issue.
robphillips → created an issue.