Search Indexes issue - advanced index updated only after 2nd save/apply

Sorry I don't know if I can post this problem here. I'm working on some custom template coding, and found this problem.

The flexicontent version is 3.0.9-rc6. I forgot if it happened in 3.0.8. But I remember it worked well before I upgrade to 3.0.8.

1. I set some fields for "Text search", please check image 1.
2. When I add an item from frontend, and check the index advanced of this item, all index are shown but no field104. The type of field104 is "Select". Please check image 2.
3. After I save(apply) the item again, the field104 occurs. Please check image 3.

image1 https://drive.google.com/open?id=0B9R0LrpWYtsgYnY0WlZMZHFCeUE
image2 https://drive.google.com/open?id=0B9R0LrpWYtsgRmFFenpwdV9od3c
image3 https://drive.google.com/open?id=0B9R0LrpWYtsgMU8zRWhBenYtS1E

(Sorry when I attached the image and it replied "500 Internal Server Error Fatal Error was detected! Please contact the site owner." So I just put the images on google drive.)

I don't know if any setting I missed, or it's a bug. I think all fields set to be index should be saved when the item is submitted for the first time, right?

Thanks,
Lomu

How is the 1st save done ?

is it done with "apply type" button or with "save" button ?

Hi

I just tried it.
All the same result with "Apply" and "Save & Return" buttons.

Thanks,
Lomu

Hello

i confirm the issue and testing a fix,

- but i think it is best to modify installation script to mark all non core searcable fields as dirty,
so that "please re-index" warning message is shown after upgrading FLEXIcontent to v3.0.9

Hi
And for the 2nd saving, both "Save" and "Save & Return" work.

Thanks,
Lomu

ggppdk wrote: Hello

i confirm the issue and testing a fix,

- but i think it is best to modify installation script to mark all non core searcable fields as dirty,
so that "please re-index" warning message is shown after upgrading FLEXIcontent to v3.0.9

OK thanks.
But I think it will be solved in next upgrade, right?
Because the frontend users can't do re-index.

Thanks,
Lomu