Trash breaks when views data has a null value

I was trying to test the patch, but was unable to reproduce the issue based on the provided issue description. Could you please provide clearer steps to reproduce the error?

@Akhil Babu , So I am not certain about the process of reproducing the error. The current issue is occuring when I have any taxonomy values (/conteexual filters in view) set in a certain view which contains a null value.

I encountered this issue and determined it's caused by a view using a relationship that has no base table; the taxonomy_index_tid_depth view argument from core is a good example.

Best I can tell, in this scenario, we should just skip over that relationship since the module wouldn't know how to alter the query for it anyway.

The attached patch avoids attempting to alter relationship queries if they have no base table.

Can it be written to log so that it can be followed up?

If we're talking about the same issue--the lack of a base table on a relationship is not a bug. It is the expected behavior of some relationship types in Views. The Trash module needs a change like the patch in #4 to handle scenarios when the relationship has no base table.

Committed the patch from #4 to 3.x, thanks!

Automatically closed - issue fixed for 2 weeks with no activity.