Your code publishes a new version of the content (check the versions gadget to confirm this). This means that you are no longer looking at the primary draft therefore the UI makes it readonly. You can hook into the publishing event which should stop this behaviour or don't publish a new version of content in your Save method.
Thank you David, I didn't relise that I was hooked in to the wrong method, changed it from
and it works perfectly.
I am hooking in to the PublishedContent Event within Episerver, so when a user publishes a particular page type some logic is performed (create pdf) and a string value is saved in to one of the properties.(the path to the pdf)
This is working, the PDF is created and the path to the PDF is also saved.
However the problem I have is after the publish is complete, all the properties become readonly, I have to click another node, then click that one again before I can edit it. - Is this normal, or is it something to do with the way I do the save?
This is my code:
This is a screen shot after saving
If I click another node in the tree, then click this one again, it goes back to normal and all the data is saved correctly.