Looking at Jez's page source I notice that none of the script codes start with <script type=... they all start with <"text/javascript"... Not sure why, but thought that may give you an idea of where to start looking for a solution.
The removed script is actually part of the WSN error display process and not reflective of the template -- to prevent all possible popups from popping up when the page is output without conditionals. It'd less confusing to asciize it instead of removing words though, will change.
Paul, emailing you. The last fixes did not work. I am away for a few days without any net access I am hoping that you can fix and I'll pay you. I just need it done.
The layout was all a bit messed up after you managed to resore what you did so I searched through the code to see if I could see what was wrong and I found 2 of the below:
It would've created one copy of that block in autoapplying template changes, and left instructions to remove the other copy, but you weren't able to see the instructions.
The errors were caused by similarly added/non-removed spots that led to mismatched conditionals.
0/5
1
2
3
4
5
Sorry, you don't have permission to post posts. Log in, or register if you haven't yet.
Comments on Upgrade errors
Forum Regular
Usergroup: Customer
Joined: Apr 03, 2007
Location: NY & PA
Total Topics: 94
Total Comments: 339
Paul,
Looking at Jez's page source I notice that none of the script codes start with <script type=... they all start with <"text/javascript"... Not sure why, but thought that may give you an idea of where to start looking for a solution.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Downloaded the wrapper and put it on one of my installs to test. needs another </IF> at the end.
Needs </IF></IF> added at the end.
Did you not apply the additional listed changes after it did the autochanges, or were these changes not listed?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Not sure if this is your problem, but when viewing the source of the page I noticed your StatCounter code shows -
<"text/javascript" language="javascript"> in 2 places try changing to -
<script type="text/javascript" language="javascript">
The removed script is actually part of the WSN error display process and not reflective of the template -- to prevent all possible popups from popping up when the page is output without conditionals. It'd less confusing to asciize it instead of removing words though, will change.
Forum Regular
Usergroup: Customer
Joined: Jan 19, 2007
Total Topics: 32
Total Comments: 130
Paul, emailing you. The last fixes did not work. I am away for a few days without any net access I am hoping that you can fix and I'll pay you. I just need it done.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Done.
Forum Regular
Usergroup: Customer
Joined: Jan 19, 2007
Total Topics: 32
Total Comments: 130
Paul, I just paid you.
The layout was all a bit messed up after you managed to resore what you did so I searched through the code to see if I could see what was wrong and I found 2 of the below:
I would not have duplicated that myself - was it caused by the failed upgrade? Was it part of the problem?
Thanks to babrees and hai who tried to help me in this thread.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
It would've created one copy of that block in autoapplying template changes, and left instructions to remove the other copy, but you weren't able to see the instructions.
The errors were caused by similarly added/non-removed spots that led to mismatched conditionals.