Databases
StackOverflow2013
Postsdbo
POtypo3 migration to new server not working
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POtypo3 migration to new server not working
    primarykey
    data
    text
    <p>I trying to move a typo3 website to a new server.I moved all the files across and created a new database and imported all the tables from the old database. I then updated the localconf.php file with the new database settings. However, I'm now getting a series of fatal errors which seem to be because the paths in the typo3 old website used a mixture of uppercase and lowercase letters, but on the new server all the files and folders are lowercase, and it is throwing an error whenever an internal path is using uppercase letters because it can't find the path or file.I don't know if this is particular to 1&amp;1 who are my hosts.</p> <p>Is there an easy way to fix this or do I have to go through all the internal code to change all the paths to lowercase? Which seems a little unrealistic. I was hoping I'd be able to transfer the website over in a few hours, but so far have spent about a day on it. I also do not know typo3 at all, this is my first time with it. Though I am experienced in setting up Drupal and Joomla websites and thought it wouldn't be so different.</p> <p>Any advice would be much appreciated.</p> <p>Ben</p> <p>EDIT - Additional information: </p> <p>The error message I'm getting is: </p> <p>Fatal error: require_once() [function.require]: Failed opening required '/htdocs/vincent/typo3conf/ext/formhandler/Resources/PHP/Hooks/class.tx_formhandler_stdwrap.php' (include_path='.:/usr/lib/php5') in /htdocs/vincent/t3lib/class.t3lib_div.php on line 5046</p> <p>The line 5046 is the last line of code below. I don't know which path is being referred to in the $requireFile variable.</p> <pre><code> /** * Require a class for TYPO3 * Useful to require classes from inside other classes (not global scope). A limited set of global variables are available (see function) */ public static function requireOnce($requireFile) { global $T3_SERVICES, $T3_VAR, $TYPO3_CONF_VARS; require_once ($requireFile); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBen
    1. USBen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI would first start with not making all file-names lowercase. It sounds as if you didn't either migrate to the same operating system or you didn't preserve the data. But this does not sound like a programming question. And please share the exact error messages and show some code where the error appears so it's more clear what this is about.
      singulars
      1. POtypo3 migration to new server not working
      1. UShakre
    2. COwhat kind of errors? Which path? fileadmin/somefolder/somefile.txt or link to a webpage? I guess its an server issue, never had such an problem. You cleared cache? removed cached files?
      singulars
      1. POtypo3 migration to new server not working
      1. USmaholtz
    3. COMany thanks for your replies. I've added additional information about the error above.
      singulars
      1. POtypo3 migration to new server not working
      1. USBen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload