Fluid variables do not read the child values anymore. (TYPO3 9.5.*)Are fluid websites worth making anymore?TYPO3 extbase fluid: nested object in loopHow to access localized page properties in TYPO3 FLUID?How to get parent Information from child object with TYPO3 extbaseCreate an and validate Parent/Child Objects with Typo3 Extbase Fluid<![CDATA[ … ]]> not working in TYPO3 v8 FluidTYPO3 8.7 update with child elements m:n not workingTypo3 9.5 Language dependent variables rendered in FluidTYPO3 9.5.x / TypoScript / Fluid: Get variable of type FILES unrenderedHow to compare a string with a variable in TYPO3 Fluid

Attacking the Hydra

Is there a word for returning to unpreparedness?

Meaning of だけはわからない

How do I pass a "list of lists" as the argument to a function of the form F[x,y]?

Did Michelle Obama have a staff of 23; and Melania have a staff of 4?

Set theory with antielements?

Output with the same length always

Will Force.com stop working on salesforce Lightning?

A Magic Diamond

100 Years of GCHQ - A quick afternoon puzzle!

How to prevent criminal gangs from making/buying guns?

Why does Japan use the same type of AC power outlet as the US?

Why do so many people play out of turn on the last lead?

Why do we use low resistance cables to minimize power losses?

Typesetting "hollow slash"

Build a mob of suspiciously happy lenny faces ( ͡° ͜ʖ ͡°)

How to gracefully leave a company you helped start?

Minimum population for language survival

Why is the battery jumpered to a resistor in this schematic?

Insert or push_back to end of a std::vector?

Adding things to bunches of things vs multiplication

What should I do if actually I found a serious flaw in someone's PhD thesis and an article derived from that PhD thesis?

Can anyone help me what's wrong here as i can prove 0 = 1?

How can I enter recovery mode (for Mac OS, on an iMac) remotely?



Fluid variables do not read the child values anymore. (TYPO3 9.5.*)


Are fluid websites worth making anymore?TYPO3 extbase fluid: nested object in loopHow to access localized page properties in TYPO3 FLUID?How to get parent Information from child object with TYPO3 extbaseCreate an and validate Parent/Child Objects with Typo3 Extbase Fluid<![CDATA[ … ]]> not working in TYPO3 v8 FluidTYPO3 8.7 update with child elements m:n not workingTypo3 9.5 Language dependent variables rendered in FluidTYPO3 9.5.x / TypoScript / Fluid: Get variable of type FILES unrenderedHow to compare a string with a variable in TYPO3 Fluid






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















So i have a table which lists some appointments. These appointments belong to an event. The goal here is to list all the appointments and get the information of the event that they belong to.



So far everything works fine until i try to get the information of the event. I get an object which looks like this:



enter image description here



Now if i use something like this : appointment.event.title it will give back NULL.



That means that it doesnt access the properties. In TYPO3 v8 it works perfectly, but not in TYPO3 v9.



If i activate the <f:debug>appointment</f:debug> and get the whole object as debugged, then this appointment.event.title works! I can get the title.



The question now is what have changed since TYPO3 8 and can not access these properties anymore and how can i regain access?



In use: TYPO3 v9



Mode: Composer



Best regards,










share|improve this question
































    0















    So i have a table which lists some appointments. These appointments belong to an event. The goal here is to list all the appointments and get the information of the event that they belong to.



    So far everything works fine until i try to get the information of the event. I get an object which looks like this:



    enter image description here



    Now if i use something like this : appointment.event.title it will give back NULL.



    That means that it doesnt access the properties. In TYPO3 v8 it works perfectly, but not in TYPO3 v9.



    If i activate the <f:debug>appointment</f:debug> and get the whole object as debugged, then this appointment.event.title works! I can get the title.



    The question now is what have changed since TYPO3 8 and can not access these properties anymore and how can i regain access?



    In use: TYPO3 v9



    Mode: Composer



    Best regards,










    share|improve this question




























      0












      0








      0








      So i have a table which lists some appointments. These appointments belong to an event. The goal here is to list all the appointments and get the information of the event that they belong to.



      So far everything works fine until i try to get the information of the event. I get an object which looks like this:



      enter image description here



      Now if i use something like this : appointment.event.title it will give back NULL.



      That means that it doesnt access the properties. In TYPO3 v8 it works perfectly, but not in TYPO3 v9.



      If i activate the <f:debug>appointment</f:debug> and get the whole object as debugged, then this appointment.event.title works! I can get the title.



      The question now is what have changed since TYPO3 8 and can not access these properties anymore and how can i regain access?



      In use: TYPO3 v9



      Mode: Composer



      Best regards,










      share|improve this question
















      So i have a table which lists some appointments. These appointments belong to an event. The goal here is to list all the appointments and get the information of the event that they belong to.



      So far everything works fine until i try to get the information of the event. I get an object which looks like this:



      enter image description here



      Now if i use something like this : appointment.event.title it will give back NULL.



      That means that it doesnt access the properties. In TYPO3 v8 it works perfectly, but not in TYPO3 v9.



      If i activate the <f:debug>appointment</f:debug> and get the whole object as debugged, then this appointment.event.title works! I can get the title.



      The question now is what have changed since TYPO3 8 and can not access these properties anymore and how can i regain access?



      In use: TYPO3 v9



      Mode: Composer



      Best regards,







      object typo3 fluid typo3-8.x typo3-9.x






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 28 at 7:24







      Aristeidis Karavas

















      asked Mar 27 at 12:33









      Aristeidis KaravasAristeidis Karavas

      2332 silver badges14 bronze badges




      2332 silver badges14 bronze badges

























          2 Answers
          2






          active

          oldest

          votes


















          1














          Probably one of the following is true:



          1. You forgot to add a getter method for the property you try to access and you are confusing the output of f:debug with what is actually gettable from the object. The debug ViewHelper outputs also protected properties.

          2. You constructed the model object with __call or __get so you are affected by https://github.com/TYPO3/Fluid/pull/438 which is solved but not yet released (current Fluid version is 2.6.0, patch will be included in next version).

          You don't say which TYPO3 version you use, nor if you are using composer, so it's hard to tell if your versions of Fluid are the same - they should be, since both TYPO3 v8 and TYPO3 v9 use the same external Fluid library.



          The solution in either case is to add proper getter methods to your domain model object and always remember that the output of f:debug does not 100% correspond to what you can actually access: f:debug will for example not show virtual getter methods that don't have a property associated with it.






          share|improve this answer

























          • I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

            – Aristeidis Karavas
            Mar 28 at 7:26











          • If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

            – Claus Due
            Mar 28 at 10:30


















          1














          I found the solution to my problem.



          Thanks to @Claus Due i visited my Model to see if the getters und setters are there. They were there BUT before my getter, the @lazy parameter was present. After i removed, everything worked as it should.



          Thank you!






          share|improve this answer

























          • This seems bug of TYPO3 version 9

            – Mihir Bhatt
            Apr 4 at 12:18













          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%2f55377319%2ffluid-variables-do-not-read-the-child-values-anymore-typo3-9-5%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          Probably one of the following is true:



          1. You forgot to add a getter method for the property you try to access and you are confusing the output of f:debug with what is actually gettable from the object. The debug ViewHelper outputs also protected properties.

          2. You constructed the model object with __call or __get so you are affected by https://github.com/TYPO3/Fluid/pull/438 which is solved but not yet released (current Fluid version is 2.6.0, patch will be included in next version).

          You don't say which TYPO3 version you use, nor if you are using composer, so it's hard to tell if your versions of Fluid are the same - they should be, since both TYPO3 v8 and TYPO3 v9 use the same external Fluid library.



          The solution in either case is to add proper getter methods to your domain model object and always remember that the output of f:debug does not 100% correspond to what you can actually access: f:debug will for example not show virtual getter methods that don't have a property associated with it.






          share|improve this answer

























          • I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

            – Aristeidis Karavas
            Mar 28 at 7:26











          • If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

            – Claus Due
            Mar 28 at 10:30















          1














          Probably one of the following is true:



          1. You forgot to add a getter method for the property you try to access and you are confusing the output of f:debug with what is actually gettable from the object. The debug ViewHelper outputs also protected properties.

          2. You constructed the model object with __call or __get so you are affected by https://github.com/TYPO3/Fluid/pull/438 which is solved but not yet released (current Fluid version is 2.6.0, patch will be included in next version).

          You don't say which TYPO3 version you use, nor if you are using composer, so it's hard to tell if your versions of Fluid are the same - they should be, since both TYPO3 v8 and TYPO3 v9 use the same external Fluid library.



          The solution in either case is to add proper getter methods to your domain model object and always remember that the output of f:debug does not 100% correspond to what you can actually access: f:debug will for example not show virtual getter methods that don't have a property associated with it.






          share|improve this answer

























          • I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

            – Aristeidis Karavas
            Mar 28 at 7:26











          • If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

            – Claus Due
            Mar 28 at 10:30













          1












          1








          1







          Probably one of the following is true:



          1. You forgot to add a getter method for the property you try to access and you are confusing the output of f:debug with what is actually gettable from the object. The debug ViewHelper outputs also protected properties.

          2. You constructed the model object with __call or __get so you are affected by https://github.com/TYPO3/Fluid/pull/438 which is solved but not yet released (current Fluid version is 2.6.0, patch will be included in next version).

          You don't say which TYPO3 version you use, nor if you are using composer, so it's hard to tell if your versions of Fluid are the same - they should be, since both TYPO3 v8 and TYPO3 v9 use the same external Fluid library.



          The solution in either case is to add proper getter methods to your domain model object and always remember that the output of f:debug does not 100% correspond to what you can actually access: f:debug will for example not show virtual getter methods that don't have a property associated with it.






          share|improve this answer













          Probably one of the following is true:



          1. You forgot to add a getter method for the property you try to access and you are confusing the output of f:debug with what is actually gettable from the object. The debug ViewHelper outputs also protected properties.

          2. You constructed the model object with __call or __get so you are affected by https://github.com/TYPO3/Fluid/pull/438 which is solved but not yet released (current Fluid version is 2.6.0, patch will be included in next version).

          You don't say which TYPO3 version you use, nor if you are using composer, so it's hard to tell if your versions of Fluid are the same - they should be, since both TYPO3 v8 and TYPO3 v9 use the same external Fluid library.



          The solution in either case is to add proper getter methods to your domain model object and always remember that the output of f:debug does not 100% correspond to what you can actually access: f:debug will for example not show virtual getter methods that don't have a property associated with it.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 27 at 14:13









          Claus DueClaus Due

          3,3407 silver badges22 bronze badges




          3,3407 silver badges22 bronze badges















          • I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

            – Aristeidis Karavas
            Mar 28 at 7:26











          • If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

            – Claus Due
            Mar 28 at 10:30

















          • I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

            – Aristeidis Karavas
            Mar 28 at 7:26











          • If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

            – Claus Due
            Mar 28 at 10:30
















          I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

          – Aristeidis Karavas
          Mar 28 at 7:26





          I have an action which calls the event and gets all the information right. If i call the same object but through the appointment repository (appointment action ) i dont get them. My getters are there. But i can not access them

          – Aristeidis Karavas
          Mar 28 at 7:26













          If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

          – Claus Due
          Mar 28 at 10:30





          If you are also unable to access those properties in your controller action (PHP code) it is clearly a problem with the model. If it's different when you load the object from repository vs map it as controller argument, that clearly indicates a problem with the repository (perhaps an improperly overridden method, wrong Query preparation, etc.). But perhaps you can explain a bit more about the context. What is the source code of the model? Which version of v8 and v9 did you use? What else did you change (because you probably updated extensions, too?). And did you check that GitHub issue...?

          – Claus Due
          Mar 28 at 10:30













          1














          I found the solution to my problem.



          Thanks to @Claus Due i visited my Model to see if the getters und setters are there. They were there BUT before my getter, the @lazy parameter was present. After i removed, everything worked as it should.



          Thank you!






          share|improve this answer

























          • This seems bug of TYPO3 version 9

            – Mihir Bhatt
            Apr 4 at 12:18















          1














          I found the solution to my problem.



          Thanks to @Claus Due i visited my Model to see if the getters und setters are there. They were there BUT before my getter, the @lazy parameter was present. After i removed, everything worked as it should.



          Thank you!






          share|improve this answer

























          • This seems bug of TYPO3 version 9

            – Mihir Bhatt
            Apr 4 at 12:18













          1












          1








          1







          I found the solution to my problem.



          Thanks to @Claus Due i visited my Model to see if the getters und setters are there. They were there BUT before my getter, the @lazy parameter was present. After i removed, everything worked as it should.



          Thank you!






          share|improve this answer













          I found the solution to my problem.



          Thanks to @Claus Due i visited my Model to see if the getters und setters are there. They were there BUT before my getter, the @lazy parameter was present. After i removed, everything worked as it should.



          Thank you!







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 2 at 13:53









          Aristeidis KaravasAristeidis Karavas

          2332 silver badges14 bronze badges




          2332 silver badges14 bronze badges















          • This seems bug of TYPO3 version 9

            – Mihir Bhatt
            Apr 4 at 12:18

















          • This seems bug of TYPO3 version 9

            – Mihir Bhatt
            Apr 4 at 12:18
















          This seems bug of TYPO3 version 9

          – Mihir Bhatt
          Apr 4 at 12:18





          This seems bug of TYPO3 version 9

          – Mihir Bhatt
          Apr 4 at 12:18

















          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%2f55377319%2ffluid-variables-do-not-read-the-child-values-anymore-typo3-9-5%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

          Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

          SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

          은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현