Double selector and double page position : trouble shoothing in adding channel to image content-type.
Wed, 06/01/2010 - 08:37
Reference:http://www.prosepoint.org/node/526
Hi!
I did try some of the above.
I set the Channel to be an obligatoiry vocabulary for the images content-type in edit/vocabulary/2. The channel selector does not appear in the page node/add/ifimage.
So I add a field_channel to the images content-type. Then the selector appear on the add page. But, when importing images with imagefield_import, I discover two sets of channel selector, one in the vocabulary section and the other above, probably the field_channel? After the import, there are doublons as well in the gallery, i.e. the field_channel appears at the bottom of the node and in the vocabulary at the top right, in the "in channel-x channel-y etc." section. I would prefer the vocabulary position for uniformity across nodes, but I don't see the channel selector when adding image one by one. My users will not be able to select it, they will only see the field_channel selector.
Suggestions?
I did add as well a vocabulary selector and a date filter to the image_selector view. Works well. But in the image_gallery view the channel selector is out of the gallery selector presentation.
I can post the modified view images_list here for nascimbeni if he wants to follow the same steps.
Thx.
Sat, 09/01/2010 - 22:07
#2
Question
Hi!
If the channel had been added to the ifimfage type before those upgrades .23 -> .25 -> .28 -> .29 ?
Thx.
Tue, 12/01/2010 - 12:05
#3
Questions
Hi,
I'd like to address your original post because that is the right idea. I think addressing your comments #1 and #2 is leading down to an eventual dead end anyway.
> I set the Channel to be an obligatoiry vocabulary for the images content-type in edit/vocabulary/2.
Sounds good. This is one way to do it. (Let's call this method A)
> The channel selector does not appear in the page node/add/ifimage.
This is where my observations differ. On the latest ProsePoint development code, I tried this and I do see the channel selector appearing on .../node/add/ifimage. Are you getting the url .../node/add/ifimage confused with the image insertion popup window?
> So I add a field_channel to the images content-type.
Then I undid my first change, and tried it this second way you mentioned (Let's call this method B). Seems to work.
> the field_channel appears at the bottom of the node and in the vocabulary at the top right,
I think this is purely a presentation issue and can be fixed through themeing.
> I don't see the channel selector when adding image one by one.
You mean the image insertion popup window? I possibly need to add some code in there to make things work. Have to look in there before I can say anything definite.
Overall, you're on the right track. My opinion at the moment is that method B is the better way to go. However, before I jump into this problem deeply, I just wanted to first make sure we're both talking about the same things.
Also, what version of ProsePoint are you using?
Wed, 13/01/2010 - 11:16
#4
I'm using Pp 0.29
Hi!
> Are you getting the url .../node/add/ifimage confused with the image insertion popup window?
No. The selector does not appear on /node/add/ifimage but do appear on the popup pp_ed/insert/ifimage/browse. I tryed it on an old version Pp 0.14 already installed somewhere where it works. That's why I say there is trouble with my installation of Pp 0.29 and it is confirmed by you saying that it works on your most recent Pp. See comment #2.
I undid the obligatory vocab for ifimage. The field_channel appears on add/ifimage, on the popup (no coding needed for you here), the gallery and the import.
> can be fixed through themeing
Yep.
Would you privilege this method for the media content-type as well? And why method B over A?
If I modify the image_list and ifimage/media content-type (adding field_channel and maybe a field node_reference for a gallery type) will there be trouble in upgrading?
Thx.
Wed, 13/01/2010 - 12:21
#5
...
> The selector does not appear on /node/add/ifimage but do appear on the popup pp_ed/insert/ifimage/browse.
(Small correction: The popup window has several stages, and the relevant stage has the url .../pp_ed/insert/ifimage/upload, but this doesn't change the facts of the matter).
> That's why I say there is trouble with my installation of Pp 0.29
Well, actually, I was working off the development codebase (instead of working off a released version). However, at time of writing, there have been no further changes to the code since the release of ProsePoint 0.29, so the two are almost identical (The development codebase has a few extra debugging things).
Looking through the release notes, there have not been any major changes to the implementation of channels from 0.14 to 0.29. In any case, I think chasing this issue from the starting point of 0.14 is the long way to address this.
> > can be fixed through themeing
I can help you with the themeing once the functional aspects are satisfactory.
> Would you privilege this method for the media content-type as well?
Not quite sure what you mean by this, but if you mean whether the same can or will be done for the media content type, then, most likely yes.
> And why method B over A?
Method A is adding another vocabulary to the image content type. All Views and other configuration is done through the (core) taxonomy module.
Method B is adding a CCK field (from the content_taxonomy module) which has the same allowed values as a taxonomy vocabulary. All Views and other configuration is done through CCK related configuration or operations.
It's a small difference that isn't important for most use cases, except for one (that I can think of). If using method A, then the taxonomy listing pages like .../taxonomy/term/N will list stories and image nodes. If using method B, then the taxonomy listing pages will not list image nodes. My opinion is that the latter is more suitable, hence I'm tending more towards method B. Your opinion may differ, which is fair enough.
Another question I have ... this path we're discussing will result in two separate vocabularies for image nodes ie. Image Gallery and Channel. Didn't you originally want a single vocabulary (which is a 'merge' of the two)?
> If I modify the image_list and ifimage/media content-type ... will there be trouble in upgrading?
If you add new CCK fields, that will be okay. ProsePoint doesn't know about the fields you add, so it won't touch them.
If you modify existing fields, it should mostly also be okay, because ProsePoint is careful to only change the minimum during upgrades. However, there will be a small probability of a configuration clash if we choose to configure things differently. I cannot guarantee such a clash will not happen, but the chances will be (I expect) very very small. If such a clash does occur, you can always reconfigure your changes again after the upgrade - it shouldn't lead to any sort of non-recoverable error.
Tue, 19/01/2010 - 04:32
#6
Method B
>Method B is adding a CCK field
I implemented Method B and did go further. I added a node_reference to ifimage for an image gallery content-type, built views around it and added lightbox2. See http://www.lullabot.com/articles/photo-galleries-views-attach.
> I can help you with the themeing once the functional aspects are satisfactory.
I do have a problem with the latest image view that does not float to the left of the teaser content in the context of a attached view to a gallery teaser.
Part of the results from the Pp node template:
<div class="node-inner">
<h2 class="title"> <-- title link --> </h2>
<div class="submitted"> <-- submitted --> </div>
<div class="content">
<-- the body of the node -->
<div class="view-display-id-node_content_2">
<-- the latest image for the gallery and it's wrappers -->
</div>
</div>
</div>
The CSS : div.view-display-id-node_content_2 { float: left; }
The div should go to the left of the <--- The body of the node -->?? It does float left ( or right if setted to it) but always under the <--- The body of the node -->.
So, I added a wrapper via a galley template: <div class="gallery-wrapper"> <-- the body of the node --> </div> and div.gallery-wrapper { float: right; }. Now the image float left and the body right... but only for the first gallery teaser(view-display-id-node_content_2 is present on all teasers)! And the small line separating teasers is now on top of image + body below title and submitted. What am I missing?
>Didn't you originally want a single vocabulary (which is a 'merge' of the two)?
No. The channel vocabulary sets things like regions and organisations (I found this wonderful module to help select channels http://drupal.org/project/hierarchical_select), the gallery vocab sets a subject (e.g.: is it a logo, etc.).
> [upgrading] shouldn't lead to any sort of non-recoverable error.
I hope so! :)
Thx.
Tue, 19/01/2010 - 16:53
#7
...
Hmmm... okay, this issue has transformed into something else ... but if you're satisfied, then I am too.
> The div should go to the left of The body of the node?? It does float left ( or right if setted to it) but always under The body of the node.
It's always a bit tricky debugging CSS with floats without having it in front of me, and I'll be taking a guess at what you mean.
If 'the gallery and its wrappers' (call this G) occurs in the html after the 'body of the node' (call this B), then G will display in the browser after B, regardless of whether G is floated or not. This is normal CSS behaviour. What you want is to float B, or move G to occur before B.
Wed, 20/01/2010 - 07:32
#8
Thx.
Thx.
Hi!
I did look everywhere to find the problem (I learn a lot about drupal coding along the way), why am I missing the channel in the ifimage type??
Then I remembered, I got a old clean Pp 0.14 Install forgotten on another server. When I add the channel to ifimage content-type on that site, everything is good. There is a corruption somewhere in the database on the other installation!? Hgh! In french I would say "Bordel de merde" and in the quebec version I would add a lot of "@#$%#%". How did it happen? Now I feel stupid :) What are the manipulations I did to get there...
I did upgrade from .23 -> .25 -> .28 -> .29, Anything here could trigger this?
Any idea on how to repair whitout loosing content, etc.?
Thx.