Base solution for your next web application
Open Closed

<p-editor can not bind [ngModel] #11328


0
feryat.olcay created

Prerequisites

Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • What is your product version? V11.3.0
  • What is your product type (Angular or MVC)? Angular
  • What is product framework type (.net framework or .net core)? .Net Core 6

If issue related with ABP Framework

  • What is ABP Framework version? 7.3

If issue is about UI

  • Which theme are you using? Default
  • What are the theme settings? Default

Hello After upgraded my project from V9.3.0 to V11.3.0 version "p-editor " is not binding [ngMode].
After I change to calling menu's items via model instead of componet than this error getting started. According my search on internet that I have to import FormsModule to the module, even I did it is still same.

Note:I have an open isse about PrimeNg .May be both issues are releated each other .

/HTML/ <div class="col-sm-12"> <div class="form-group"> <p-editor ** [(ngModel)]="update.description" ** [ngModelOptions]="{standalone: true}" [style]="{'height':'320px'}" [modules]="{'imageResize': {'displaySize': true}}"> </p-editor> </div> </div>

/Model/ import { NgModule } from '@angular/core'; import { FormsModule } from '@angular/forms'; ....


3 Answer(s)
  • 0
    ismcagdas created
    Support Team

    Hi @feryat.olcay

    To fix your problem with PrimeNg with table load, you need to upgrade your PrimeNg version. If that doesn't solve this problem, is it possible to share your project with us, so we can check it for you ?

    Thanks,

  • 0
    feryat.olcay created

    Hi,

    thank you for the return. I upgraded the version of PrimeNG to "13.0.4" but the problem is still same. "primeng": "^13.0.4",

    Is that possible to you connect to my computer .

    Regards

  • 0
    ismcagdas created
    Support Team

    Hi @feryat.olcay

    Is it possible to share your project with us via email ([email protected]) ? If you get this error when running npm start command, you can just share the angular folder. In that way, we can address the problem faster.