Closed (duplicate)
Project:
Redirect
Version:
8.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Oct 2017 at 10:25 UTC
Updated:
3 Nov 2017 at 15:18 UTC
Jump to comment: Most recent
Comments
Comment #2
gmaxwelled commentedRe-saving the redirect as a 307 seems to resolve the issue. I still get the problem with 301s.
Comment #3
paulkittredge commentedFor what it's worth, I've turned off page caching (not an ideal long-term solution) and that seems to fix it. But I'd love to see a fix too! Note that this only seems to be a problem on Drupal 8.4 sites; I have a Drupal 8.3.7 site where I can't replicate this problem.
Comment #4
danthorneChanging the redirect to a 307 got around it for me.
Comment #5
0xl337 commentedIt's happening to me too. Since the migration to 8.4.0, I have the same 500 Error.
Comment #6
wim leersComment #7
wim leersComment #8
darkstartom commentedI'm getting the same error after upgrading to Drupal 8.4. I wasn't getting it on 8.3.4.
Comment #9
freelockSame as DarkstarTom -- after upgrading to 8.4, we started seeing this on some pages with an active redirect. The latest patch on #2573807 fixed the issue for us -- patch applied with an offset of 25 lines.
Comment #10
robertoguzman commentedHi freelock, would you like to provide the link to patch #2573807
Thank you
Comment #11
wim leers#2573807: Fatal error: Call to a member function getTimestamp() was just committed to Drupal core 8.4 and 8.5!
Comment #12
Christophe Bourgois commentedUpdate to Drupal core 8.4.2 worked for me, the patch #2573807 in included
Thanks !