Bug #38232
TYPO3 in subdirectory no more supported
| Status: | Closed | Start date: | 2012-06-20 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Karl-Heinz Dahlmann | % Done: | 100% |
|
| Category: | Bug | Spent time: | - | |
| Target version: | 3.0 | |||
| TYPO3 Version: | PHP Version: | |||
| Votes: | 0 |
Description
I tested it with newest version 3.0.1 of direct_mail. When TYPO3 is installed in a subdirectory, the path to ressources (mostly images, maybe same with other ressources) is wrong. direct_mail does not find images because they are expected in
http://www.domain.com/typo3temp
while TYPO3 is installed in
http://www.domain.com/subdirectory/
and images are generated in
http://www.domain.com/subdirectory/typo3temp
Same with uploads directory, maybe same with fileadmin.
A symbolic link in the root directory is a possible workaround
(e.g. ln -s subdirectory/typo3temp/ typo3temp)
but not in all cases (if you want to install / test different versions of TYPO3 on one server or if you can not install in the root directory for other reasons.
direct_mail with TYPO3 in a subdirectory worked without problems in earlier versions like 2.7 and of course all other extensions (which have been tested ;-) ) work either with TYPO3 in a subdirectory.
Associated revisions
- Bug #38232: fixed fetching included media from the wrong FE path
- Bug #38232: fixed fetching included media from the wrong FE path
git-svn-id: https://svn.typo3.org/TYPO3v4/Extensions/direct_mail/trunk@64254 735d13b6-9817-0410-8766-e36946ffe9aa
History
Updated by Karl-Heinz Dahlmann 11 months ago
- Assignee deleted (
Karl-Heinz Dahlmann)
Updated by Karl-Heinz Dahlmann 11 months ago
Btw, tried to use
config.baseURL=... and
plugin.tx_directmail_pi1.siteUrl=...
but does not help.
Updated by Ivan Dharma Kartolo 11 months ago
are you saying, if your installation is in a subfolder, the fetched mail doesn't have images in it? are you sending the images as inline media in the main?
Updated by Karl-Heinz Dahlmann 11 months ago
no, it is not just the generated email.
the extension breaks with error page
Oops, an error occurred!
Unable to open file for reading [http://www.domain.com/uploads/pics/image.png]
(which has to be http://www.domain.com/subdirectory/uploads/pics/image.png)
In the newsletter generation wizard this error is shown when going to step 4 and send a test email (which is not send but error page displayed through generating email I think).
At this point the image is created correctly for example in the subdirectory/uploads directory but the extension try to find it in the uploads directory in root webserver directory and fails.
When I do not send a test email the same error is shown when manually starting to send the newsletter.
I use option images include in html. If I use the option show html format during step 1 of wizard the corresponding page is shown correctly with the image.
Updated by Ivan Dharma Kartolo 11 months ago
- Status changed from New to Needs Feedback
- Assignee set to Karl-Heinz Dahlmann
- % Done changed from 0 to 100
fixed in svn r64254. Please check this version.
Updated by Ivan Dharma Kartolo 10 months ago
- Status changed from Needs Feedback to Closed
please check latest release 3.0.2 from TER