Closed (works as designed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
tracker.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Dec 2013 at 17:01 UTC
Updated:
17 Feb 2015 at 04:28 UTC
Jump to comment: Most recent
Comments
Comment #1
tim.plunkettI cannot reproduce. Can you provide step by step instructions?
Comment #2
Blooniverse commentedTim, the error happens straight after enabling the module. But -- as I have found out in the meantime -- not only after enabling this particular module.
It happens too after changing a node type and wanting to display an old/existing content of this [changed] node type. E.g. this was the case after deleting a taxonomy reference field and adding a new one. My intuition is telling me, vaguely, that this has something to do with content translation, since I've had a lot of errors in the last days in relation to it.
Comment #3
tim.plunkettYou didn't mention content_translation before.
Without step-by-step instructions, starting with a fresh install, this will be impossible to reproduce.
Comment #4
Blooniverse commentedAye, it is a very rudimentary issue explanation, I admit.
Well, in the meantime I get the error as well after flushing the caches (all). Let me perform some tests with a fresh D8 installation, maybe I can narrow down or even identify the cause of this nasty, nasty, nasty thing.
Comment #5
Blooniverse commentedOkäy: I've tested all imaginable possibilities with a new D8 installation, but I couldn't reproduce the error either! However, as soon as I translate a field the horrors start in uncountable ways (various errors, complete site crash).
I am quite sure that this error is actually one of the component Language System, but I cannot directly proof it yet.
Comment #6
Blooniverse commentedTagging with language-config.
Comment #7
larowlanI don't see a repeating pattern in that trace can you disable xdebug and see if the page renders fine. If it does, you need to update your xdebug settings
Comment #8
Blooniverse commentedChanging the title.
Still get the error. Will provide more in-depth insight from testing later.
Comment #9
berdirThis is a xdebug specific setting, which defaults to 100. This can be too low, also on big 7.x sites. I don't think there's anything we can do.
Comment #10
jhedstromI've been seeing this a lot on osx. Usually an apache restart fixes it. Bumping the xdebug nesting level to 200 definitely fixes it. In
xdebug.ini:Comment #11
elijah lynnComment #12
sutharsan commentedI ran into this with a clean install (standard install profile) when adding a node (/node/add/article).
I can confirm Berdir's (#9) and jhedstrom's (#10) comments that it is due to an xdebug setting. Raising 'xdebug.max_nesting_level ' to 250 and restarting apache fixed it for me.
Comment #13
sutharsan commentedI take the liberty to close the issue, as the solutions all point in the same direction.
@the_phi, if you feel this issue is not closed to you, feel free to re-open.
Comment #14
Mark_L6n commentedThanks for the info. I corrected this using the
.htaccessfile. In the section:add:
php_value xdebug.max_nesting_level 200