xweb Posted February 13, 2014 Share Posted February 13, 2014 I'm using the latest development version of Processwire with a simple template (see attached tplProduct.png). The only thing that is somehow more complicated is the Categorias field that is of type Page, with details "Single page (Page) or empty page (NullPage) when none selected" and the Input Field is of type PageListSelectMultiple. Now this is for a Product Catalog where I have the Categories on a branch of the tree and use them as a field in the Product page. I create this all using a script that does a CSV import and everything works fine here. When I try to make a change in the backoffice I get warning and in the end a fatal error :-( First: Notice: Trying to get property of non-object in /home/vagrant/public_html/mp/wire/core/Page.php on line 318 Second: Warning: Invalid argument supplied for foreach() in /home/vagrant/public_html/mp/wire/core/Page.php on line 318 Last: Fatal error: Maximum function nesting level of '100' reached, aborting! in /home/vagrant/public_html/mp/wire/core/Field.php on line 386 Could someone shed some light here? What stupid error is it that I'm doing, that I can't find out? Thanks Adelino Link to comment Share on other sites More sharing options...
Martijn Geerts Posted February 13, 2014 Share Posted February 13, 2014 First one we can't tell without details 2nd: google this: site:processwire.com Maximum function nesting level of '100' 1 Link to comment Share on other sites More sharing options...
xweb Posted February 13, 2014 Author Share Posted February 13, 2014 Ok... I deserved that reply Thanks ! Link to comment Share on other sites More sharing options...
ryan Posted February 16, 2014 Share Posted February 16, 2014 Line 318 seems to imply that the page being accessed didn't yet have a template assigned to it. That sounds like a core error rather than a user one, so I'd be curious about how to duplicate that–maybe a potential bug. But if it was accompanied by a nesting level issue (via xdebug), and correcting the xdebug setting also corrected the issue, then I wouldn't worry about it. Are you still getting the Page.php line 318 error? Link to comment Share on other sites More sharing options...
xweb Posted February 16, 2014 Author Share Posted February 16, 2014 I'd never thought that xdebug could be the issue here and therefore didn't even tried to search for it. Making the change suggested in one of the post about xdebug solved this issue. Sorry for the false alarm. 1 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