Right, I might be doing something wrong here, but I suspect it is a bug.

I have created a two new content types from scratch, for simplicity sake we'll call them Image_1 and Gallery_1

After I have created the gallery relationship, I upload the images to the gallery (by clicking the "upload images" link inside the Gallery).

The images upload fine and I can see them in the uploaded directory on the server.

When I view the Gallery List, The Gallery Cover image displays fine.

When I visit the Gallery, The Image Thumbnails images display fine.

When I click on one of the thumbnails, the Image Preview does not display.

May I assure you that I do have permissions set up correctly.

I am also logged in as administrator.

Further.

Using the above settings exactly as they are, I make only one change, I visit the Node Gallery Settings page, I click on the link for edit.

Home › Administer › Site configuration › Node Gallery
Node Gallery Config Edit

Here I only change the Image Type node type to the one originally created by the Image module.

I save the relationship making no further changes.

I now upload images, the images display fine even on the Image Preview.

So this leads me to conclude there is either something I should be doing when I create the node type for images which I am not doing, or there is something wrong with the module.

One other thing that I can't understand is that when I later install the Lightbox module, the Image Preview displays fine in Lightbox, but still not on the Image Preview node page.

I don't know if this is relevant but I am using CCk 6.x-2.5 and Views 6.x-2.6

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dbeall’s picture

something funny going on..

I did this test on wamp-xp with the dev version that has all the patches available.
I have run a test (create 2 new content types and add a new relationship) and it all works as expected..
The only settings i made in the new relationship was (choosing the new content types) and check marking the fields(title and body).

I did a second test on wamp-xp with the alpha10 version to see if any difference is found..(same test)
I have run a test (create 2 new content types and add a new relationship) and it all works as expected..
The only settings i made in the new relationship was (choosing the new content types) and check marking the fields(title and body).

I wish I could say I found something, but it seems to work as expected..

Now I am wondering what could be wrong... hmmm
Is there any content access modules installed..
I am heading into the shop to work on a boat cover, and will be hashing this out in my little tiny brain.....

EDIT: I was using a core theme.. what is it , garland

Manamarak’s picture

1) I am using XAMPP
2)I have tested with a core theme
3) I have Node Gallery Access, ACL, Forum Access and Content Access installed and activated.

I will try it on a clean drupal install with no other modules and report back.

dbeall’s picture

I would try taking out node_gallery_access and try it again.
There are known issues with node_gallery_access not playing nicely with other access modules..

Manamarak’s picture

I have disabled Node Gallery Access and still get the same results.

I don't think this is a permissions issue and here's why:

1) The problem occurs for the Admin user, who by definition should have all permissions.

2) When clicking on the link, the node doesn't display the Access Denied message.

3) The image's title displays and the comment link displays.

Basically, the only part of the node which is not displaying is the body. Neither the Body text nor Image.

Manamarak’s picture

Right,I've just switched to the Dev version and now it's working.

I'm not sure why though.

Tell me Dbeall, when you switched to Alpha 10, did you first deactivate Dev, then uninstall it, then deleted the folder in your modules directory before copying Alpha 10 in?

If not, that could have caused the discrepancy between my findings and yours. It may, for instance, if you have replaced the directory without deleting it first, have left one of the original files in tact.

Dev works for me now, but I'd be interested to know how it happened.

dbeall’s picture

I always delete the module folder before any upgrade, (best practice) as to not leave any old files that may not be overwritten... because the new module folder may not have all the files the original one did, which means some old files could possibly remain.

I did a complete uninstall and deleted all the folders in the sites/all/default file system.. because node_gallery uninstall doesn't remove things the way it should.

Actually, it may have some other database remnants left behind after uninstall too, but i never have looked into that...
When i have more time, i dump the whole database and do a new Drupal install, just to be clean.
Right now I have 11 Drupal installs in my wamp folder, well, 3 of them are D7(testing different modules)

dbeall’s picture

BTW, You might want to try out my text upgrade files with your install:
http://drupal.org/node/601738 ; use the full text ones in comment #3
There are copies of the full files, select all, copy and paste into a file, name it and run it. Does not require uninstall since they are not database changes.

dddave’s picture

I did not read this issue completly and only chime in to rule out something very basic:

Are the "View field xy" perms correctly defined?
Have you checked the field settings for the content type?

This looks like some field visibility issue to me.

Manamarak’s picture

Category: bug » support

I have a sneaky suspicion that this was my fault. I'll make sure this weekend and report back.

kmonty’s picture

Status: Active » Fixed

Author reports this as being fixed, although I'll be interested to hear what the problem/solution ultimately was.

Manamarak’s picture

Could this have been caused by the fact that I did not check the 'body' field when I created the user relationship?

I did later check this field, but didn't do so at the time of creating the relationship.

To be honest, I don't know what the problem was, I just assumed that it was because the body field was not checked.

My understanding of the checking the body field in the user relationship was that it will allow the user to add body text to the uploaded image.

All I know is that once I installed the dev version, all my problems went away.

I will do some tests to confirm whether it was caused by me not checking the body field or because it was due to some other clash with another module, perhaps even the Node Gallery Access module which I had turned on, and which I was warned not to use.

As soon as I have time I will report back, but at present I'm very busy with a new job.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.