Transition extra long after last img of multi-image node...
| Project: | Views Rotator |
| Version: | 6.x-1.0-alpha2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hi,
great module. I enabled it to work so that the module shows images from ONE node, and then I put it on the rest of the pages so that if there is just one image, it will not transition... I might just re-upload two of the same image so that it transitions into itself... unnoticeable except for a touch of speed degredation.
However, lets say I upload 3 images... It gets to #3, and then does not find anymore images. it sits there with a blank area. BUT... after a long wait... it starts back up again. I'm guessing it's browsing in all the nodes for the image files, but shouldn't it be able to refer to the database to know which ones have and have not any image files immediately, in order to build the page? I dunno, it just gets to the end and stops turning for a long while.
Isn't it supposed to go back to the start immediately?
#1
#2
hello? anyone?
#3
This is for anyone who may be having the same problem, I ran across this post looking for the same answer.
Here is what I found:
I could not have multiple File-Images or Text-Fields per Content Type.
Meaning, each Content Type created could only have one field available for the rotator, then it rotated without delay. If I added multiple fields (File-Images, Text-Fields) per one Content Type created, it caused a delay.
I needed 7 different rotors, so for 1 Content Type I added 7 different File-Images fields, and created 7 different Contents from that 1 Content Type, which all caused a delay between the last img and restarting to the first img.
I then had to create 1 Content Type, with 1 File-Image, and each rotor rotated without delays between the last, and first img.
Sorry for no coding, or patching, but this worked for me (troublesome) but it worked.
Hope this helps