#3
🐛
Date range filter not working if min and max date field have same date value in view
Closed: duplicate
helped me.
In my case I used "node_field_data.created BETWEEN"
But is is not a universal solution.
This is a serious bug. I wonder how other people overcome it.
Patch in #27 fixes issue for me too.
This was a scary bug.
Took me some time until google sent me to this page.
Same problem here.
Charts 5.0.11
Drupal 10.1.6
If I select Enable color changer widget then I can change the color manually.
I have exactly the same problem.
Any solutions ?
I am trying to access route
diff.revisions_diff: '/node/{node}/revisions/view/{left_revision}/{right_revision}/{filter}'
from inside hook_node_update(NodeInterface $node)
but i get
TypeError: Argument 3 passed to Drupal\diff\Controller\PluginRevisionController::compareEntityRevisions() must implement interface Drupal\Core\Entity\ContentEntityInterface, null given
probably because the new revision is not saved when the hook runs.
Is it related to this issue and is there a workaround?
Same problem here. Any proposed solution or patch that will remain when drupal gets updated?
@xamount
Same.
I got the error but am not using the LiteSpeed Cache module.
I have the same question.
I found the following on https://drupal.stackexchange.com/questions/221410/how-to-add-a-database-...
/**
* Add SQL index on published_date base field
*/
function MY_MODULE_update_8010(&$sandbox) {
// Add index
// ALTER TABLE $table ADD INDEX $name ($column1, $column2..)
db_query("ALTER TABLE node_field_data ADD INDEX node_field__published_date (published_date)");
}
But after examining the drupal schema db shouldn't the query be something like
ALTER TABLE node__field_fieldname ADD INDEX node__field_fieldname (field_fieldname_value) ?
Same problem here. Just updated from 9.5.11 => 10.1.6
Cleared cache a bunch of times but it pops up in the logs quite frequently.
Yes.
Since I changed the location to "private://filefield_paths" I haven't had the problem again.
I had upgraded to 8.x-1.0-beta6 weeks ago but the exact same problem happened first time today.
I agree with #24 last paragraph.
I had upgraded to 8.x-1.0-beta6 weeks ago but the exact same problem happened first time today.
Changed the temporary file location to "private://" and hoping it fixes the problem.
Had the same problem with Drupal 9.5.3 and 6.0.2
Applied patch #4 and problem solved.