In the main directory there is a main page index.html, a page
Travels.htm, and a subdirectory Namibia which contains index_nam.html.
index.html calls Travels.htm (besides other links), and from there is
called index_nam.html.
From index_nam.html I want to get back to Travels.htm by clicking the
button
<a href="../Travels.htm" target="_parent"><img style="border:0;" ...
With Firefox 4.0.1 this reference works but with the Internet Explorer
9 (IE9) not. IE9 is doing nothing when clicking.
> In the main directory there is a main page index.html, a page
> Travels.htm, and a subdirectory Namibia which contains index_nam.html.
> index.html calls Travels.htm (besides other links), and from there is
> called index_nam.html.
> From index_nam.html I want to get back to Travels.htm by clicking the
> button
> <a href="../Travels.htm" target="_parent"><img style="border:0;" ...
Are you using frames? They are generally regarded as an old and bad
idea.
> With Firefox 4.0.1 this reference works but with the Internet Explorer
> 9 (IE9) not. IE9 is doing nothing when clicking.
If you are using frames, you should use the frameset DTD.
Anyhow, none of the this answers your question, but I don't want to
speculate further without a URL I can try out. I.e. post a link to your
site and you'll probably get better answers.
> Udo Huebner<udo.hueb...@t-online.de> writes:
> <snip>
>> In the main directory there is a main page index.html, a page
>> Travels.htm, and a subdirectory Namibia which contains index_nam.html.
>> index.html calls Travels.htm (besides other links), and from there is
>> called index_nam.html.
>> From index_nam.html I want to get back to Travels.htm by clicking the
>> button
>> <a href="../Travels.htm" target="_parent"><img style="border:0;" ...
> Are you using frames? They are generally regarded as an old and bad
> idea.
Hi Ben -
sorry for the delay.
Concerning frames I even are not able answer. My knowledge is limited to
a bit more than a beginner.
The aim is to show photos from a travel through Namibia in the section "Reisen" of my homepage "www.uhuebner.de" where "Namibia" will be one
link.
At the moment I am preparing the respective pages at home with the
program JAlbum and its skin Chamaeleon. Therefrom are the code parts I
mentioned. I will try to understand what frames are and if they are
used in the pages created by JAlbum.
> <snip>
> If you are using frames, you should use the frameset DTD.
Thanks for the hint.
> Anyhow, none of the this answers your question, but I don't want to
> speculate further without a URL I can try out. I.e. post a link to your
> site and you'll probably get better answers.
Well, I will transfer the respective pages to my homepage as fast as
possible and give notice of the result next time.
Thanks again Udo
> In the main directory there is a main page index.html, a page
> Travels.htm, and a subdirectory Namibia which contains index_nam.html.
> index.html calls Travels.htm (besides other links), and from there is
> called index_nam.html.
> From index_nam.html I want to get back to Travels.htm by clicking the
> button
> <a href="../Travels.htm" target="_parent"><img style="border:0;" ...
On the Reisen page you have this:
<span style="text-align:center;font-size:30px;font-weight:bold;"><a
name="Reisen">Reisen</a></span>
>> In the main directory there is a main page index.html, a page
>> Travels.htm, and a subdirectory Namibia which contains index_nam.html.
>> index.html calls Travels.htm (besides other links), and from there is
>> called index_nam.html.
>> From index_nam.html I want to get back to Travels.htm by clicking the
>> button
>> <a href="../Travels.htm" target="_parent"><img style="border:0;" ...
> On the Reisen page you have this:
> <span style="text-align:center;font-size:30px;font-weight:bold;"><a
> name="Reisen">Reisen</a></span>
> Notice that the href="index.htm" part is missing.
Nice, you obviosly looked at my homepage. :-)
The mentioned line indeed contains the part <a name="Reisen"> ... /a>
which is a wrong relic of my former programming and should be taken out!
The program line has to write only the text Reisen in big letters and
reads correctly:
>> In the main directory there is a main page index.html, a page
>> Travels.htm, and a subdirectory Namibia which contains index_nam.html.
>> index.html calls Travels.htm (besides other links), and from there is
>> called index_nam.html.
>> From index_nam.html I want to get back to Travels.htm by clicking the
>> button
>> <a href="../Travels.htm" target="_parent"><img style="border:0;" ...
> On the Reisen page you have this:
> <span style="text-align:center;font-size:30px;font-weight:bold;"><a
> name="Reisen">Reisen</a></span>
> Notice that the href="index.htm" part is missing.
Sorry, I have to add some:
The page Reisen.htm contains links to the different travels. I am
preparing such a travel link for Namibia to be included in Reisen.htm.
At home I am testing this page Namibia.htm if it leads correctly back
to Reisen.htm which does work with Firefox but not with IE9.
I hope I could clarify the problem a bit more.
Regards Udo
> Am 28.01.2012 13:05, schrieb MG:
>> "Udo Huebner"<udo.hueb...@t-online.de> wrote in message
>> news:jfubj4$6e5$1@solani.org...
>>> Hi NG -
>>> I am new here and hope to be wellcome.
>>> In the main directory there is a main page index.html, a page
>>> Travels.htm, and a subdirectory Namibia which contains index_nam.html.
>>> index.html calls Travels.htm (besides other links), and from there is
>>> called index_nam.html.
>>> From index_nam.html I want to get back to Travels.htm by clicking the
>>> button
>>> <a href="../Travels.htm" target="_parent"><img style="border:0;" ...
>> On the Reisen page you have this:
>> <span style="text-align:center;font-size:30px;font-weight:bold;"><a
>> name="Reisen">Reisen</a></span>
>> Notice that the href="index.htm" part is missing.
> Sorry, I have to add some:
> The page Reisen.htm contains links to the different travels.
There are no links to the different travels. For example, there is no link to Ägypten.
> I am
> preparing such a travel link for Namibia to be included in Reisen.htm.
> At home I am testing this page Namibia.htm if it leads correctly back
> to Reisen.htm which does work with Firefox but not with IE9.
> I hope I could clarify the problem a bit more.
I would need to see the Namibia.htm page to see what is wrong.
> "Udo Huebner"<udo.hueb...@t-online.de> wrote in message
> news:jg0rku$q8c$1@solani.org...
>> Am 28.01.2012 13:05, schrieb MG:
>>> "Udo Huebner"<udo.hueb...@t-online.de> wrote in message
>>> news:jfubj4$6e5$1@solani.org...
>>>> Hi NG -
>>>> <snip>
>> Sorry, I have to add some:
>> The page Reisen.htm contains links to the different travels.
> There are no links to the different travels. For example, there is no link
> to Ägypten.
Oh, of course, you are right and meanwhile I am myself confused.
My homepage was started with the hope to insert the pertinent links
to travels with many photos which I have but I didn't do this up to
now. The Namibia page should be the first to be installed.
That is why there are no links in Reisen.htm to Photo pages. :-(
>> I am
>> preparing such a travel link for Namibia to be included in Reisen.htm.
>> At home I am testing this page Namibia.htm if it leads correctly back
>> to Reisen.htm which does work with Firefox but not with IE9.
>> I hope I could clarify the problem a bit more.
> I would need to see the Namibia.htm page to see what is wrong.
> Hi NG -
> ...
> With Firefox 4.0.1 this reference works but with the Internet Explorer
> 9 (IE9) not. IE9 is doing nothing when clicking.
> ...
> I have no explanation and hope to get a hint from the NG.
Hi Ben and MG -
I loaded my files up to my homepage (uhuebner.de) and the problem
disapeared - at least in my homepage. :-O
At home my tests still show the problem that IE9 does not react when
trying to go back to the upper page Reisen.htm.
My other similar photo gallery Kakteen.htm does not show the problem.
It was done with an older version of the chamaeleon skin of JAlbum.
Thus, I have the possibility to compare and probably find out the
reason.
To Ben: Up to now no frames are used in my pages. You recommended not
to use frames. What do you take when only a small part of the page
window shall be changed? Do you let reload the whole page?
> To Ben: Up to now no frames are used in my pages. You recommended not
> to use frames. What do you take when only a small part of the page
> window shall be changed? Do you let reload the whole page?
In article <0.c3d15ba083f40fa7282b.20120129141914GMT.87aa56382l....@bsb.me.uk>, ben.use...@bsb.me.uk says...
> Udo Huebner <udo.hueb...@t-online.de> writes:
> <snip>
> > To Ben: Up to now no frames are used in my pages. You recommended not
> > to use frames. What do you take when only a small part of the page
> > window shall be changed? Do you let reload the whole page?
> Yes.
And if you have 100 pages, you take 100 identicals menus and fixed things.
> If the menu is constant why did you oblige us to reload it when
> viewing every page ... This menu is downloaded 100 times if you look
> at 100 pages.
His sig line didn't explain the rationale clearly enough? 8-)
> The problem is that up to know my knowledge is rather limited. From
> PHP I only know the name but I should learn. ;-)
> Regards Udo
If you don't know PHP there is another way.
Create a page that will be a template for all your pages. This template will have all the html that is common to all pages. Usually header, menu and footer. Maybe some other stuff too. Save this page as template.html. Run this file through the validator to make sure there are no errors.
When you create a new page, make a copy of template.html and add the content for the new page.
The important thing is to use tokens in your template.
For example, enclose your menu in tokens like this:
<!-- START OF MENU -->
....menu html comes here
<!-- END OF MENU -->
If you need to change the menu across all your pages you use a search and replace utility that will find all content between the tokens and replace it with new content. This search and replace utility must be able to work across multiple files.
> > The problem is that up to know my knowledge is rather limited. From
> > PHP I only know the name but I should learn.
> If you don't know PHP there is another way.
> Create a page that will be a template for all your pages. This template will > have all the html that is common to all pages.
...
> If you need to change the menu across all your pages you use a search and > replace utility that will find all content between the tokens and replace it > with new content. This search and replace utility must be able to work > across multiple files.
> Not as neat as PHP, but it works.
A third way is to use Server Side Includes. But the S&R you describe is the least frightening.
>>> The problem is that up to know my knowledge is rather limited. From
>>> PHP I only know the name but I should learn.
>> If you don't know PHP there is another way.
>> Create a page that will be a template for all your pages. This template will
>> have all the html that is common to all pages.
> ...
>> If you need to change the menu across all your pages you use a search and
>> replace utility that will find all content between the tokens and replace it
>> with new content. This search and replace utility must be able to work
>> across multiple files.
>> Not as neat as PHP, but it works.
> A third way is to use Server Side Includes. But the S&R you describe
> is the least frightening.
Thank you both. I should "try" to learn PHP anyway because you emphasize
that PHP is neat! :-)
In article <jg89ma$82...@solani.org>,
Udo Huebner <udo.hueb...@t-online.de> wrote:
...
> >> If you need to change the menu across all your pages you use a search and
> >> replace utility that will find all content between the tokens and replace > >> it
> >> with new content. This search and replace utility must be able to work
> >> across multiple files.
> >> Not as neat as PHP, but it works.
> > A third way is to use Server Side Includes. But the S&R you describe
> > is the least frightening.
> ... I should "try" to learn PHP anyway because you emphasize
> that PHP is neat! :-)
You don't really need to learn much PHP to use its includes functions, you *can* treat it as a magic wand that does certain things if you get certain simple things right. If your server supports php, the wand will work straight off if you name any html files that have includes in them with a .php end, it is the signal for the server to read the programming instructions within and run them. Instead of index.html, you would have index.php.
If you have a footer, that is the same for all pages, put the markup for it in a separate text file and save this file with any ending you like, .inc is popular. Create a new folder and call this whatever you like, "includes" is sensible. Put the folder on your server, just as you might put any folder like "images".
In all your html files (even though they might end in .php) at the point at which you would normally have something like
The above ul markup above goes into the text file footer.inc in the folder called includes.
This is particularly useful when you have a complicated bit of markup, think drop-down menus. Changing the one file in the folder includes ensures all your pages register the change.
What happens is this, the server sees any file that ends in .php and checks it out for php instructions. In the case of the above include, it fetches the content of the text file footer.inc in the folder "includes" and dumps it in the html page at the point where the include statement occurs. When it gets to the visitor's browser it looks like a normal html page with lots of markup, what you see in the View Source.
If all your html files are on the same level as the includes folder, the server will find it and Bob should be your uncle. Me, I use a global reference so that all my includes can be found from wherever, but keep it simple to start off.
dorayme <dora...@optusnet.com.au> writes:
> In article <jg89ma$82...@solani.org>,
> Udo Huebner <udo.hueb...@t-online.de> wrote:
<snip>
>> ... I should "try" to learn PHP anyway because you emphasize
>> that PHP is neat! :-)
<snip>
> In all your html files (even though they might end in .php) at the > point at which you would normally have something like
I'd suggest using '...' rather than "..." when offering "cut-and-paste"
code since there is only one special case with '...' quotes. Windows
users in particular may fall foul of writing "includes\footer.inc" with
unintended effects. Also (minor point) include is not a function but a
control structure, so the brackets are not needed. The ; is also
optional at the end of PHP section, so the simplest include looks like
this:
<?php include 'includes/footer.inc' ?>
I think it helps to make it all seem slightly less magical.
> > In article <jg89ma$82...@solani.org>,
> > Udo Huebner <udo.hueb...@t-online.de> wrote:
> <snip>
> >> ... I should "try" to learn PHP anyway because you emphasize
> >> that PHP is neat! :-)
> <snip>
> > In all your html files (even though they might end in .php) at the > > point at which you would normally have something like
> I'd suggest using '...' rather than "..." when offering "cut-and-paste"
> code
I was not offering cut and paste code. I was pretending to be human and assuming that another human reading me would understand that where I had "..." they would have text, simple as that. But what do I know, your knowledge of these things is likely greater as you are likely a real human unlike my cheating self.
> ... the brackets are not needed. The ; is also
> optional at the end of PHP section, so the simplest include looks like
> this:
> <?php include 'includes/footer.inc' ?>
True. I was looking for a simple something in a url to refer OP to but gave up and wrote a cheating mini one for him but not before lazily cutting and pasting the above from an example in some page that was not too unreasonable.
> I think it helps to make it all seem slightly less magical.
Depends on your understanding of magic. Perhaps the pretty and extravagant
<?php include (((((("includes/footer.inc"))))));;;;;;;;;; ?>
would more magical. Perhaps in the world of magic, Ockham's Blooming rather Ockham's Razor operates.
Perhaps, humans do not grok magic well in spite of all their religious efforts.