Closed (fixed)
Project:
Views Nivo Slider
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Anonymous (not verified)
Created:
8 May 2010 at 11:17 UTC
Updated:
26 Oct 2018 at 04:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedLink above didn't quite work:
Link appears as below:
http://192.168.0.251/fcontent/<a href="/fcontent/node/1">view</a>Comment #2
pedrofaria commentedHello mcdazz,
When i start the project i did not figure out Node: Link fields must be used... just Link fields... ok... i made a patch for you... test and send me a feedback (positive or negative)...
Cya
Comment #3
Anonymous (not verified) commentedHi Pedro,
Thanks very much for that - it works beautifully.
I guess I should have paid more attention to the "How to use" section on the Views Nivo Slider module page (where it clearly states "Link field") - I guess I missed it in my excitement.
Thanks again for the patch - it's much appreciated. :-)
Cheers,
Dazz
Comment #4
Anonymous (not verified) commentedClosed with much thanks to Pedro.
Comment #5
pedrofaria commentedadded to cvs!
Comment #6
gillesbailleuxHi Pedro,
The 6.x-1.x-dev (21st May) has obviously solved the link problem. Thank you!
Gilles
Comment #7
jasondecamp commentedI am having issues with the links as well. As a simple test I set the link location to be and I get the following:
"http://localhost/base_url//base_url/"
This double appearance of the base_url and the extra "/" occurs no matter what the link url is set to be.
Views Basic settings:
Style: Views Nivo Slider
Row style: Views Nivo Slider
Views Fields are set as follows:
Note: Title
Content: Image Image
Content: Link, Link as URL
Row style: Views Nivo Slider is configured as follows:
Image field: Content: Image (field_image)
Title field:
Content: Link (field_link)
Thanks,
Jason
Comment #8
Anonymous (not verified) commentedI've had a look into the issue you've raised, and I've been able to replicate the issue (links appearing as "http://localhost/base_url//base_url/").
I'm guessing on the actual node(s) itself, you've entered into the link field a link like "node/1"?
If you enter the full link - ie "http://localhost/node/1", the link appears correctly and works.
I don't think it's the ideal way to work - it would be interesting to see what others do.
Cheers,
Darren
Comment #9
jasondecamp commentedYes, I am trying to link the node using relative paths since I am working on a local version before uploading to the live site. I would rather not have to go back and redo all of the links once it is moved to the final destination.
Thanks,
Jason
Also, it stripped the tag out of my first post... what it should have said is:
"As a simple test I used
<front>"Comment #10
Anonymous (not verified) commentedIt would definitely make things easier in the long run - you could of course go for a slightly different approach and use the link to node option instead of using a Link field. It wouldn't work with something like
<front>though.Comment #11
jasondecamp commentedThe problem with link to node is that I am not linking to the node used the the view... it is linking to a related page. In order to link to the node I would need to restructure my article completely so that the parts used in the slider are hidden attributes to the main article.
So I guess my question is, is this a bug, or am I missing the intent of this link function?
Thanks,
Jason
Comment #12
Anonymous (not verified) commentedAhh yes, I can see your point. I don't think it's so much a bug as a limitation in the way the link Views Nivo Slider currently works.
What you've outlined above actually makes a lot of sense - I'm sure that Pedro (or someone else) will make some changes and get it working.
Comment #13
klonos+1 here too.
We definitely need to be more flexible with paths/URLs. Mostly for cases when there's a test installation that is to be moved at a later point to a different server.
Comment #14
pedrofaria commentedHello guys...
I was trying to reproduce the @jasondecamp report and found the bug...
The problems at Link field, is that Link field generate a URL and i am forcing a regeneration of this URL and URL crash!
i am studying a best way to fix this issue...
i will report when i have some progress...
cya
Comment #15
pedrofaria commentedI made this patch... please, test and send me a feedback.
Comment #16
klonoswell... I don't have a test environment set up atm, but I think that jasondecamp can check if adding a relative path works.
@jasondecamp: ping?
Comment #17
jasondecamp commentedCan you explain how to apply that patch? I will test it as soon as I know how.
Thanks,
Jason
Comment #18
jasondecamp commentedOk, I think I figured it out... I just went through "views_nivo_slider.module" and replaced all of the lines marked with a "-" with the line noted with a "+".
The patch fixes my problems locally. Works with , local paths, and absolute urls. I tried it with: "Content: Link, URL as link" and "Content: Link, URL as plain text." Both work.
Thanks for your fix pedrofaria
-Jason
Comment #19
jasondecamp commentedShould say "works with
<front>, local paths, and absolute urls"Comment #20
pedrofaria commentedThanks for your reporte and time spent on it...
For apply patch, read this page with all explanations.
http://drupal.org/patch/apply
I will commit it on CVS and release a new version soon...
Pedro Faria
Comment #21
pedrofaria commentedcommited
Comment #23
Oleiade commentedHi, I'm sorry I reopen this, but i'm having the exact same issue that the guy who opened this thread and i'm using the last 6.x-2.x-dev version.
Whatever I put in my Link field, my slideshow elements redirect to a strange http://[my_base_url]/"a href="/index.php/?q=node/2" /a".
Have to admit I'm a bit disapointed with this.
Any idea of how to fix it please?
Comment #24
mpflaging commentedMe too. I'm using 6.x-2.11, which I think includes the two patches Pedro put in this thread?
Wonder if there's a conflict with some other module, Pathologic maybe? I've had the problem since I first set up the slideshow. Now it has become a show-stopper.
Comment #25
mpflaging commentedI fixed this (in my case) by playing around with the View. "Content: Link Title, as link (default)" is what worked for me.
Full instructions: It's in the "Fields" section of the View, banner_slider. Click the "Content: Link" item, and at the bottom of the "Configure field" section, there's a "Format" dropdown. I set it to "Title, as link (default)" and the problem went away. (It was previously set to "URL, as link" which is in the tutorial or something.)
Comment #26
bryancasler commentedI'm re-opening this and moving up the version.
@mpflaging: On 7.x-2.x-dev no matter what format you choose for the link, everything will break if a link is included. The only solution right now it to leave the link option blank http://awesomescreenshot.com/01eor8910.
Comment #27
ckngUse "Content: Link", not URL
@animelion,
Could not reproduce the link problem in D7
Comment #28
bryancasler commentedThis was resolved over here http://drupal.org/node/1121072#comment-5294156
Comment #29
ovunc commentedhi there.. i am very beginner for drupal and php codes. i just wanted to have a nice slider which can show page groups in web site. i have finally found and decided to use views nivo slider. its wonderful looking very smooth slider. among all others i can say it is the most useful for me.
i created nodes with original size of images
slider is working well on my main page
however i have this problem (might be so easy to solve but i couldnt manage):
when i click on image or node name on slider it takes me to nodes which hold the images with full(!) size. in those nodes before image there is "image:" title and below image there is "link:" title. if i add a link to node while i create it this link appears next to this title. it looks very unpleasant.
all i need is redirect this clicks to related pages which include resized images and text information.
thank you all
Comment #30
ckng@ovunc, please open a new issue, do not reopen closed issue unless it is exactly the same issue.
Since you are new, please read up on how to report an issue.
Sometimes screenshot can explain better than words.
Comment #31
ovunc commentedthank you very much for your care. actually i saw couple of issue reports like mine but since 2011 nobody answered. and i thought that some people can answer under a title which seems related and at least includes some comments.
forgive me for my ignorance. many thanks