A few template problems

Quote from: goonz at Mar 08, 2011, 09:20 PM

Can you show me what Wayfinder is spitting out, and tell me which page it is on?

http://www.scotiahouse.co.uk/ is the website page it is on. The first button should say Scotia House but it’s just white on white. And there should be button graphics behind...

This may be part of your problem. Found this in your stylesheet:

this is where I bought the template:

http://www.4templates.com/view/website-templates/0/AX0352OR

but as soon as I tried to convert it to modx I lost those background images behind buttons...

I can’t see the original template files to compare and contrast. Check your output and compare it to the original files. The styling for your links is also not showing up correctly. Check your CSS file and the location of your image files, and make sure that the relative path actually points to where those images now reside. Also, you should pull out the closing style tag; it may not do anything, but it will be better if it is gone.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.scotiahouse.co.uk%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Hi I’ve put the original html back in and coded it manually instead of using wayfinder so you can see how it should look:

http://www.scotiahouse.co.uk

I would still like to get this to work in wayfinder but if not I’ll just leave it this way... thanks again for your help.

I think you need to go through the original HTML and the output coming from Wayfinder to make it all matches up, and everything should start working for you. You may need to add the following parts to your WF call:
&rowIdPrefix=`menu` but you will need to change your CSS to reflect your doc IDs, because the id will become menu+DocID.
&firstClass=`first`
You can also go through the Wiki to find other help:
http://wiki.modxcms.com/index.php/Wayfinder Also, Check out that book again.

As of right now you have an unmatched </style> on your page.

whistlemaker, I saw that also which is why I posted the validator link. do you know if that would cause errors like that though? I’ve never left an unmatched </style> tag, so I’m wondering....thanks!

I have no idea what an unmatched style tag will do - I would bet the farm that it depends on the browser, other stuff on your page and the way the planets are aligned

begin <rant>
It just is good practice as I’m sure you are aware to have the code right - browsers let people get away with way too much stuff and unfortunately this will not change because if it did so many pages would break and would the page owners/creators be blamed? No the browser would be blamed - so the browsers will somehow guess what the coder intended BUT on the other hand bad syntax will produce seemingly random errors always in which ever browser you do not check - Murphy’s Law - well maybe that is being too pessimistic but still. Good practice suggests it is good to check your syntax (I use BBedit for coding and it has a wonderful syntax checker - probably other programs do as well) and to use an online validator such as the w3c one - though at times it seems that you have to bend their rules, just as long as you know why the code is not valid and there is a good reason for it!!!!
</rant>

your rant +1