I'm getting this error with angular 4:
The <template> element is deprecated. Use <ng-template> instead ("
[attr.tabIndex]="-1"
[ngClass]="{'k-item': true}">
[WARNING ->]<template *ngIf="template"
[templateContext]="{
are you planning on updating this for the final release?
Yes, the components have been updated and released with Angular 4 support.
Related
We’ve been working with mongoose#^5.4.11 and due to the MongoDB Server upgrade to version 5, we are upgrading to mongoose#6.1.7.
In our code we have this line:
Model.base.modelSchemas[modelName].paths
after upgrading to 6.1.7 I get undefined for modelSchemas.
I cloned the mongoose repo for tag 5.4.11, and there modelSchemas is a property of the Mongoose class in ‘lib/index.js/’
I also cloned the mongoose repo for tag 6.1.7, and there modelSchemas is not defined anywhere (only see mentions of it in docs files)
In the mongoose migration guide 5 to 6 modelSchemas is not mentioned anywhere.
I think I have things working again by changing the code to:
Model.base.model(modelName).schema.paths
Could someone confirm this change is exactly equivalent to the original statement?
Using the REST API, I have no issues creating and updating task items in Todoist. However, I can't seem to remove a due date completely from an item.
This works for setting the due date:
{"due_date":"2020-01-20"}
I have tried the following for removing it with no luck.
{"due_string":"null"}
{"due_string":null}
{"due":{"date": null }}
{"due":{"string": null }}
{"due":null}
{"due":"null"}
How can I accomplish this?
{ due_string: "no due date" } will do the trick.
Have you tried {"due": null}?
According to the API spec it should work.
If you're using Python to generate the request, and depending on how you generate the actual request, you might consider using the None keyword.
I'm migrating Odoo module from version 10 to version 11. I have website template with following code:
<ul class="dropdown-menu js_language_selector" t-if="(request and request.website_multilang and len(languages) > 1) or (website and (editable or translatable))">
It raises AttributeError: 'HttpRequest' object has no attribute 'website_multilang'. I can't find documentation on how to adapt this Odoo 10 code to v11?
You can try following :
<ul class="dropdown-menu js_language_selector" t-if="(request and request.is_frontend_multilang and len(languages) > 1) or (website and (editable or translatable))">
I have just analysed that in v11 it needs to be "is_frontend_multilang" instead of "website_multilang".
Hope it works.
Regards
I'm using Orchard 1.7
In Orchard, when a content item is removed, it don't actually deleted from database, the cms just only set Published & Latest value of all versions of content item to 0, it still can be retrieved
And my problem is: I have a user that was removed (this user was modified many times, especially the Title)
Case 1: I use cms.Get(userId, VersionOptions.AllVersions).As<TitlePart>()
Case 2: I use myItem.As<CommonPart>().Owner.As<TitlePart>()
And the result is it always returns the title of the first version of this user, I want it return the latest version (the largest version number) of it.
So, where in Orchard should I modify to resolve this ?
I had this issue too. Here is my solution to query the recent version of a deleted user by using the content manager:
Orchard.Users.Models.UserPart lUserPart = mContentManager
.Query<Orchard.Users.Models.UserPart,
Orchard.Users.Models.UserPartRecord>(VersionOptions.AllVersions)
.Where(u => u.NormalizedUserName == lowerName) // taken from Orchard.Users.Services.MembershipService.GetUser()
.List()
.LastOrDefault(); // LastOrDefault() to get version with highest version number
The quality of the item excerpt of a search result seems to differ between Magnolia 5.4.1 CE and 5.4.3 CE. I have the same website/pages on both system. On 5.4.1, the excerpts look good and it actually shows the parts where the keywords occurs and highlights them, whereas on 5.4.3, the excerpts does not show this but instead shows weird UUIDs and author names, that should not be visible to a public user:
The content nodes on both systems have the identical content. I pretty much use the default installation of 5.4.1 and 5.4.3 CE.
Anybody else having this problem or knows a reason for this? Is it a bug? Any way to fix this without having to write my own SearchTemplatingFunctions or ExcerptProvider?
The code that I use for the search:
[#-------------- ASSIGNMENTS --------------]
[#assign queryStr = ctx.getParameter('q')!?html]
[#-------------- RENDERING --------------]
[#if queryStr?has_content]
[#assign searchResults = searchfn.searchPages(queryStr, '/mysubfolder') /]
[#assign recordsFound = searchResults?size /]
<h3><em>${recordsFound}</em> ${i18n['search.pagesFoundFor']} "${queryStr}"</span></h3>
<div class="list-group">
[#if searchResults?has_content]
[#list searchResults as item]
<a href="${cmsfn.link(item)}" class="list-group-item">
<h4 class="list-group-item-heading">${item.title!}</h4>
<p class="list-group-item-text">${item.excerpt!}</p>
</a>
[/#list]
[/#if]
</div>
[/#if]
Thanks.
================== Update ==================
It seems to be a know bug as per https://jira.magnolia-cms.com/browse/MAGNOLIA-6245 but it is said to be fixed (in June 2015). However I still have the issue. See my comment in the Jira Ticket: https://jira.magnolia-cms.com/browse/MAGNOLIA-6245?focusedCommentId=120828&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-120828
================== Update 2 ==================
I setup a new 5.4.3 locally, where the issue does not occur. The issue still occurs at the 5.4.3 instance at my hosting provider though (about which my original posting is about). I downloaded the repo-conf, and made a diff with my local repo-conf folder, there are no differences in either jackrabbit-memory-search.xml nor jackrabbit-bundle-mysql-search.xml.
I found the solution to the problem thanks to a hint in the Jira:
https://jira.magnolia-cms.com/browse/MAGNOLIA-6245?focusedCommentId=120872&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-120872
The lines
<!-- needed to highlight the searched term -->
<param name="supportHighlighting" value="true"/>
<!-- custom provider for getting an HTML excerpt in a query result with rep:excerpt() -->
<param name="excerptProviderClass" value="info.magnolia.jackrabbit.lucene.SearchHTMLExcerpt"/>
were also missing in the file
${magnolia.repositories.home}/magnolia/workspaces/website/workspace.xml
due to some mistake at the hosting provider's template which they use for setting up Magnolia.