Why is setting html properties false considered an unexpected token? - html

I'm unable to build a VB.NET site I've inherited due to a nebulous error.
Without a clue as to what might be causing it, I turned the hounds of the Czech Republic loose on it (otherwise known as Resharper). It ended up showing me 20 errors and upwards of a thousand other "issues" with the solution:
Okay, so I'm going after the errors first; ASP Errors first. The first one pointed to this:
<telerik:RadButton ID="ExportButtonRad" DisabledButtonCssClass="rbDownload' UseSubmitBehavior="false" EnableViewState="false" AutoPostBack="true" CommandName="ExportToExcel" Skin="Default" Visible="false" OnClientClick="document.body.style.cursor = 'wait';" ButtonType="StandardButton" HoveredCssClass="goButtonClassHov" ToolTip="Export" runat="server" Text="Export">
...and flagged the following portion:
UseSubmitBehavior="false"
...as an "Unexpected token"; so I removed that, and re-ran the Resharper > Inspect > Code Issues in Solution.
Now there are more (not less) ASP Errors, and that same element ("ExportButtonRad") is red-flagged again for the same supposed infraction ("Unexpected token"); this time EnableViewState="false" is the culprit or scapegoat.
So I'm afraid that if I remove that, I will have 11 ASP Errors and it will finger some other property set to false as being bogus. I have suspicions this is not the real problem. Does anybody know about any "gotchas" with this that might be the underlying cause of this whack-a-moliation?

I think the problem will be this:
DisabledButtonCssClass="rbDownload'
Equalise the quotes.
DisabledButtonCssClass="rbDownload"

Related

Dynamically adding/removing TabViewItem in NativeScript tabs project

I have a NativeScript 8.1 JavaScript project that uses the tabs template, so that the app-root.xml file looks like this:
<TabView tabTextFontSize="16" androidOffscreenTabLimit="0" androidTabsPosition="bottom"
id="tabview" class="ns-light" loaded="onLoaded" >
<TabViewItem title="Riders" iconSource="res://biking_solid" >
<Frame id="main" defaultPage="views/main-page" />
</TabViewItem>
<TabViewItem title="Volunteers" iconSource="res://hands_helping_solid" >
<Frame id="vol" defaultPage="views/volunteers-page" />
</TabViewItem>
<TabViewItem title="Director" iconSource="res://user_ninja_solid" >
<Frame id="director" defaultPage="views/director-page" />
</TabViewItem>
</TabView>
The catch here is that the third tab needs to be conditional and only visible if the user is authorized. I've tried pop'ing the TabView's item's array. I've tried creating a new TabViewItem and pushing it onto the items array. I've tried using the visibility property, and none of these work.
I'll know at startup time whether the third tab should be displayed, so handling this in app-root.js is fine. I'm OK with creating all of the tabs dynamically but I can't get that to work either. I could live with disabling the third tab but the enabled property on TabViewItem is ignored.
In short, I've tried everything I can think of and I'm unable to change the TabViewItem's in any way. I realize the underlying implementations are likely imposing some restrictions, but still, is there any way I can control whether the third tab is visible?
This doesn't really answer the question, but it does solve my problem. I can have two separate app-root files, say app-root2 and app-root3, then in app.js I can apply logic and start the appropriate one:
if (<condition>)
application.run({ moduleName: "app-root2" });
else
application.run({ moduleName: "app-root3" });
Edit 4/10/2022: I ended up switching to the BottomNavigation component and dealt with the same issue. That, and the accompanying solution, is described in this post.

VS code Error : settings.json property expected (bug)

enter image description here
When I use VS Code, a problem notice likes that(in the above image) is printed.
Although I want to fix it and really don't want to see it, I can't find any way to fix.
I am very painful about just seeing that error message all the time.
Please give me some helps.
You opened a { parenthesis at line 2784 and didn't close it. You should close it. --> }
Also, you have an extra comma , at 2793 that you have to remove.
Not use {}, because you may already mess your settings.json before.
so my suggestion as follows:
// in/your/settings.json/file
...
setting0_name:[setting0.0, setting0.1],
seting1_name : settings,
...

MediaWiki: how to prevent template from inserting white space?

Today, I tried to create a template on Portuguese Wikipedia inside one of my subpages. It works fine with this code:
<includeonly>'''{{{num}}}''': <span style="font-family:monospace;">{{{date}}}</span> — [[{{{title}}}]]<!--
--> {{#if:{{{faults|}}}<!--
-->|({{{faults}}})<!--
--->|}}<br /></includeonly>
This code creates items like this:
81: 28/feb — Der heimliche Aufmarsch gegen die Sowjetunion (one source)
But, I want to do more! The purpose of creating this template isn't just to set the date to monospace fonts... I want to add support for information about translations, and about deletions. Every time I tried to add text about deletions (you can check in the page history), the space between the lines got enormous, making the "lists" very, very ugly...
For example, this is one of the solutions I tried to add deletion information:
<includeonly>'''{{{num}}}''': <span style="font-family:monospace;">{{{date}}}</span> — [[{{{title}}}]]<!--
--> {{#if:{{{faults|}}}<!--
-->|({{{faults}}})<!--
-->|}}<!--
-->{{#if:{{{Speedy-del|{{{Semi-speedy-del|{{{Consensus-del|}}}}}}}}}|
{{#if:{{{Speedy-del|}}}<!--
-->|<div style="margin-left:2em">✘ <small>Speedy deletion denied by {{{Speedy denier}}} on {{{Speedy date}}}</small></div><!--
-->|}}
{{#if:{{{Semi-speed-del|}}}<!--
-->|<div style="margin-left:2em">✘ <small>Semi-speedy deletion denied by {{{Semi-speedy denier}}} on {{{Semi-speedy date|}}}</small></div><!--
-->|}}
{{#if:{{{Consensus-del|}}}|<!--
--><div style="margin-left:2em">✘ <small>Consensus deletion denied on {{{Consensus date|}}}</small></div><!--
-->|}}
|<br />}}</includeonly>
Why is this happening to me? I could not find any typo. So the problem must be logical, and I gave up trying to find a solution alone. My logic must be broken.
You can use HTML comments if you want to make sure there is no extra output from your template, but still need linebreaks etc for readability:
<includeonly><!--
-->'''{{{num}}}''': {{{date}}}<!--
-->[[{{{title}}}]]<!--
-->{{#if:{{{faults|}}}| ({{{faults}}})|}}<br><!--
--></includeonly>

ExpressionEngine not showing when there are no comments

I can't seem to figure out why ExpressionEngine is not displaying the message when there are when there are no comments. The way it works now, when there are no comments nothing is displayed. When there is one comment, the comment is displayed. I also noticed when there are no comments it won't execute anything inside of the comment:entries loop.
{exp:comment:entries channel="article" url_title="{segment_4}" orderby="{entry_date}" sort="desc" dynamic=“no”}
{if no_results}
<p>Nothing has been said yet. Write something.</p>
{/if}
{comment}
<p class="comment-by">By {if "{url}" != ""}{name}{if:else}{name}{/if} on {comment_date format="%Y %m, %d"}</p>
{/exp:comment:entries}
I'm unable to test this, but you have dynamic="no" on, and url_title="{segment_4}".
dynamic="no" prevents the URI from having any effect on the content of a weblog. Whether this has any effect when the url_title is specified using a {segment_x} variable, I do not know. (This is speculation)
However your code seems needlessly complicated, when the following will work fine for a single page entry:
{exp:comment:entries sort="asc" limit="20"}
{if no_results} There are no comments... {/if}
{comment}
<p>By {name} on {comment_date format="%Y %m %d"}</p>
{/exp:comment:entries}
You don't need to specify channel/url_title in the comments tag (assuming you are on a single page entry, which I believe you are from your post).
Try that, see if you get the desired result.

Internet Explorer form input problem

I'm having a ton of problems with every version of IE, one of which is that IE7 won't register input in this text input field.
http://www.flightm8.com/redesign
I'm a bit nervous about posting the link since the site looks a mess and doesn't function properly in any version of IE at the moment, and it is still quite a way off being ready for public consumption. But if anyone can shed any light on this particular problem I'd very much appreciate it.
So the question is: What is causing this problem in IE7?
Update: I've also added an additional textfield at the bottom of the page to try and rule out any CSS wierdness that might be causing the problem.
<form method="post" action="nowhere.php">
<input type='text' name='test' value='testing' />
</form>
And I still can't enter any text, or select the text that is in there. I'm wondering now if it's a problem caused by running a standalone version of IE7 and IE6.
thanks
-t
the function causing problem is this one :
function modalAlert
the call that need to be debugged is this one :
modalAlert("NO SELECTIONS");
in
function findRoutes
the line that bug is :
$("#dialog").css("top", dTop);
first, you should avoid iframes when you can, why don't you do :
var message = $('<div></div>').load('/modal/"+modalpage);
instead of crappy code like this :
var iframe = "<iframe id='modal_frame' width='533' height='292' src='/modal/"+modalpage+"' >You didn't give me any information</iframe>"
If you don't need iframes, don't use them !
$('body').append(message);
I have IE7 on win xp (native), I was able to enter text but after a freeze (when you add all those markers), then when entering text and clicking on "find routes", there's a bug that i just explained to you ...
I would imagine it is because the input box doesn't have a 'name' field, which is used when posting form data.