Project

General

Profile

Actions

Bug #44205

closed

Exception: #1343589451: Could not fetch page data for uid XXX, where XXX - id missing pages

Added by Anton almost 12 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-12-23
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.0
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Administration log:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1343589451: Could not fetch page data for uid 1234. | RuntimeException thrown in file /usr/local/src/typo3_src-6.0.0/typo3/sysext/core/Classes/Utility/RootlineUtility.php in line 211. Requested URL: http://www.domain.com/index.php?id=1234

where:
1234 - id missing pages


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #44454: pageNotFound_handling never happensClosed2013-01-11

Actions
Actions #1

Updated by Oliver Hader almost 12 years ago

  • Status changed from New to Needs Feedback

Can you please give a step-by-step example on how to reproduce this behaviour on your side?
What's the type of that page (shortcut, regular page, recycler, ...) and are you using workspaces or a localized pages when this error is being shown?

Actions #2

Updated by Anton almost 12 years ago

Configuration: TYPO3 6.0.0, realurl 1.12.3, realurlautoconf 2.0.0

Main objective: to redirect erroneous links to static error.html (with HTTP 404 Not found)

[FE][pageNotFound_handling] = /errors/404.html
[FE][pageNotFound_handling_statheader] = HTTP/1.0 404 Not Found
[HTTP][ssl_verify_host] = 1
[HTTP][ssl_local_cert] = /etc/ssl/cert/main.site.crt
[BE][lockSSL] = 0

case 1:
request: http://www.example.com/index.php?id=1
response: HTTP 200, http://www.example.com/index.php?id=1 - Ok

case 2:
request: http://www.example.com/qwerty/
response: HTTP 404, http://www.example.com/errors/404.html - Ok

case 3:
request: http://www.example.com/index.php?id=124
response: HTTP 500, http://www.example.com/index.php?id=124 (Could not fetch page data for uid 124.)
Log: Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1343589451: Could not fetch page data for uid 124. | RuntimeException thrown in file /usr/local/src/typo3_src-6.0.0/typo3/sysext/core/Classes/Utility/RootlineUtility.php in line 211. Requested URL: https://www.example.com/index.php?id=124

but the page with id 124 does not exist and must be forwarded to HTTP 404

Actions #3

Updated by Anton almost 12 years ago

... and Workspaces Management extension is not installed, Localization is not used.

Actions #4

Updated by Marcin Sągol almost 12 years ago

When testing latest TYPO3 6 git version i have similiar error but only in the backend :

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1343589451: Could not fetch page data for uid 0. | RuntimeException thrown in file [MY_PATH]/typo3/sysext/core/Classes/Utility/RootlineUtility.php in line 211. Requested URL: http://domain.com/typo3/backend.php

Actions #5

Updated by Vincent Mans almost 12 years ago

I confirm this error as Anton describes it.

Priority must be elevated to "Must have".

Problem: if a website is changed (I took one over) the page ids change. In Google the old links still exist for a while. Visitors get to the page "Oops, an error occurred!"

You understand, this is a major issue.

The only option to bypass this issue is putting the most important links as they exist in the Google index, in the htaccess with a 301.

Actions #6

Updated by Constantin Iliescu over 11 years ago

The error appears in frontend when I'm logged in in backend on the same browser.

Typo3 6.0.2 upgraded from 4.2 -> 4.5 -> 4.7
PHP 5.4.12

Activating / deactivating SimulateStatic does not make any difference.

Actions #7

Updated by Tilo Baller over 11 years ago

As for the original problem, there is a fix out now here:
http://forge.typo3.org/issues/44454

@Marcin Sągol: You problem seems to have another cause. I would recommend to search this bugtracker and google for "Could not fetch page data for uid 0." as there are already some posts out there. If you are still not able to get it working please open a new issue.

@Moderator: I would recommend to close this issue while it duplicates the mentioned issue which is already under review.

Actions #8

Updated by Michael Stucki over 11 years ago

  • Status changed from Needs Feedback to Resolved

Thanks Tilo, closing this issue. Please follow up to #44454.

Actions #9

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF