Using rotor images for other views
scalp - April 19, 2009 - 16:14
| Project: | Rotor Banner |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | mrfelton |
| Status: | closed |
Jump to:
Description
Is there a way to use the images uploaded as rotor images in other views? I've looked at the rotor view and it seems configurable to the point that I could use images uploaded via other methods in there so I guess this isn't essential, but I was curious as to whether or not it was possible.
#1
I have added this feature to CVS. Please check out the latest code and report back. You should now be able to find the field in the Views UI, in the Fields section, under 'Rotor: Rotor image'.
#2
bumping version to 6.x-2.x-dev
#3
It works. It doesn't work with imagecache though? I'm guessing this is because the image upload in the content type rotor isn't a CCK field, but is there any way to integrate with imagecache using the default rotor image upload field?
#4
Rotor2 actually has ImagageCache support when using the Rotor Row style (as opposed to Node or Fields)- but I guess you know that already. I'll have a look add making the standalone Rotor Image field available to ImageCache too...
#5
That would be great. I'm trying to put together a small, simple site for an artist. That way I could just show her where to upload rotor images and have it populate a gallery through views also. It could obviously be done the other way around, but it may be a nice feature for Rotor. Great module though! Very easy to use.
#6
latest code in CVS has ImageCache support on the rotor_image views field.
#7
If you saw my post from five minutes ago, please disregard. I'm an idiot!
I've got it in views. Works nicely. I don't know how far out you want to build this, but I'll let you know my thoughts. If I could get all the same functionality of an imagefield in views that would be great. Like an option to link the image to its node and lightbox compatibility. Like I said, I know that this may not have been what the module was intended for so it really comes down to what you want it to be used for.
#8
Well... you know, there is nothing that says you need to use the Rotor Item content at all... Why not just create a new content type with whatever fields you like (including imagefields), create a view out of them, and set it's display style to Rotor. I haven't tested that fully... but I don't see any reason why it wouldn't work.
#9
That's the route I went and it works great! Like I said, it is definitely not essential to Rotor Banner because the other functionality is available through CCK, imagefield, and imagecache. The only reason it could be needed is if someone didn't want to use those and soley wanted to use Rotor Banner for whatever reason. In conclusion I think it is an awesome module, very easy to use with beautiful results.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.