I don't us the SWadress option because i like the clean look when there is just the url (eg. www.mydomain.com) in the adress bar. But i'm using a textpage as a startingpage where i also mention the updates in the gallery. Now i want to link that to a certain folder. I found the way to do that in your example package of textpages but when i use the link(eg. a href="#/content/Earth Animals/">a specific page</a>) the full location will display in the address bar. like : www.mydomain.com/content/Earth Animals/. And that is something that i don't want!! And for the rest of the "visit" it stays like :
www.mydomain.com/content/Earth Animals/. It doesn't change??!!!
Is there something i can do about that? I hope you can help me.
X3Photo Gallery Forums
X3 Photo Gallery Support Forums
-
-
MorningWood
Experienced
- Posts: 60
- Joined:
Yes, the link worked fine. I just tried it again and works like a charm.
Example : added video to my page and mentioned that on the textpage that i start with.
Link used :<a href="#/content/Video/">video</a><br/> This will give people the option to click on video and go directly to the video folder.
But when they from there on surf the site the url in the address bar wil show :
www.mydomain.com/#/content/Video/. It does not change at all. Probably because i haven't checked the option useswfaddress in the config menu.
Obviously i just want the url to stay like www.mydomain.com.
If you want a link to my page i will pm it to you.
Example : added video to my page and mentioned that on the textpage that i start with.
Link used :<a href="#/content/Video/">video</a><br/> This will give people the option to click on video and go directly to the video folder.
But when they from there on surf the site the url in the address bar wil show :
www.mydomain.com/#/content/Video/. It does not change at all. Probably because i haven't checked the option useswfaddress in the config menu.
Obviously i just want the url to stay like www.mydomain.com.
If you want a link to my page i will pm it to you.
One thing though ... If I fix the SWFaddress to be fully disabled like you suggest, you won't be able do what you explained in your original post.
The reason for your link (ex. <a href="#/content/Earth Animals/">a specific page</a>) would work, is because of the SWFAddress. As I said in my first post, you can't have one without the other ...
If you want to use #/links/, they will show up on the URL field of your browser(That's how it works) ... Disabling the swfaddress completely will not allow you to do internal linking, and then the point of having the link in the first place is lost.
The reason for your link (ex. <a href="#/content/Earth Animals/">a specific page</a>) would work, is because of the SWFAddress. As I said in my first post, you can't have one without the other ...
If you want to use #/links/, they will show up on the URL field of your browser(That's how it works) ... Disabling the swfaddress completely will not allow you to do internal linking, and then the point of having the link in the first place is lost.
-
-
MorningWood
Experienced
- Posts: 60
- Joined:
-
-
gadgetologist
Experienced
- Posts: 123
- Joined:
useswfaddress : Does it restrict internal link usage?
When I first read this I thought I understood it to mean that the setting for useswfaddress has no effect on (does not restrict usage of) the internal links. So, I went and used them and it and now have seen problems. I've read this again and it still seems like Karl is saying that it has no affect. Either I'm misunderstanding this or something has changed intentionally (spec change) or unintentionally (bug)?
Would someone please clear this up for me? If it is true that internal links are a casualty of a setting on useswfaddress, then perhaps an explicit mention somewhere (perhaps the settings comments area) would be appreciated. If I missed it, sorry, just point me there and forgive me, but I did look.
Thanks.
Would someone please clear this up for me? If it is true that internal links are a casualty of a setting on useswfaddress, then perhaps an explicit mention somewhere (perhaps the settings comments area) would be appreciated. If I missed it, sorry, just point me there and forgive me, but I did look.
Thanks.
-
-
gadgetologist
Experienced
- Posts: 123
- Joined:
Okay, I called it "internal links" you called it "internal linking"... but thanks for the clarification.mjau-mjau wrote:One thing though ... If I fix the SWFaddress to be fully disabled like you suggest, you won't be able do what you explained in your original post.
The reason for your link (ex. <a href="#/content/Earth Animals/">a specific page</a>) would work, is because of the SWFAddress. As I said in my first post, you can't have one without the other ...
If you want to use #/links/, they will show up on the URL field of your browser(That's how it works) ... Disabling the swfaddress completely will not allow you to do internal linking, and then the point of having the link in the first place is lost.
And may I ask what about the last part of that question regarding suggesting an explicit note/warning to highlight this fact?
Yes. This should probably be added to docs somewhere, although Im not sure everyone will find it since it related to textpages, descriptions, titles and basically anything that can contain a textlink. ANY textlink using html <a> href tag targets the browser URL, and must use the swfaddress method to target internal linking.gadgetologist wrote:And may I ask what about the last part of that question regarding suggesting an explicit note/warning to highlight this fact?