not even sure where to begin - i think the bottom line is that it appears that flexi is maybe not ready for 4.7 release yet??? which at this stage seems kind of scary.

- more info in 2 bug posts preceding this (too bad you can see poster to know which are mine)
- i have latest CVS for 4.7
- i have existing flexinode which was upgraded from 4.6 to 4.7
- i try to add a field
- my table output now shows no results

- if i edit one of existing records and add content for new field; then do my table output.. i now get that single result

- it seems as though results don't return records that dont have a field defined for new field type (which will be all legacy records) - this seems wrong to me - pretty sure i should be able to add fields

Comments

Bèr Kessels’s picture

Bèr Kessels commented

I don't understand your problem: can you not add fields (you mentioned that ni another thread too) OR can you not show the tables?

Please be verbose in what versions you use etceteras.

karger’s picture

karger commented

I can second this bug report. I have added a field and now the table shows "no results for your search". By looking directly at the nodes, I have confirmed that the data is still there; however, the new fields are not showing up in the node presentation (this may be because the presentation of the node is cached? I'm not sure how that is handled). At the very least, I would like to recover the ability to view the old data; however, removing the new field did not do this.

liquidcms’s picture

liquidcms commented

i thought i should re-test this with a new site install and the latest (4.7 CVS) version of flexinode.

- add a flexi type with 2 fields
- add 2 items of this new type
- go to flexinode/table/1 and i see the table listing showing the 2 items i just created
- add new field to my flexi type
- now when i go to flexinode/table/1 it shows "no results"
- if i delete the new field; the table again shwos the 2 results.

Without lokong into this too much i think the SQL query created to build the table is incorrect - it searches for the items that have ALL the fields as per the new flexi type - but this will not match the 2 original items

2 solutions would seem to be:

- when a new field is added the old items need to be padded with empty records for this new field

OR

- modify the query to look for all node of the flexi type and simply pull whatever field info is available and just put "" if no record available for each field

2nd method is likely the best

Couple questions:

- do we agree that you shold be able to add fields to an existing flexi type (seems like obvious YES, but thought i'd ask)
- did you used to be able to do this in older versions of flexinode?? seems hard to imagine no one has come across this

Bèr Kessels’s picture

Bèr Kessels commented

Closely related to http://drupal.org/node/68641 (not a dupe)