Project

General

Profile

Actions

Bug #78490

closed

file_get_contents fail prevents page tree to render

Added by Peter Kraume about 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2016-10-28
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

This bug report was sent to by an anonymous person:

I have no Forge account and do not want to register, but since 8.4 (up to current master) I am getting the folliwng error in the backend:

Core: Error handler (BE): PHP Warning: file_get_contents(/var/www/test/typo3//test/typo3/sysext/backend/Resources/Public/JavaScript/extjs/components/pagetree/javascript/app.js): failed to open stream: No such file or directory in /var/www/test/typo3_src/typo3/sysext/core/Classes/Resource/ResourceCompressor.php line 285

This prevents the page tree from rendering because all the Javascript from loadorder.txt is missing.

The problem seems to be that an relativ path is concatenated to a absolute path. Probably related to making "EXT:" available in Backend modules.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Task #78193: Deprecate ExtensionManagementUtility::extRelPath()ClosedBenni Mack2016-10-08

Actions
Related to TYPO3 Core - Bug #78803: ResourceCompressor can't deal with paths relative to docrootClosedMarkus Klein2016-11-25

Actions
Actions #1

Updated by Nicole Cordes about 8 years ago

  • Status changed from New to Needs Feedback

Hi Peter,

Thank you for the bug report. Is there any way to get in contact with the author? There seems to be a problem with his/her folder structure and unless there are more information I fear there is nothing we can do to solve this issue. I had a look at there code there and it seems to work properly so far (for me).

Actions #2

Updated by Peter Kraume about 8 years ago

Hi Nicole, unfortunately there is no contact information available.

Actions #3

Updated by Malte Koitka about 8 years ago

Hey there, we're having the exact same problem. What I found out so far is that it is triggered due to TYPO3 8.4 being installed in a subdirectory e.g. dev.local/my-site/typo3

As reported some calculated filenames contain a redundant relative part thus cannot be found by the ResourceCompressor. Also, in the Install Tool the configuration preset "Live" has to be enabled. With "Debug" mode active the page tree strangely renders perfectly fine.

Actions #4

Updated by Nicole Cordes about 8 years ago

Malte Koitka wrote:

Hey there, we're having the exact same problem. What I found out so far is that it is triggered due to TYPO3 8.4 being installed in a subdirectory e.g. dev.local/my-site/typo3

Do you mean subdirectory (on hard drive) or do you refer to your domain?

Actions #5

Updated by Nicole Cordes about 8 years ago

  • Status changed from Needs Feedback to Accepted
  • Assignee set to Nicole Cordes

Hi Malte,

Thank you for the feedback. I'm finally able to reproduce this error and try to find the problem!

Actions #6

Updated by Malte Koitka about 8 years ago

Hi Nicole. Great, thanks for your effort!

Actions #7

Updated by Gerrit Code Review about 8 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/50475

Actions #8

Updated by Nicole Cordes about 8 years ago

Steps how to be able to reproduce the problem:

1. install TYPO3 sources within an existing document root (I used folder "t3" under localhost document root)
2. install TYPO3 using the existing domain + folder (in my case localhost/t3/)
3. go to install tool and make sure "live" preset is set
4. remove typo3temp/assets/compressed folder (just to be sure)
5. go to the page module

Expected result:

You should see an empty page tree

Actual result:
Nothing in the page tree frame is shown

Actions #9

Updated by Nicole Cordes about 8 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #10

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF