Closed (fixed)
Project:
Lightbox2
Version:
5.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Sep 2008 at 22:16 UTC
Updated:
8 Jan 2009 at 13:51 UTC
Environment: Drupal installed in subdirectory. Will update later, installed as root.
Using
"node/xx"
as a setting for except or only does not take effect.
Also a new line with a space will match the front page.
In contrast, block settings, with the same values work as expected.
I don't believe it should have anything to do with basepath. I also used *node/xx* and it still failed.
It failed when viewing the page as a clean url and also as its node/xx alias.
Comments
Comment #1
stella commentedI've fixed the issue where a new line with a space will match the front page. The fix for this issue will be included in the next dev release, available later today.
The other issue isn't a real bug in my mind. If you're viewing node with id 123 which also has an alias content/foo, then in the disabled url list, you need to enter both "node/123" and "content/foo". If you're using a multilingual site you need to enter "*/node/123", etc in order to match the language code at the beginning (e.g. en in en/node/123).
Cheers,
Stella
Comment #2
sgriffin commentedWell in the block usages of node/xxx
it will lookup the path as well, and use it for visibility settings. Or just lookup the node id of the node, That way you don't waste time by having to do the path and the node both.
If you put the node/xx, you will also want to match the path. And if you put the path, you will want to match the node.
This is just the way, the other core visibility settings work.
The bug was... If you have the drupal site installed as a subdirectory, node/xxx or *node/xx does not work in any case.
I have made the site live now, and node/xx works, but perhaps, some live sites are normally installed as domain.com/drupalsite/
Comment #3
stella commentedI won't be doing much additional work on the Drupal 5 version of lightbox2, now that Drupal 6 has been out for a good few months now. Also this problem shouldn't exist in the Drupal 6 branch.
Cheers,
Stella
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
stella commentedReleased in Lightbox2 5.x-2.9.
Cheers,
Stella