| Update: Problems with added/updated pages in article tree in postgres setting | Daniel Holbach | 10/11/15 09:03 | Hello everybody, as you can see https://stackoverflow.com/questions/33284171/ Daniele helped us out with the question and gave us a couple of tips on how to proceed. The takeaway was:
We tried option 1. It worked in a local, simple postgres setting, but didn't work on staging (also postgres). Instead of trying to figure out the differences in the database configuration (or whatever else), we decided to spend some more time on 2., as we had the Django/Django CMS upgrade in our cards as well. Unfortunately, even with the most recent Django/Django CMS (and treebeard) we experience the same problem. The importer (using cms.api.create_page) works in a simple sqlite setting, but not using postgres. If anyone wants to help out with this, I prepare two branches to test this:
You mostly just should have to run the ./setup script to see the problem unfold. It contains very basic test data and if you open the "external docs branches" in the admin view, you can trigger an import of them. If you compare the page overview afterwards you will notice the changes. Another thing I noticed: some of the articles seem to be in status 'draft' even though we ran page.publish() in the code. Maybe you have an idea? Thanks a lot everyone for your support and help, it's much appreciated! Have a great day, Daniel |