Undefined property error while trying to create a new resource










0















I get the Undefined property AppPlan::$bandwidth error when I try to create a new Resource or save the edited value.



However, values are listed fine for the same field during view/edit.



Here is the field definition:




Number::make('Bandwidth', 'bandwidth')->min(0),










share|improve this question


























    0















    I get the Undefined property AppPlan::$bandwidth error when I try to create a new Resource or save the edited value.



    However, values are listed fine for the same field during view/edit.



    Here is the field definition:




    Number::make('Bandwidth', 'bandwidth')->min(0),










    share|improve this question
























      0












      0








      0








      I get the Undefined property AppPlan::$bandwidth error when I try to create a new Resource or save the edited value.



      However, values are listed fine for the same field during view/edit.



      Here is the field definition:




      Number::make('Bandwidth', 'bandwidth')->min(0),










      share|improve this question














      I get the Undefined property AppPlan::$bandwidth error when I try to create a new Resource or save the edited value.



      However, values are listed fine for the same field during view/edit.



      Here is the field definition:




      Number::make('Bandwidth', 'bandwidth')->min(0),







      laravel-nova






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 16 '18 at 0:52









      mishkamishka

      425416




      425416






















          1 Answer
          1






          active

          oldest

          votes


















          3














          The model had a method with the same name. Works fine after the renaming the method. I wonder if this is a bug.






          share|improve this answer




















          • 1





            Same issue here. You ever found a way to resolve this issue without having to rename the method?

            – timgvandijk
            Dec 24 '18 at 15:17











          • Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

            – mishka
            Dec 25 '18 at 0:23











          • Has this issue been resolved?

            – Farveaz
            Feb 22 at 6:50











          • @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

            – mishka
            Feb 23 at 15:47










          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329936%2fundefined-property-error-while-trying-to-create-a-new-resource%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          The model had a method with the same name. Works fine after the renaming the method. I wonder if this is a bug.






          share|improve this answer




















          • 1





            Same issue here. You ever found a way to resolve this issue without having to rename the method?

            – timgvandijk
            Dec 24 '18 at 15:17











          • Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

            – mishka
            Dec 25 '18 at 0:23











          • Has this issue been resolved?

            – Farveaz
            Feb 22 at 6:50











          • @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

            – mishka
            Feb 23 at 15:47















          3














          The model had a method with the same name. Works fine after the renaming the method. I wonder if this is a bug.






          share|improve this answer




















          • 1





            Same issue here. You ever found a way to resolve this issue without having to rename the method?

            – timgvandijk
            Dec 24 '18 at 15:17











          • Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

            – mishka
            Dec 25 '18 at 0:23











          • Has this issue been resolved?

            – Farveaz
            Feb 22 at 6:50











          • @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

            – mishka
            Feb 23 at 15:47













          3












          3








          3







          The model had a method with the same name. Works fine after the renaming the method. I wonder if this is a bug.






          share|improve this answer















          The model had a method with the same name. Works fine after the renaming the method. I wonder if this is a bug.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 16 '18 at 12:54

























          answered Nov 16 '18 at 3:40









          mishkamishka

          425416




          425416







          • 1





            Same issue here. You ever found a way to resolve this issue without having to rename the method?

            – timgvandijk
            Dec 24 '18 at 15:17











          • Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

            – mishka
            Dec 25 '18 at 0:23











          • Has this issue been resolved?

            – Farveaz
            Feb 22 at 6:50











          • @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

            – mishka
            Feb 23 at 15:47












          • 1





            Same issue here. You ever found a way to resolve this issue without having to rename the method?

            – timgvandijk
            Dec 24 '18 at 15:17











          • Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

            – mishka
            Dec 25 '18 at 0:23











          • Has this issue been resolved?

            – Farveaz
            Feb 22 at 6:50











          • @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

            – mishka
            Feb 23 at 15:47







          1




          1





          Same issue here. You ever found a way to resolve this issue without having to rename the method?

          – timgvandijk
          Dec 24 '18 at 15:17





          Same issue here. You ever found a way to resolve this issue without having to rename the method?

          – timgvandijk
          Dec 24 '18 at 15:17













          Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

          – mishka
          Dec 25 '18 at 0:23





          Have you tried v1.2.1? nova.laravel.com/releases It seems to address many known issues. I still think it's not production-ready.

          – mishka
          Dec 25 '18 at 0:23













          Has this issue been resolved?

          – Farveaz
          Feb 22 at 6:50





          Has this issue been resolved?

          – Farveaz
          Feb 22 at 6:50













          @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

          – mishka
          Feb 23 at 15:47





          @Farveaz No. I don't think so. I haven't tried it with 1.3.2 though. Too many issues, had to put off using Nova for production unfortunately.

          – mishka
          Feb 23 at 15:47



















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329936%2fundefined-property-error-while-trying-to-create-a-new-resource%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Top Tejano songwriter Luis Silva dead of heart attack at 64

          政党

          天津地下鉄3号線