Answers.Body: <p>solved it with a rebuilded project file locally.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-17T12:15:34.440Z
Answers.LastActivityDate: 2019-12-17T12:56:15.123Z
Answers.LastEditDate: 2019-12-17T12:56:15.123Z
Answers.UserDisplayName: Peter L
Body: <p>I had a table field and created a new super table field to try something.
  After that I removed my table field and gave my super table field the same handle like the old table field had.</p>
  
  <p>I did it locally and synced it via git. 
  After that I wanted to sync my project.yaml. 
  I tried <code>./craft project-config/sync</code> and I got a error: <code>error: Getting unknown property: craft\fields\Table::contentTable</code></p>
  
  <p>I tried to remove the complete section on my production server but still no changes. At the moment I have no Idea what I could do…</p>
  
  <p>Of course <code>./craft project-config/rebuild</code> works but then I have my old project.yaml</p>
  
  <p>Thanks for any help!</p>
  
Tags: <craft3><projectconfig><project.yaml>
Title: project.yaml synchronize error (not usable anymore)
ThreadText: # project.yaml synchronize error (not usable anymore)
  
  (Asked by: username_0 on 2019-12-17)
  
  I had a table field and created a new super table field to try something.
  After that I removed my table field and gave my super table field the same handle like the old table field had.
  
  I did it locally and synced it via git.
  After that I wanted to sync my project.yaml.
  I tried `./craft project-config/sync` and I got a error: `error: Getting unknown property: craft\fields\Table::contentTable`
  
  I tried to remove the complete section on my production server but still no changes. At the moment I have no Idea what I could do…
  
  Of course `./craft project-config/rebuild` works but then I have my old project.yaml
  
  Thanks for any help!
  
  **Tags:** craft3, projectconfig, project.yaml
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-12-17. Score: 1 | Accepted answer
  
  solved it with a rebuilded project file locally.
  
  
  ---
  
  