Model.Content.GetPropertyValue not working on some widgets, but it is working when loaded in the backoffice
Something is really off here, but I have no clue what I have done, or what is wrong, but when I use the doctype grid editor it doesn't always work...
It used to work in the past, in fact, many grid-widgets still work, but I have some that don't work... if I try Model.Content.GetPropertyValue
When I check the content of Model.Content I see that the properties are empty... The Model.Content.Name is filled correctly, but that's it...
But the weird thing is that it DOES work in the backoffice, it renders my content as it should, just the frontend doesn't...
I have the latest version of the plugin installed and I'm running on Umbraco 7.3.1
I'm pulling all of my hair out of my head because of this, I need help before I turn bald ;-) I hope someone can help me out on this one...
I haven't heard of this scenario before, where the preview works in the back-office, but the data isn't there in the front-end.
My gut feeling is that somehow the underlying JSON data for the DTGE cell has become corrupted. But this is still strange, as we use the same code to convert the value for both the back-office and front-end.
Given I don't know the ins & outs of your project set-up, (e.g. what other packages you are using, etc), my advice would be...
Try republishing the content page, see if that makes a difference. (I'm assuming that you've already tried this?)
Make a copy of the content page/node, see if that has the same issue.
Delete the DTGE cell and re-enter the data, then republish the page.
Sorry I don't have any better advice at the moment. I hope this can help?
I tried all of that but to no avail. (had the issue for a while when i sent the message last night)
I resorted to reinstalling everything with nuget and doing so a few times caused some other issues but I persisted and now it works again... and the other issues (caused by the reinstall) are gone too, lets hope it stays this way...
it's all so weird... :-) but hey, it works! :-)
Cool that the issue hasn't come back, but sucks to hear that you had to go through all that. Let us know if anything weird happens like that again, (I hope not).
Model.Content.GetPropertyValue not working on some widgets, but it is working when loaded in the backoffice
Something is really off here, but I have no clue what I have done, or what is wrong, but when I use the doctype grid editor it doesn't always work... It used to work in the past, in fact, many grid-widgets still work, but I have some that don't work... if I try Model.Content.GetPropertyValue
When I check the content of Model.Content I see that the properties are empty... The Model.Content.Name is filled correctly, but that's it... But the weird thing is that it DOES work in the backoffice, it renders my content as it should, just the frontend doesn't...
I have the latest version of the plugin installed and I'm running on Umbraco 7.3.1 I'm pulling all of my hair out of my head because of this, I need help before I turn bald ;-) I hope someone can help me out on this one...
Hi Sandro,
Sorry to hear about the hair pulling :-(
I haven't heard of this scenario before, where the preview works in the back-office, but the data isn't there in the front-end.
My gut feeling is that somehow the underlying JSON data for the DTGE cell has become corrupted. But this is still strange, as we use the same code to convert the value for both the back-office and front-end.
Given I don't know the ins & outs of your project set-up, (e.g. what other packages you are using, etc), my advice would be...
Sorry I don't have any better advice at the moment. I hope this can help?
Cheers,
- Lee
I tried all of that but to no avail. (had the issue for a while when i sent the message last night) I resorted to reinstalling everything with nuget and doing so a few times caused some other issues but I persisted and now it works again... and the other issues (caused by the reinstall) are gone too, lets hope it stays this way... it's all so weird... :-) but hey, it works! :-)
Cool that the issue hasn't come back, but sucks to hear that you had to go through all that. Let us know if anything weird happens like that again, (I hope not).
Cheers,
- Lee
is working on a reply...