I really like the tabular view but a fairly big problem is after I add another field (which is NOT flagged as a required field) to that content type, ZERO entries will display in the tabular view. If you go back and open of the the entries in this content type, hit submit this entry will show up in the Tabular view again.

CommentFileSizeAuthor
#5 tablefix46.diff1.33 KBgeodaniel
#4 tablefix.diff1.29 KBgeodaniel
#1 flexinode_1.patch1.55 KBcrunchywelch

Comments

crunchywelch’s picture

crunchywelch commented
Component: User interface » Code
Assigned: Unassigned » crunchywelch
StatusFileSize
new flexinode_1.patch1.55 KB

This is a patch against drupal cvs that fixes this issue. It has to do with the sql statement joining the data fields, since there are no records for new fields on poreviously created nodes, it returns nothing. This patch changes the sql statement to only retrieve the basic node inforamtion and load the field data afterward using flexinode_load.

jonbob’s picture

jonbob commented

Could this cause problems with the table sorting? I need to investigate further.

geodaniel’s picture

geodaniel commented
Version: 4.5.x-1.x-dev » master

Has there been any further investigation into this issue? I see the patch has not been applied as the problems still exist in 4.7 flexinode.

geodaniel’s picture

geodaniel commented
StatusFileSize
new tablefix.diff1.29 KB

The attached patch is based on crunchywelch's patch against 4.5, but re-rolled to work with 4.7.

Table sorting does not appear to be affected, working as expected.

geodaniel’s picture

geodaniel commented
Assigned: crunchywelch » geodaniel
StatusFileSize
new tablefix46.diff1.33 KB

This patch can be applied againt 4.6 to get it to work properly (note the added DISTINCT command in the SQL).

urbanlegend’s picture

urbanlegend commented
Component: Code » flexinode.module (core)
Issue summary: View changes
Status: Needs review » Closed (outdated)

Given that this issue has not been updated in 10 years or more, I am closing this ticket as outdated (no longer needed and/or relevant). However, if anyone feels this represents an issue that is still being encountered in the current version of Drupal, please reopen and/or provide additional comments.