trunk behaves strangly when doing manage.py syncdb

[GoogleCodeExporter]

Use the latest version of photologue, (278), and the latest version of
Django from SVN, and when you run syncdb photologue will ask you twice to
set up all the thumbnails etc for admin and viewing.  I kinda expected to
be asked once only...

However syncdb does complete without any errors, but when I then log into
the admin interface there is no sign of photologue.

Original issue reported on code.google.com by rambling...@gmail.com on 5 Aug 2008 at 11:11

[GoogleCodeExporter]

The setup routine first asks to define the "admin_thumbnail" size, which most 
people
are going to want. It then asks to whether you want to set up the default sizes 
need
for the included templates ("thumbnail" and "display"). If you're not going to 
use
the included templates you can just skip that step. This is the reasoning 
behing the
two step process. I was originally 3 steps :). It's a rough implementation 
though and
I'd like to hear what your opinion was of doing it this way, though obviously it
wasn't entirely intuitive.

As far as the admin interface goes, are you calling admin.auto_discover() in 
your
projects urls.py file?

See step 4 if not:
http://code.google.com/p/django-photologue/source/browse/trunk/photologue/README
.txt

Original comment by justin.d...@gmail.com on 5 Aug 2008 at 11:22

[GoogleCodeExporter]

If it really is running the initialization process twice it should identify the 
app
name it's initializing before each run:

Initializing photologue

Is it saying that twice or something else?

Original comment by justin.d...@gmail.com on 5 Aug 2008 at 11:30

[GoogleCodeExporter]

Here is a copy of whats going on from my terminal, should clear up my poor
explanation... :)

$ python manage.py syncdb

Initializing photologue

Photologue requires a specific photo size to display thumbnail previews in the 
Django
admin application.
Would you like to generate this size now? (yes, no):yes

We will now define the "admin_thumbnail" photo size:

Width (in pixels):200
Height (in pixels):200
Crop to fit? (yes, no):no
Pre-cache? (yes, no):yes
Increment count? (yes, no):yes

A "admin_thumbnail" photo size has been created.

Would you like to apply a sample enhancement effect to your admin thumbnails? 
(yes,
no):np

Photologue comes with a set of templates for setting up a complete photo 
gallery.
These templates require you to define both a "thumbnail" and "display" size.
Would you like to define them now? (yes, no):yes

We will now define the "thumbnail" photo size:

Width (in pixels):200
Height (in pixels):200
Crop to fit? (yes, no):no
Pre-cache? (yes, no):yes
Increment count? (yes, no):yes

A "thumbnail" photo size has been created.

We will now define the "display" photo size:

Width (in pixels):600
Height (in pixels):400
Crop to fit? (yes, no):no
Pre-cache? (yes, no):yes
Increment count? (yes, no):yes

A "display" photo size has been created.

Would you like to apply a sample reflection effect to your display images? 
(yes, no):yes

Initializing photologue

Photologue requires a specific photo size to display thumbnail previews in the 
Django
admin application.
Would you like to generate this size now? (yes, no):yes

We will now define the "admin_thumbnail" photo size:

Width (in pixels):200
Height (in pixels):200
Crop to fit? (yes, no):no
Pre-cache? (yes, no):yes
Increment count? (yes, no):yes

A "admin_thumbnail" photo size has been created.

Would you like to apply a sample enhancement effect to your admin thumbnails? 
(yes,
no):no

Photologue comes with a set of templates for setting up a complete photo 
gallery.
These templates require you to define both a "thumbnail" and "display" size.
Would you like to define them now? (yes, no):no
[davidmartin@web41 outc]$

Original comment by rambling...@gmail.com on 6 Aug 2008 at 12:04

[GoogleCodeExporter]

I have added admin.auto_discover to my urls.py file, I am using the admin 
interface
with other apps I have written for my site, so I am fairly confident that is 
working,
I think photologue is having trouble setting itself up properly... I'll check 
what
has been put in the database and let you know.

Original comment by rambling...@gmail.com on 6 Aug 2008 at 12:06

[GoogleCodeExporter]

I updated Django and apparently there was a backwards incompatible refactoring 
of the
signals system. I've updated Photologue to comply with the new changes (r279). I
don't know if this affects your situation or not. I haven't been able to 
recreate the
issue you describe.

What platform are you developing on?

Original comment by justin.d...@gmail.com on 6 Aug 2008 at 8:13

[GoogleCodeExporter]

I am running Linux (shared hosting), python 2.5, mod_python in apache 2.2.

I just updated to the latest version of Django and Photologue and the problem
persists.  I checked my database after the syncdb and it seems to have created 
the
tables, I don't really know why it would be running through all the setup 
options twice.

Original comment by rambling...@gmail.com on 7 Aug 2008 at 6:12

[GoogleCodeExporter]

Are you able to access the photologue admin now or is that still unavailable? 
How
does your shared host deploy Django? Is there any possibility you're sharing a 
python
path with a another instance? Have you tried it locally on the test server?

Original comment by justin.d...@gmail.com on 7 Aug 2008 at 6:31

[GoogleCodeExporter]

Still no access to the admin.  My host deploys django by creating a complete 
install
of apache, python and django in my hoime dir that I have full access to.  I am 
pretty
sure my python path is properly configured, if it wasn't, surely the installer
wouldn't run?

I can't spare too much time to test locally right now, possibly tomorrow am.

Original comment by rambling...@gmail.com on 7 Aug 2008 at 6:45

[GoogleCodeExporter]

I can get photologue working locally just fine, I may yet change hosts for the
deployed app, so this may never be an issue for me.  If I figure out what is 
causing
it then I will let you know.

Original comment by rambling...@gmail.com on 12 Aug 2008 at 7:40

[GoogleCodeExporter]

Just to clean things up I'm going to close this ticket for now. If you continue
having issues please reopen it or submit a new one.

Original comment by justin.d...@gmail.com on 27 Aug 2008 at 1:58

• Changed state: Fixed