Marcel Stäheli Posted May 29, 2017 Share Posted May 29, 2017 Hello there I recently updated a website running PW 2.6.1 to PW 2.8.35. I followed the instructions and everything went fine. The website is being displayed as it should. However if I try to edit the home-page (ID=1) I get this error: Error: Call to a member function getInputfield() on null (line 204 of C:\inetpub\wwwroot\www.globalsystem.ch\wire\modules\Fieldtype\FieldtypeRepeater\InputfieldRepeater.module) the code in the file on that line is: /** * Determine if the request is one we should handle (internal) or one that another * script coming after this (external) will handle. * */ $internal = isset($_SERVER['HTTP_HOST']) && realpath(__FILE__) == realpath($_SERVER['SCRIPT_FILENAME']); if(!$internal) register_shutdown_function('ProcessWireExternalShutdown'); The site is running on IIS8. There is another page that uses a (diffrent) repeater field and it can be edited just fine. Is the error cause because the repeater is on the home-page? Any idea how to fix it? Link to comment Share on other sites More sharing options...
Robin S Posted May 29, 2017 Share Posted May 29, 2017 I'm not sure about this error, but just a correction to the code that is triggering it - line 204 in PW 2.8.35 is: $inputfield = $field->getInputfield($this->page); The legacy branch has been updated to 2.8.62 (despite what is says on the "Download" page) and the code in InputfieldRepeater.module has changed in this version. So you could try updating to 2.8.62 and see if that resolves the issue. 1 Link to comment Share on other sites More sharing options...
Marcel Stäheli Posted May 30, 2017 Author Share Posted May 30, 2017 Thanks for your correction, I did not notice. I updated the site to PW 2.8.62 but the error persists, it is on line 222 now though. Link to comment Share on other sites More sharing options...
Marcel Stäheli Posted May 31, 2017 Author Share Posted May 31, 2017 The problem was with that particular repeater field. It caused an error in the backend no matter on what page I tried to use it. I recreated the repeater-field with a new name using the same fields as before and populated it with the same content as before. Now it works. No idea what caused that error, I didn't find anything suspicious in the settings of that repeater field. 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now