I am writing Jest snapshot tests. My snapshot files sometimes contain <!---->. What does it mean?
Example:
<div>
<!---->
<br />
</div>
You're seeing the concatenation of the start <!-- and end --> of a HTML comment tag. Refer to HTML documentation here.
Related
My Stripe Form isn't showing properly. Here is the screenshot.
I included the stripe script tag in my head tag. Added the form and the css and javascript per instructions in stripe docs.
I thought maybe some other links or scripts are overwriting the stripe script so I tried to uncomment them, but nothing changed the stripe form.
I also made sure than my classes aren't overwriting each other.
<head>
...
<!-- Stripe -->
<script src="https://js.stripe.com/v3/"></script>
...
</head>
<body>
...
<form action="/charge" method="post" id="payment-form">
<div class="form-row">
<label for="card-element">
Credit or debit card
</label>
<div id="card-element">
<!-- A Stripe Element will be inserted here. -->
</div>
<!-- Used to display form errors. -->
<div id="card-errors" role="alert"></div>
</div>
<button>Submit Payment</button>
</form>
...
</body>
Figured it out. I just ended up making my own styles tho it took some time.
I´m working in a Windows App but when I want to add a toolTip I get this exception: HierarchyRequestError. I´ve checked if all my tags are properly typed and it seems that there is no problem with them. Any ideas?
<div id="wrapper" data-win-control="WinJS.UI.Tooltip" data-win-options="{contentElement:'info'}">
<img src="images/news.jpg" alt="Donald Trump">
</div>
<section class="info-wrapper">
<div id="info">
<video controls src="videos/info.wmv"></video>
</div>
</section>
Nevermind, I can´t use a dash. I changed it for an underscore and it worked.
I'm using Koken and would like to customize the template for text entries by putting the date at the top of the entry.
I hacked a call to new Date() into the core template file /admin/templates/text.tmpl.html
<div id="entry-editor">
<div id="edit-area" data-bind="html: content() ||
'<p class=\'date\'>' + new Date() + '</p>
<p class=\'media-row\'><br /></p>'">
</div>
</div> <!-- close #entry-editor -->
This works fine, but I know the perils of hacking core files.
As of this writing, I don't see an answer on the page linked as "define your own custom template types" on help.koken.me.
Without hacking core files, how can I have Koken add a date to the top of each text entry?
From http://help.koken.me/customer/portal/questions/1080677-how-to-make-custom-templates-in-koken-
Simply place a <koken:time> tag in the customized theme template.
For example, in my /storage/themes/<custom-theme-name>/essay.lens file:
<header>
<h2>
<koken:link>{{ essay.title }}</koken:link>
</h2>
<p>
<strong><koken:time show="time" /> <koken:time show="date" /></strong>
</p>
</header>
I am testing lungo framework, and by reading their examples (http://lungo.tapquo.com/howto/prototype), it does not work.
I am using their skeleton code:
<body class="app">
<section id="main" data-transition="">
<article id="main-article" class="active">
test.
</article>
</section>
<script src="components/quojs/quo.js"></script>
<script src="components/lungo/lungo.js"></script>
<script type='text/javascript'>
Lungo.init({
name: 'example'
});
</script>
</body>
I have no errors in my console. What can be causing the issue?
Thanks in advance.
If that's all of your HTML, then you're missing a whole bunch of CSS files, etc. Could you share a JS fiddle or longer code example? The way you're not getting any JS errors implies to me you may well be missing some CSS. Also, what version of Lungo are you using? How did you obtain it?
Lots of questions :) However, I created a basic Lungo JSfiddle a while ago - http://jsfiddle.net/otupman/vz59n/ - try that and see if it works. In the "External Resources" section you'll find the CSS & JS I'm including to make it work.
The simple code I'm using (as S/O won't let me post a JSFiddle link without code) simply looks like this:
<section id="main" >
<header data-title="JsFiddle Lungo">
<nav class="left">
<a data-icon="home"></a>
</nav>
</header>
<article class="active" id="first_article">
<strong>Simple Example</strong>
Second article
<br/>
Second section
</article>
<article id="second_article">
<strong>Second article</strong>
First article
<br/>
Second section
</article>
</section>
All of the CSS/JS files are coming from Lungo's example, for example, one CSS is http://lungo.tapquo.com/example/components/lungo/lungo.css
I am currently doing some research into SharePoint Page Layouts and building pages based on those layouts.
I currently have a page layout containing several RichImageFields and RichHtmlFields, but it seems that the first RichImageField is not displaying (doesn't even render out anything).
As far as I can see, he's the same as the others:
<div id="headerImage">
<PublishingWebControls:RichImageField id="HeaderImage" FieldName="HeaderImage1" runat="server"/>
</div>
<div id="middleContent">
<div id="left">
<div id="about">
<fieldset>
<legend>About</legend>
<PublishingWebControls:RichHtmlField ID="About" FieldName="AboutMedicInfo1" runat="server"/>
</fieldset>
</div>
<div id="items">
<h1>
<SharePointWebControls:FieldValue FieldName="ItemsTitle1" runat="server"/></h1>
<PublishingWebControls:EditModePanel runat="server" CssClass="edit-mode-panel">
<SharePointWebControls:TextField runat="server" FieldName="ItemsTitle1" />
</PublishingWebControls:EditModePanel>
<div id="Item1">
<fieldset>
<legend>
<SharePointWebControls:FieldValue FieldName="Item11" runat="server"/></legend>
<PublishingWebControls:EditModePanel runat="server" CssClass="edit-mode-panel">
<SharePointWebControls:TextField runat="server" FieldName="Item11" />
</PublishingWebControls:EditModePanel>
<PublishingWebControls:RichHtmlField ID="Item1" FieldName="Item1Content1" runat="server"/>
</fieldset>
</div>
<div id="Item2">
<fieldset>
<legend>
<SharePointWebControls:FieldValue FieldName="Item21" runat="server"/></legend>
<PublishingWebControls:EditModePanel runat="server" CssClass="edit-mode-panel">
<SharePointWebControls:TextField runat="server" FieldName="Item21" />
</PublishingWebControls:EditModePanel>
<PublishingWebControls:RichHtmlField ID="Item2" FieldName="Item2Content1" runat="server"/>
</fieldset>
</div>
</div>
</div>
<div id="center">
<div>
<PublishingWebControls:RichImageField id="HighLight1" FieldName="HighLight11" runat="server"/></div>
<div>
<PublishingWebControls:RichImageField id="HighLight2" FieldName="HighLight22" runat="server"/></div>
<div>
<PublishingWebControls:RichImageField id="HighLight3" FieldName="HighLight32" runat="server"/></div>
</div>
<div id="right">
<div id="report">
<PublishingWebControls:RichHtmlField ID="Report" FieldName="Report" runat="server"/>
</div>
<div id="webparts">
<WebPartPages:WebPartZone runat="server" Title="Rechtsonder" ID="BottomRightControl"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone></div>
</div>
</div>
</div>
The funny thing is that I'm perfectly able to see the image when I'm in editing mode and when I'm viewing the Page Library items (after I added the specified field to the view).
Does anyone have any experience with this? Feel free to ask further questions if I might be unclear.
Okay, I should have checked before posting my initial question. It turned out that my problem was because I was using the Page content type, instead of the Article Page or Welcome Page content types. The Page CT doesn't have the field that the image was looking for.
What I find really interesting is that it still let me select the image AND it stored the value somewhere... even though there was no official field for it. I suspect that the field in the library is there, since you would need it for your other content types.
Anyway, hoping that someone else may find this useful.
Make sure that you don't miss the two properties RichText="TRUE" and RichTextMode="FullHtml" of the image field definition to be like:
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Field
ID="{4ea31e74-f59d-4ddf-863c-607a01735f65}"
Name="pls_H2_2_Image"
DisplayName="Titel 2 Bild"
Type="Image"
Required="FALSE"
RichText="TRUE"
RichTextMode="FullHtml"
Group="Custom">
</Field>
</Elements>
I faced this issue before and this solution did it properly.