Re: [mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
On Thu, Jul 30, 2015 at 12:24 AM, Déborah Leder debdeb...@gmail.com wrote: OK, but then how do you explain the fact that it worked on my second project ? There's no way I possibly could - I'm not sitting next to you and you haven't described in enough detail the exact sequence of events that took place in creating both projects. Presumably that's not even possible either - we go through the process of putting things together assuming that they'll work, without noting down every little step we take. Whereas I had really run the commands python manage.py makemigration and then python manage.py migrate and both of them had terminated normally. I did nothing more on my second project Le mercredi 29 juillet 2015 16:14:39 UTC+2, Stephen McDonald a écrit : The original error stated that the database table for the Geoloc_map model didn't exist in the database, see the relation geoloc_geoloc_map does not exist part, that's the error message. The part you focused on searching for was the SQL query that caused the error, and had nothing to do with it particularly. You say that the migrations were created and run for the new app, and I'm sure you believe that to be - but unfortunately the error says otherwise. Let's try not to talk about these things as magical - we do ourselves a disservice by creating that perception, when the reality is we simply haven't invested enough to time in studying the code and documentation which will eventually reveal how simple and boring these things really are. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
If that's the case, it sounds like a naming problem. What was the name of the old project and the app inside it (folder names)? -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
The original error stated that the database table for the Geoloc_map model didn't exist in the database, see the relation geoloc_geoloc_map does not exist part, that's the error message. The part you focused on searching for was the SQL query that caused the error, and had nothing to do with it particularly. You say that the migrations were created and run for the new app, and I'm sure you believe that to be - but unfortunately the error says otherwise. Let's try not to talk about these things as magical - we do ourselves a disservice by creating that perception, when the reality is we simply haven't invested enough to time in studying the code and documentation which will eventually reveal how simple and boring these things really are. On Thu, Jul 30, 2015 at 12:00 AM, Déborah Leder debdeb...@gmail.com wrote: I have just done it and it displays the same error page. I have managed to skirt the problem by creating another mezzanine-project, creating another django-app with a new name inside the new project and copying the exact same models.py and admin.py files. I don't understand why this works, but it does... So if you think my problem was due to some hidden bug, I can keep my project and answer your questions to help resolve it, and if not, my problem has magically been resolved. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
I have just done it and it displays the same error page. I have managed to skirt the problem by creating another mezzanine-project, creating another django-app with a new name inside the new project and copying the exact same models.py and admin.py files. I don't understand why this works, but it does... So if you think my problem was due to some hidden bug, I can keep my project and answer your questions to help resolve it, and if not, my problem has magically been resolved. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
The project name was : mystere And the app name was : geoloc I didn't think those name could cause any trouble... When I said naming problem I meant something about inside the app named geoloc, having a model called Geoloc_map. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
+1, Stephen! All the magic was removed from Django https://code.djangoproject.com/wiki/RemovingTheMagic in 2007. Mezzanine is perhaps the least magical code base I have encountered. The community, on the other hand... On Wed, Jul 29, 2015 at 10:14 AM, Stephen McDonald st...@jupo.org wrote: The original error stated that the database table for the Geoloc_map model didn't exist in the database, see the relation geoloc_geoloc_map does not exist part, that's the error message. The part you focused on searching for was the SQL query that caused the error, and had nothing to do with it particularly. You say that the migrations were created and run for the new app, and I'm sure you believe that to be - but unfortunately the error says otherwise. Let's try not to talk about these things as magical - we do ourselves a disservice by creating that perception, when the reality is we simply haven't invested enough to time in studying the code and documentation which will eventually reveal how simple and boring these things really are. On Thu, Jul 30, 2015 at 12:00 AM, Déborah Leder debdeb...@gmail.com wrote: I have just done it and it displays the same error page. I have managed to skirt the problem by creating another mezzanine-project, creating another django-app with a new name inside the new project and copying the exact same models.py and admin.py files. I don't understand why this works, but it does... So if you think my problem was due to some hidden bug, I can keep my project and answer your questions to help resolve it, and if not, my problem has magically been resolved. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: zip_import FROM pages_page LEFT OUTER JOIN
OK, but then how do you explain the fact that it worked on my second project ? Whereas I had really run the commands python manage.py makemigration and then python manage.py migrate and both of them had terminated normally. I did nothing more on my second project Le mercredi 29 juillet 2015 16:14:39 UTC+2, Stephen McDonald a écrit : The original error stated that the database table for the Geoloc_map model didn't exist in the database, see the relation geoloc_geoloc_map does not exist part, that's the error message. The part you focused on searching for was the SQL query that caused the error, and had nothing to do with it particularly. You say that the migrations were created and run for the new app, and I'm sure you believe that to be - but unfortunately the error says otherwise. Let's try not to talk about these things as magical - we do ourselves a disservice by creating that perception, when the reality is we simply haven't invested enough to time in studying the code and documentation which will eventually reveal how simple and boring these things really are. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
