{"action":"created","issue":{"url":"https://api.github.com/repos/joomla/joomla-cms/issues/9534","repository_url":"https://api.github.com/repos/joomla/joomla-cms","labels_url":"https://api.github.com/repos/joomla/joomla-cms/issues/9534/labels{/name}","comments_url":"https://api.github.com/repos/joomla/joomla-cms/issues/9534/comments","events_url":"https://api.github.com/repos/joomla/joomla-cms/issues/9534/events","html_url":"https://github.com/joomla/joomla-cms/issues/9534","id":142811490,"number":9534,"title":"Error when saving file after updating to Joomla 3.5","user":{"login":"ggeorgg","id":13244552,"avatar_url":"https://avatars.githubusercontent.com/u/13244552?v=3","gravatar_id":"","url":"https://api.github.com/users/ggeorgg","html_url":"https://github.com/ggeorgg","followers_url":"https://api.github.com/users/ggeorgg/followers","following_url":"https://api.github.com/users/ggeorgg/following{/other_user}","gists_url":"https://api.github.com/users/ggeorgg/gists{/gist_id}","starred_url":"https://api.github.com/users/ggeorgg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ggeorgg/subscriptions","organizations_url":"https://api.github.com/users/ggeorgg/orgs","repos_url":"https://api.github.com/users/ggeorgg/repos","events_url":"https://api.github.com/users/ggeorgg/events{/privacy}","received_events_url":"https://api.github.com/users/ggeorgg/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/joomla/joomla-cms/labels/No%20Code%20Attached%20Yet","name":"No Code Attached Yet","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":45,"created_at":"2016-03-22T23:36:11Z","updated_at":"2016-03-25T13:27:20Z","closed_at":null,"body":"#### Steps to reproduce the issue\r\nUpdate Joomla 3.4 with Joomla-Updater\r\nOpen an article and save it.\r\n\r\n#### Expected result\r\nNo error messages.\r\n\r\n#### Actual result\r\ngetting the following error:\r\n\r\n`Fehler\r\nSpeichern fehlgeschlagen! Fehler: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0-11' for key 'PRIMARY'`\r\n\r\n#### System information (as much as possible)\r\nPHP 7.0 as CGI\r\nMySQL 5.5.46\r\n\r\n#### Additional comments\r\nThe good thing is: The article is saved to the database even if I get this error. \r\n\r\nHow can I figure out where I have duplicate entries? How did this happen? Has it something to do with my recent update of Joomla to 3.5?\r\nHow can I solve this problem or should I just use a backup and try again?\r\n"},"comment":{"url":"https://api.github.com/repos/joomla/joomla-cms/issues/comments/201275449","html_url":"https://github.com/joomla/joomla-cms/issues/9534#issuecomment-201275449","issue_url":"https://api.github.com/repos/joomla/joomla-cms/issues/9534","id":201275449,"user":{"login":"sg08234","id":13982821,"avatar_url":"https://avatars.githubusercontent.com/u/13982821?v=3","gravatar_id":"","url":"https://api.github.com/users/sg08234","html_url":"https://github.com/sg08234","followers_url":"https://api.github.com/users/sg08234/followers","following_url":"https://api.github.com/users/sg08234/following{/other_user}","gists_url":"https://api.github.com/users/sg08234/gists{/gist_id}","starred_url":"https://api.github.com/users/sg08234/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sg08234/subscriptions","organizations_url":"https://api.github.com/users/sg08234/orgs","repos_url":"https://api.github.com/users/sg08234/repos","events_url":"https://api.github.com/users/sg08234/events{/privacy}","received_events_url":"https://api.github.com/users/sg08234/received_events","type":"User","site_admin":false},"created_at":"2016-03-25T13:27:20Z","updated_at":"2016-03-25T13:27:20Z","body":"I redid everything (Akeeba Restore website / database from version 3.4.8 to empty website / database) and Joomla update to 3.5 through the update hint on the admin start page.\r\nThe database obviously is not updated by this procedure (can be seen in extension | maintenance| database). A database repair seems to work (no database error messages after the repair anymore) but does not eliminate the SQL-errors."}}