Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When I first create an album inside another existing album, the link that is created on the parent album is incorrect: instead of taking me to /node/xxx it takes me to /node/node/xxx.
The problem seems to go away entirely after I put at least one photo inside the album. Weird!
I'm using the latest acidfree.module 4.6 version (1.2.2.23).
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | ie_fix.patch | 672 bytes | vhmauery |
Comments
Comment #1
vhmauery commentedI cannot reproduce this. Can you give me more specifics so I can? I created a new album in my root album called test. The root album already had some other items in it. When I clicked on test, it went to the right place. I created an album inside test called inside. When I returned to the test album, I clicked on inside and it went to the right place.
I am using 1.2.2.25 (but the changes between that and 1.2.2.23 were fixes for the description field in album contents bug and is really a one-liner that would not fix this problem.)
Comment #2
ricmadeira commentedWeird... I'll try to reproduce this on my other site later, using the new CVS version. But if you wanna have a look, just go to these links and click on the empty albums:
http://rpg.turnodanoite.com/node/563
http://rpg.turnodanoite.com/node/581
Oh, and I just noticed, this also happens with empty albuns in the root:
http://rpg.turnodanoite.com/node/562
Comment #3
vhmauery commentedHmmm. This not good. I clicked on the empty albums on your site and it worked fine for me. I wasn't logged in, but I couldn't reproduce it on my site when I was logged in. I am really confused about this. Clicking on the folder is actually a javascript thing. The folder is a background image in a div with the pointer set to be a hand. It also has the onclick event set to do a 'document.location="node/nnnn";' This makes me wonder if there is something else going on here. Can you view the source to see what location it thinks it wants to go to and post that?
Comment #4
ricmadeira commentedJavascript, huh? Well, guess what?, the problem only happens when you use Internet Explorer. I tried it on several different computers at work, and they all took me to /node/node/xxx instead of node/xxx.
Now I'm home, I just fired up Firefox and everything works just fine. Even the first page node preview for the album looks different, with folder aligned to the top right of the description text. In IE, the folder just appears centered on few blank lines, and then the description text starts. Would be cool to have everything working on IE too, though.
Sorry, I didn't get this part: "Can you view the source to see what location it thinks it wants to go to and post that?"
Comment #5
vhmauery commentedI was going to ask what the source code looked like from IE, as if it were mangled or something, but I figured that was a stupid idea. The source is the same either location. The problem is that IE thinks the clean urls are really directories and is appending node/xxxx on top of the last upper level directory, i.e., node/. So we just need to specify an absolute url for IE (or for all browsers since it shouldn't be a problem to be more specific)
Try out this patch and let me know if it fixes the problem.
Comment #6
vhmauery commentedClosing the bug. The fix is in cvs and the tarball.
Comment #7
vhmauery commented