All my CSS Menus have stopped working and the error message I get is: fwParameters.markertop has no properties
This occurs even in menus I haven’t altered.
I can’t clear this error and if i create a new CSS Menu, I get an error message straight away.
Anyone know what has changed?
Can you send your Freeway file into support(a)softpress.com so we can
take a closer look please.
Thanks,
Joe
On 16 Jun 2008, at 18:22, AndrewMS wrote:
All my CSS Menus have stopped working and the error message I get
is: fwParameters.markertop has no properties
This occurs even in menus I haven’t altered.
I can’t clear this error and if i create a new CSS Menu, I get an
error message straight away.
Anyone know what has changed?
Has anybody got a fix to this yet or is it something we have to live with? All CSS menus have stopped working. Beginning to think that this action is too buggy to use.
Once again - yawn - all my css menus have gone to pot with the now super familiar "action has KNOWN javascript ERROR’ stemming from the css menu action
Is it really impossible to change a css menu once it has been published without this happening?
Somebody else HAS to be getting this?
The GOOD news is that I can remember exactly what happened.
I decided to change a word in the menu and deleted it on a master page.
I copied the entire html box with the css action attached and went to each master page and deleted the existing css menu html box and pasted the new one.
Why is my FWY file now going beserk and telling me I have a known javascript error? This HAS to be a bug - surely?
This is by the by, but your example is a candidate for saving immediately
before trying out a likely candidate for calamity - then one can at least
revert.
I confess to failing to get off the starting block with CSS layouts except
in specific requirements.
But I trust that by the time it becomes mandatory - Softpress will have made
it a lot easier to just do it and not make a mess.
all the best
Brian
John-Paul Kernot said recently:
Once again - yawn - all my css menus have gone to pot with the now super
familiar "action has KNOWN javascript ERROR’ stemming from the css menu action
Is it really impossible to change a css menu once it has been published
without this happening?
Somebody else HAS to be getting this?
The GOOD news is that I can remember exactly what happened.
I decided to change a word in the menu and deleted it on a master page.
I copied the entire html box with the css action attached and went to each
master page and deleted the existing css menu html box and pasted the new one.
Why is my FWY file now going beserk and telling me I have a known javascript
error? This HAS to be a bug - surely?
It may not be a bug. I’ve copied and pasted CSS Menus without a
problem. However, if you have edited them, check that the list
parameters are set at default and, if you’ve added a word or two,
check that your styles have taken. You may have to highlight your
addition and click again on the chosen style in the styles pallet.
Why? I haven’t a clue, as I am somewhat ‘code challenged’!
Also if you remove the Action, clear the Javascript error and then
reunite the menu with the Action, that may fix it. But definitely no
promises. :-0
Colin
On 22 Jan 2009, at 18:05, John-Paul Kernot wrote:
Once again - yawn - all my css menus have gone to pot with the now
super familiar "action has KNOWN javascript ERROR’ stemming from the
css menu action
Is it really impossible to change a css menu once it has been
published without this happening?
Somebody else HAS to be getting this?
The GOOD news is that I can remember exactly what happened.
I decided to change a word in the menu and deleted it on a master
page.
I copied the entire html box with the css action attached and
went to each master page and deleted the existing css menu html box
and pasted the new one.
Why is my FWY file now going beserk and telling me I have a known
javascript error? This HAS to be a bug - surely?
It does sound like a bug yes, but we still haven’t seen your file in
support yet. If we can repeat the problem in house it makes it a lot
easier to pinpoint and fix the problem.
If you could send it, or a cut down version of it to
support(a)softpress.com that would be most appreciated.
On 22 Jan 2009, at 20:10, Colin Alcock email@hidden wrote:
It may not be a bug. I’ve copied and pasted CSS Menus without a
problem. However, if you have edited them, check that the list
parameters are set at default and, if you’ve added a word or two,
check that your styles have taken. You may have to highlight your
addition and click again on the chosen style in the styles pallet.
Why? I haven’t a clue, as I am somewhat ‘code challenged’!
Also if you remove the Action, clear the Javascript error and then
reunite the menu with the Action, that may fix it. But definitely no
promises. :-0
Colin
On 22 Jan 2009, at 18:05, John-Paul Kernot wrote:
Once again - yawn - all my css menus have gone to pot with the now
super familiar "action has KNOWN javascript ERROR’ stemming from
the css menu action
Is it really impossible to change a css menu once it has been
published without this happening?
Somebody else HAS to be getting this?
The GOOD news is that I can remember exactly what happened.
I decided to change a word in the menu and deleted it on a
master page.
I copied the entire html box with the css action attached and
went to each master page and deleted the existing css menu html box
and pasted the new one.
Why is my FWY file now going beserk and telling me I have a known
javascript error? This HAS to be a bug - surely?