migrating TYPO3 6.2.31 to TYPO3 7.6.23

2
votes

When I try to migrate my TYPO3 6.2.31 to 7.6.23 I've got some problems.

Especially the page tree is missing so I got this error

The requested resource "%2Fmain" was not found

I've tried this way to migrate:

1.) Copy the whole page

2.) Changing the symlinks to the new sources

3.) Starting the migration wizard in install tool

And now When I want to access the backend I got the above mentioned error.

what can I do?

thanks.

When I call url.de/typo3 the follwing url is called:

index.php?route=%252Fmain&token=XXX

The correct one should be

index.php?route=%2Fmain&token=XXX

What could be the problem in the url?

2
typo3typo3-6.2.xtypo3-7.6.x
Try deleting caches via installtool (or hole typo3temp). Did seen the same in TYPO3 8.7, which helped in this case. Sometimes OPcode/APC can be the issue, if you change symlinks. – jokumer
Yes I already have cleared all cache. In the error massage the following hint is linked: wiki.typo3.org/Exception/CMS/1425389240 – Felix
but this does not work in my context because I cannot import anything... only the error message is shown – Felix
Did you followed Check for broken extensions from installTool? – Ravi Sachaniya
yes no problems – Felix

2 Answers

1
votes

Please follow below steps.

  1. Download typo3 7 LTS latest source and create symlink.
  2. Add your typo3conf, uploads and fileadmin folder
  3. Open install tools and clear both cache php and typo3.
  4. Compare currentdatabse specification and perform all steps.
  5. Go to upgrade wizard and complete all needed steps
  6. Clear cache and remove typo3temp file and open BE
1
votes

as mentioned here: Need to allow encoded slashes on Apache

Issue 1: Apache believes that's an invalid url

Solution: AllowEncodedSlashes On in httpd.conf

Issue 2: Apache decodes the encoded slashes

Solution: AllowEncodedSlashes NoDecode in httpd.conf (Requires Apache 2.3.12+)

Issue 3: mod_proxy attempts to re-encode (double encode) the URL changing %2F to 

%252F (eg. /example/http:%252F%252Fwww.someurl.com/)

Solution: In httpd.conf use the ProxyPass keyword nocanon to pass the raw URL thru the proxy.

ProxyPass http://anotherserver:8080/example/ nocanon

httpd.conf file:

AllowEncodedSlashes NoDecode

<Location /example/>
  ProxyPass http://anotherserver:8080/example/ nocanon
</Location>