-
I just killed an almost finished client site
Hi,
I need your collective help .... again.
The problem:
The navigation is AllWebMenus and does what it needs to do in FF,
Chrome, Safari and as of 4am today it wont do what it's meant to in IE.
And yes it has been working perfectly up until the last upload. No
changes to AWM files however.
There were many site wide changes yesterday including the introduction
of some .js to pull in a glossary.txt file when hovering over words.
Other than that no changes to anything that I can see would cause this.
On a couple of pages I have moved the two script calls (jquery.js and
glossary.js) from the page head to the body but that made no difference.
The site can be seen at:-
http://www.test.adendum.co.uk/client2/html/home.html
and the home page looks the same in all browsers - even IE - but try
navigating and see what happens.
It's gonna be obvious I just know it!
Paul.
PS. Generator is actually NOF 11 even though the tags say 10.
-
Re: I just killed an almost finished client site
Do you have one two row AWM menu called menu.js? Or two one row menus with
the same name?
I see two sets of identical linking code after the <body> tag, both
referring to a menu.js file, but only one piece of code relative to an
element down in the page.
And on all but the home page, there's some awm code erroneously embedded in
the search form in the upper right corner of the pages.
Bad upload of the site?
In the menu.js file, you're using relative links rather than full URLs. IE
isn't handling this well on pages other than the home page, dropping the
"client2" folder from the URL when you try to navigate from a non-home page.
Use full URLs when publishing by asset type so you can use the same menu on
all pages.
Also, don't leave menus with the default filename of menu.js. Give each menu
a unique name. If you place multiple menus on a page with the same name,
it'll break.
--
Chuck Joslin
BeyondFusion.com - Your Fusion Community
www.beyondfusion.com
Register domain names at www.awavedomains.com
"Adendum" <Adendum@hotmail.co.uk> wrote in message
news:hntck7$qkp$1@DailyPlanet.news.netobjects.com. ..
> Hi,
>
> I need your collective help .... again.
>
> The problem:
> The navigation is AllWebMenus and does what it needs to do in FF, Chrome,
> Safari and as of 4am today it wont do what it's meant to in IE. And yes it
> has been working perfectly up until the last upload. No changes to AWM
> files however.
>
> There were many site wide changes yesterday including the introduction of
> some .js to pull in a glossary.txt file when hovering over words. Other
> than that no changes to anything that I can see would cause this.
>
> On a couple of pages I have moved the two script calls (jquery.js and
> glossary.js) from the page head to the body but that made no difference.
>
> The site can be seen at:-
>
> http://www.test.adendum.co.uk/client2/html/home.html
>
> and the home page looks the same in all browsers - even IE - but try
> navigating and see what happens.
>
> It's gonna be obvious I just know it!
>
> Paul.
>
> PS. Generator is actually NOF 11 even though the tags say 10.
-
Re: I just killed an almost finished client site
Chuck,
You have better eyes than me!
It's a double row AWM and a single menu.js - but I have had several
version before this, so maybe there is some residual stuff in there. I
did do a re-optimise yesterday but I'll revisit this now.
The search area is only for show at the moment but no idea how/why there
is AWM code in it. Again will take a closer look.
And full URL's. Will look into that. Odd though because I have other
sites all using relative and they seem OK (just checked another test
site using relative links and all OK).
Will also change the menu.js name!
Will get back here with an update.
Thanks Chuck (as always!)
Paul
On 18/03/2010 15:37, Chuck Joslin wrote:
> Do you have one two row AWM menu called menu.js? Or two one row menus
> with the same name?
>
> I see two sets of identical linking code after the <body> tag, both
> referring to a menu.js file, but only one piece of code relative to an
> element down in the page.
>
> And on all but the home page, there's some awm code erroneously embedded
> in the search form in the upper right corner of the pages.
>
> Bad upload of the site?
>
> In the menu.js file, you're using relative links rather than full URLs.
> IE isn't handling this well on pages other than the home page, dropping
> the "client2" folder from the URL when you try to navigate from a
> non-home page.
>
> Use full URLs when publishing by asset type so you can use the same menu
> on all pages.
>
> Also, don't leave menus with the default filename of menu.js. Give each
> menu a unique name. If you place multiple menus on a page with the same
> name, it'll break.
>
-
Re: I just killed an almost finished client site
Chuck,
Interesting.....
Like I said your eyes are better than mine.
Have done the clean up and removed all references to AWN (for now). Did
a re-optimize and then a local publish but I am still getting AWM
folders published from the three versions I trialed. So I have folders
awmdata, awmdata1 and awmdata2 plus the (now) old menu.js and a
unicodemenu.js.
I can't see how/where to eliminate these?
When I've cleared that old AWM stuff out I'll end up with FAIAMENU.JS
and a single folder AWMDATA, at least that's the theory...but I need to
clean out those old references.
Paul
On 18/03/2010 15:37, Chuck Joslin wrote:
> Do you have one two row AWM menu called menu.js? Or two one row menus
> with the same name?
>
> I see two sets of identical linking code after the <body> tag, both
> referring to a menu.js file, but only one piece of code relative to an
> element down in the page.
>
> And on all but the home page, there's some awm code erroneously embedded
> in the search form in the upper right corner of the pages.
>
> Bad upload of the site?
>
> In the menu.js file, you're using relative links rather than full URLs.
> IE isn't handling this well on pages other than the home page, dropping
> the "client2" folder from the URL when you try to navigate from a
> non-home page.
>
> Use full URLs when publishing by asset type so you can use the same menu
> on all pages.
>
> Also, don't leave menus with the default filename of menu.js. Give each
> menu a unique name. If you place multiple menus on a page with the same
> name, it'll break.
>
-
Re: I just killed an almost finished client site
Hi again,
Getting concerned now. I have turned off the AWM component from
publishing and there are no references to AWM in the newly published
HTML files (yup - checked each one by hand).
Have re-optimised, saved, closed NOF and started again but I am still
seeing locked assets that shouldn't be there:- see attached
The folders awmdata1 and awmdata2 and the two .js files shouldn't be
there....any clues?
Paul
On 18/03/2010 15:37, Chuck Joslin wrote:
> Do you have one two row AWM menu called menu.js? Or two one row menus
> with the same name?
>
> I see two sets of identical linking code after the <body> tag, both
> referring to a menu.js file, but only one piece of code relative to an
> element down in the page.
>
> And on all but the home page, there's some awm code erroneously embedded
> in the search form in the upper right corner of the pages.
>
> Bad upload of the site?
>
> In the menu.js file, you're using relative links rather than full URLs.
> IE isn't handling this well on pages other than the home page, dropping
> the "client2" folder from the URL when you try to navigate from a
> non-home page.
>
> Use full URLs when publishing by asset type so you can use the same menu
> on all pages.
>
> Also, don't leave menus with the default filename of menu.js. Give each
> menu a unique name. If you place multiple menus on a page with the same
> name, it'll break.
>
-
Re: I just killed an almost finished client site
Hi again....doh!
Problem solved with the locked assets. For those interested....
I had taken the precaution, when trying different AWM navigation
options, to put each of them into separate and unique masterborders.
After settling on the final AWM settings I deleted the pages with the
trial AWM elements and forgot about it.
These components (folders and .js) still want to be published because
they appear on a masterborder - even if your site doesn't use those
masterborders.
So deleting the erroneous masterborders eliminates the publishing of
unwanted components!
OK....I can get back to the main problem now!!!!!!!!
Paul
On 18/03/2010 17:04, Adendum wrote:
> Hi again,
>
> Getting concerned now. I have turned off the AWM component from
> publishing and there are no references to AWM in the newly published
> HTML files (yup - checked each one by hand).
>
> Have re-optimised, saved, closed NOF and started again but I am still
> seeing locked assets that shouldn't be there:- see attached
>
> The folders awmdata1 and awmdata2 and the two .js files shouldn't be
> there....any clues?
>
> Paul
>
>
> On 18/03/2010 15:37, Chuck Joslin wrote:
>> Do you have one two row AWM menu called menu.js? Or two one row menus
>> with the same name?
>>
>> I see two sets of identical linking code after the <body> tag, both
>> referring to a menu.js file, but only one piece of code relative to an
>> element down in the page.
>>
>> And on all but the home page, there's some awm code erroneously embedded
>> in the search form in the upper right corner of the pages.
>>
>> Bad upload of the site?
>>
>> In the menu.js file, you're using relative links rather than full URLs.
>> IE isn't handling this well on pages other than the home page, dropping
>> the "client2" folder from the URL when you try to navigate from a
>> non-home page.
>>
>> Use full URLs when publishing by asset type so you can use the same menu
>> on all pages.
>>
>> Also, don't leave menus with the default filename of menu.js. Give each
>> menu a unique name. If you place multiple menus on a page with the same
>> name, it'll break.
>>
-
Re: I just killed an almost finished client site
Paul,
Don't just turn off the component form publishing... remove the component
placeholder from your pages.
Then delete the awm folders and start again. Remove them manually from your
site folder too.
If you haven't already, in AWM set your menu Site_Root folder to be your
site folder inside of User sites.
You can refer to the AWM tutorial on BeyondFusion for more hints.
--
Chuck Joslin
BeyondFusion.com - Your Fusion Community
www.beyondfusion.com
Register domain names at www.awavedomains.com
"Adendum" <Adendum@hotmail.co.uk> wrote in message
news:hntmqt$ves$1@DailyPlanet.news.netobjects.com. ..
> Hi again,
>
> Getting concerned now. I have turned off the AWM component from
> publishing and there are no references to AWM in the newly published
> HTML files (yup - checked each one by hand).
>
> Have re-optimised, saved, closed NOF and started again but I am still
> seeing locked assets that shouldn't be there:- see attached
>
> The folders awmdata1 and awmdata2 and the two .js files shouldn't be
> there....any clues?
>
> Paul
>
>
> On 18/03/2010 15:37, Chuck Joslin wrote:
>> Do you have one two row AWM menu called menu.js? Or two one row menus
>> with the same name?
>>
>> I see two sets of identical linking code after the <body> tag, both
>> referring to a menu.js file, but only one piece of code relative to an
>> element down in the page.
>>
>> And on all but the home page, there's some awm code erroneously embedded
>> in the search form in the upper right corner of the pages.
>>
>> Bad upload of the site?
>>
>> In the menu.js file, you're using relative links rather than full URLs.
>> IE isn't handling this well on pages other than the home page, dropping
>> the "client2" folder from the URL when you try to navigate from a
>> non-home page.
>>
>> Use full URLs when publishing by asset type so you can use the same menu
>> on all pages.
>>
>> Also, don't leave menus with the default filename of menu.js. Give each
>> menu a unique name. If you place multiple menus on a page with the same
>> name, it'll break.
>>
>
-
Re: I just killed an almost finished client site
Yep....
This can happen with any component. Not just AWM.
It's good housekeeping practice to delete unused master borders you've
created.
Just keep them in your site if you're actually using them.
The defaultmasterborder and the zeromargins master borders are best left
unaltered and only used to make a copy from for use in your site with a
unique name.
--
Chuck Joslin
BeyondFusion.com - Your Fusion Community
www.beyondfusion.com
Register domain names at www.awavedomains.com
"Adendum" <Adendum@hotmail.co.uk> wrote in message
news:hntnga$voc$1@DailyPlanet.news.netobjects.com. ..
> Hi again....doh!
>
> Problem solved with the locked assets. For those interested....
>
> I had taken the precaution, when trying different AWM navigation options,
> to put each of them into separate and unique masterborders. After settling
> on the final AWM settings I deleted the pages with the trial AWM elements
> and forgot about it.
>
> These components (folders and .js) still want to be published because they
> appear on a masterborder - even if your site doesn't use those
> masterborders.
>
> So deleting the erroneous masterborders eliminates the publishing of
> unwanted components!
>
> OK....I can get back to the main problem now!!!!!!!!
>
> Paul
>
>
>
> On 18/03/2010 17:04, Adendum wrote:
>> Hi again,
>>
>> Getting concerned now. I have turned off the AWM component from
>> publishing and there are no references to AWM in the newly published
>> HTML files (yup - checked each one by hand).
>>
>> Have re-optimised, saved, closed NOF and started again but I am still
>> seeing locked assets that shouldn't be there:- see attached
>>
>> The folders awmdata1 and awmdata2 and the two .js files shouldn't be
>> there....any clues?
>>
>> Paul
>>
>>
>> On 18/03/2010 15:37, Chuck Joslin wrote:
>>> Do you have one two row AWM menu called menu.js? Or two one row menus
>>> with the same name?
>>>
>>> I see two sets of identical linking code after the <body> tag, both
>>> referring to a menu.js file, but only one piece of code relative to an
>>> element down in the page.
>>>
>>> And on all but the home page, there's some awm code erroneously embedded
>>> in the search form in the upper right corner of the pages.
>>>
>>> Bad upload of the site?
>>>
>>> In the menu.js file, you're using relative links rather than full URLs.
>>> IE isn't handling this well on pages other than the home page, dropping
>>> the "client2" folder from the URL when you try to navigate from a
>>> non-home page.
>>>
>>> Use full URLs when publishing by asset type so you can use the same menu
>>> on all pages.
>>>
>>> Also, don't leave menus with the default filename of menu.js. Give each
>>> menu a unique name. If you place multiple menus on a page with the same
>>> name, it'll break.
>>>
-
Re: I just killed an almost finished client site
Chuck,
I did remove the placeholder and all references. As you can see from the
earlier post - it was the redundant masterborders that were the problem
causing the locked assets.
So, I've made all the corrections you mentioned Chuck and I'm happy to
say that everything is fine and dandy! Well, almost - with the weird
exception that one page (Glossary) doesn't work like it should (see FAQ
page). Believe it or not it works properly in FF, Chrome and Safari but
not in IE.
My next fix then....the IE Glossary page! Deep joy!
Thanks so much Chuck, again!
Paul
On 18/03/2010 17:20, Chuck Joslin wrote:
> Paul,
>
> Don't just turn off the component form publishing... remove the
> component placeholder from your pages.
>
> Then delete the awm folders and start again. Remove them manually from
> your site folder too.
>
> If you haven't already, in AWM set your menu Site_Root folder to be your
> site folder inside of User sites.
>
> You can refer to the AWM tutorial on BeyondFusion for more hints.
>
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules