{"action":"created","issue":{"url":"https://api.github.com/repos/WeTeam/WeBlog/issues/241","repository_url":"https://api.github.com/repos/WeTeam/WeBlog","labels_url":"https://api.github.com/repos/WeTeam/WeBlog/issues/241/labels{/name}","comments_url":"https://api.github.com/repos/WeTeam/WeBlog/issues/241/comments","events_url":"https://api.github.com/repos/WeTeam/WeBlog/issues/241/events","html_url":"https://github.com/WeTeam/WeBlog/issues/241","id":215870758,"number":241,"title":"WeBlog entries prompting a save action immediately upon creation","user":{"login":"ECYR-TG","id":26582494,"avatar_url":"https://avatars2.githubusercontent.com/u/26582494?v=4","gravatar_id":"","url":"https://api.github.com/users/ECYR-TG","html_url":"https://github.com/ECYR-TG","followers_url":"https://api.github.com/users/ECYR-TG/followers","following_url":"https://api.github.com/users/ECYR-TG/following{/other_user}","gists_url":"https://api.github.com/users/ECYR-TG/gists{/gist_id}","starred_url":"https://api.github.com/users/ECYR-TG/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ECYR-TG/subscriptions","organizations_url":"https://api.github.com/users/ECYR-TG/orgs","repos_url":"https://api.github.com/users/ECYR-TG/repos","events_url":"https://api.github.com/users/ECYR-TG/events{/privacy}","received_events_url":"https://api.github.com/users/ECYR-TG/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"alan-null","id":6848691,"avatar_url":"https://avatars3.githubusercontent.com/u/6848691?v=4","gravatar_id":"","url":"https://api.github.com/users/alan-null","html_url":"https://github.com/alan-null","followers_url":"https://api.github.com/users/alan-null/followers","following_url":"https://api.github.com/users/alan-null/following{/other_user}","gists_url":"https://api.github.com/users/alan-null/gists{/gist_id}","starred_url":"https://api.github.com/users/alan-null/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alan-null/subscriptions","organizations_url":"https://api.github.com/users/alan-null/orgs","repos_url":"https://api.github.com/users/alan-null/repos","events_url":"https://api.github.com/users/alan-null/events{/privacy}","received_events_url":"https://api.github.com/users/alan-null/received_events","type":"User","site_admin":false},"assignees":[{"login":"alan-null","id":6848691,"avatar_url":"https://avatars3.githubusercontent.com/u/6848691?v=4","gravatar_id":"","url":"https://api.github.com/users/alan-null","html_url":"https://github.com/alan-null","followers_url":"https://api.github.com/users/alan-null/followers","following_url":"https://api.github.com/users/alan-null/following{/other_user}","gists_url":"https://api.github.com/users/alan-null/gists{/gist_id}","starred_url":"https://api.github.com/users/alan-null/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alan-null/subscriptions","organizations_url":"https://api.github.com/users/alan-null/orgs","repos_url":"https://api.github.com/users/alan-null/repos","events_url":"https://api.github.com/users/alan-null/events{/privacy}","received_events_url":"https://api.github.com/users/alan-null/received_events","type":"User","site_admin":false}],"milestone":null,"comments":1,"created_at":"2017-03-21T20:39:48Z","updated_at":"2018-03-12T15:08:52Z","closed_at":null,"author_association":"NONE","body":"We're having an issue after a fairly extensive sitecore upgrade (including weblog versions) when creating a new blog entry. Right after clicking the blog item, creating a new entry, and naming it, a Sitecore save confirmation window will appear. This would be only a slight nuisance, but if you accept the save it clears out the bucketable settings of the item which gives an error and confuses our client. Is there some known mechanism that would execute on create and reset these standard values? I've looked through the configuration and there doesn't seem to be anything related to item creation outside of moving the file to the correct subfolder. "},"comment":{"url":"https://api.github.com/repos/WeTeam/WeBlog/issues/comments/372343194","html_url":"https://github.com/WeTeam/WeBlog/issues/241#issuecomment-372343194","issue_url":"https://api.github.com/repos/WeTeam/WeBlog/issues/241","id":372343194,"user":{"login":"amir-begic","id":18397369,"avatar_url":"https://avatars2.githubusercontent.com/u/18397369?v=4","gravatar_id":"","url":"https://api.github.com/users/amir-begic","html_url":"https://github.com/amir-begic","followers_url":"https://api.github.com/users/amir-begic/followers","following_url":"https://api.github.com/users/amir-begic/following{/other_user}","gists_url":"https://api.github.com/users/amir-begic/gists{/gist_id}","starred_url":"https://api.github.com/users/amir-begic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amir-begic/subscriptions","organizations_url":"https://api.github.com/users/amir-begic/orgs","repos_url":"https://api.github.com/users/amir-begic/repos","events_url":"https://api.github.com/users/amir-begic/events{/privacy}","received_events_url":"https://api.github.com/users/amir-begic/received_events","type":"User","site_admin":false},"created_at":"2018-03-12T15:08:52Z","updated_at":"2018-03-12T15:08:52Z","author_association":"NONE","body":"Hi!\r\n\r\nI've been encountering the same issue and I don't think it has to do anything with the upgrade. I'm using WeBlog 3.10 on a Sitecore 8.1 rev. 160302 (8.1 Update-2). \r\nThe save dialog only appears when the \"Standard fields\" checkbox (Content Editor -> \"View\"-Ribbon) is activated. If you answer the overwrite dialog with \"Yes\", the item is created and loses the Item Buckets standard values. :( At least other standard values, for example \"Disable Comments\", are not affected by the issue.\r\nI've tested the whole thing on a fresh Sitecore 8.1 Update-2 SIM install and it behaves the same as it does within our customers Sitecore instance.\r\n\r\nAs a workaround we could advise the authors to disable the checkbox, but I'd really like to find a better solution than that. If you need any "}}
{"actor":{"display_login":"amir-begic"}}