Project

General

Profile

Actions
Copy link

Bug #14347

closed

absolute path for [FE][logfile_dir] don't work

Added by Schmid Valentin about 20 years ago. Updated over 18 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Michael Stucki
Category:
Frontend
Target version:
-
Start date:
2004-10-05
Due date:
% Done:

0%

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

Description

We tried to set an absolute path for [FE][logfile_dir] in Version 3.7.0
(because we want the logfile on the /var partition). Unfortunately
it didn't work. After some debugging we recognised that
[BE][lockRootPath] must also be set to the same absolute path
(because of a t3lib_div::isAllowedAbsPath check).

Was this really the intention? I thought [BE][lockRootPath]
stands for absolute another thing.

If it was the intention, please document it in the [FE][logfile_dir]-paragraph
of the 1-2-3 tool.

Thanks, valli

(issue imported from #M405)

Actions
Copy link
 #1

Updated by Michael Stucki about 20 years ago

The description of [BE][lockRootPath] says:

"[...] This path is also used to evaluate if paths outside the PATH_site should be allowed."

I think this is ok, isn't it?

I close the bug but if you think it's not ok, just reopen it.

Actions
Copy link
 #2

Updated by Michael Stucki about 20 years ago

I have now changed the description of $TYPO3_CONVF_VARS[FE][logfile_dir]:
"Path where TYPO3 should write webserver-style logfiles to. This path must be write-enabled for the webserver. If this path is outside the PATH_site, you have to allow it using [BE][lockRootPath]"

Actions
Copy link

Also available in: Atom PDF