« Previous | Next » 

Revision ad3e1668

IDad3e166852129266033a4a53eaf486392fe4a8bc

Added by Robert Lemke about 11 years ago

[~TASK] FLOW3 (MVC): Don't log non-matching link resolves

If a link configuration could not be resolved into a fitting route,
this was logged to the system log, including the "routeValues" which
could not be resolved. If a route value is an object though, it could
easily happen that the var_export call tries to export FLOW3's whole
object structure recursively.

Therefore we don't log this anymore - because without the route values
it doesn't make sense anyway.

Change-Id: I0d2e3bd05e0303ff8e02097cd8161834d158584b

  • added
  • modified
  • copied
  • renamed
  • deleted