Results 1 to 9 of 9

Thread: problem with the install tool 3.2.x

  1. #1
    New user
    Join Date
    02-11-14.
    Posts
    4

    Default problem with the install tool 3.2.x

    Hi there, I want to report a problem with the Contao install tool in the Core 3.2.x.
    I have done 6 different Installations of Contao (3.0.6 to 3.1.5) in the last 9 months after I read a Contao book and carefully understood the basic database issues, never had a single problem up to now. I have also read the similar recent posts regarding installation issues.
    Since I would like to use the new Isotope and I need 3.2 for my sites, I would wish this is fixed relatively fast, thanks for your help in this...!
    (I am not a specialist, but can understand the basics well.)

    Before writing this post, I tried 2 installations (3.2.3 and 3.2.5) from scratch with no success, read all recent posts in the forum and I finally installed 3.1.5 just now, without any problems. Therefore, I am pretty sure the problem is somewhere in the new install tool.

    What happens: after copying all files of the Contao core 3.2.5 on the server, I start the install tool and it starts without problems. The problem comes on clicking "update database". There, after waiting for about 20 seconds, I get a completely white screen (every single time). When I reload the tool (after restarting Safari or Firefox, I have tried everything on my side), I have to log-in again. The result is always the same white screen, no error reports, nothing. This thing happened exactly the same way with a completely new installation. Of course I have used the Contao Check before and after, it found absolutely no problems with the server or the installation. Checking the database on the server side: all tables created, no problems (collation also OK). I have also tried optimisation and repair database (on the server): nothing helps.

  2. #2
    Community-Moderator xchs's Avatar
    Join Date
    06-19-09.
    Posts
    1,287

    Default

    What are the server limits (PHP memory_limit and max_execution_time)?

    Do you have already checked the log files ("system/logs" and the web server log file) ?
    Last edited by xchs; 02/11/2014 at 15:47.
    Contao Community Moderator
    → Support options

  3. #3
    New user
    Join Date
    02-11-14.
    Posts
    4

    Default

    Quote Originally Posted by xchs View Post
    What are the server limits (PHP memory_limit and max_execution_time)?

    Do you have already checked the log files ("system/logs" and the web server log file) ?

    Thanks for your reply!
    I am afraid I cannot respond to such technical questions with ease... Where do I normally find the memory_limit and max_execution_time? Should I ask the provider? (one.com)

    I haven't checked the log files of the Contao installation (now they are gone). I have the web server log file of course. What I am I looking for?

    I am currently running 3.1.5 without problems and I have to build this site in the next days. So, I am thinking on updating later, but I suppose I will then run into the same problem as soon as I hit "update database" in the install tool.

  4. #4
    Community-Moderator xchs's Avatar
    Join Date
    06-19-09.
    Posts
    1,287

    Default

    Quote Originally Posted by periklis View Post
    Where do I normally find the memory_limit and max_execution_time? Should I ask the provider? (one.com)
    Never mind! You can – of course – ask your provider, but you can also get this kind of information by calling the phpinfo() function. Just download the archive from here, extract the script "phpinfo.php" to the root of your Contao installation and run it in your web browser by calling http://www.example.com/phpinfo.php You should then get as output a long list with the PHP configuration and there you'll find the settings for memory_limit and max_execution_time.

    Quote Originally Posted by periklis View Post
    I have the web server log file of course. What I am I looking for?
    It was meant the error log file (error_log or something like that). When you get a blank page after some time the Apache web server should log the issue (with all the relevant information and hopefully the reason for the problem) in the mentioned error log file.

    Quote Originally Posted by periklis View Post
    I am currently running 3.1.5 without problems and I have to build this site in the next days. So, I am thinking on updating later, but I suppose I will then run into the same problem as soon as I hit "update database" in the install tool.
    Yes, that could be. I suspect that the PHP execution time is too short to perform all the database statements within the specified time. Therefore, the web server terminates the script execution after a specific time.
    Contao Community Moderator
    → Support options

  5. #5
    New user
    Join Date
    07-15-09.
    Posts
    12

    Default

    I'm having the same issues with Fasthosts that one of my clients is with.

    database update refuses to work and kicks the page back with "The connection was interrupted." on the server but does work locally.
    I don't know if the server has changed or something else.

    Contao v3.2.7
    max_execution_time 60
    memory_limit 64M

  6. #6
    New user
    Join Date
    02-11-14.
    Posts
    4

    Default

    Quote Originally Posted by xchs View Post
    Never mind! You can – of course – ask your provider, but you can also get this kind of information by calling the phpinfo() function. Just download the archive from here, extract the script "phpinfo.php" to the root of your Contao installation and run it in your web browser by calling http://www.example.com/phpinfo.php You should then get as output a long list with the PHP configuration and there you'll find the settings for memory_limit and max_execution_time.
    Thanks! Here is the info:
    memory_limit 128M
    max_execution_time 50
    Last edited by xchs; 03/05/2014 at 16:38.

  7. #7
    Community-Moderator xchs's Avatar
    Join Date
    06-19-09.
    Posts
    1,287

    Default

    Quote Originally Posted by periklis View Post
    Here is the info:
    memory_limit 128M
    max_execution_time 50
    Actually, the given server limits should be enough to process the SQL statements. Therefore, you must look at the server error log files to identify the real problem.
    Contao Community Moderator
    → Support options

  8. #8
    New user
    Join Date
    02-11-14.
    Posts
    4

    Default

    Quote Originally Posted by xchs View Post
    Actually, the given server limits should be enough to process the SQL statements. Therefore, you must look at the server error log files to identify the real problem.
    I do not seem to have any error log files (PHP error log was deactivated on the server, the logs I have are "access" logs).
    But, I communicated with the hosting service and I got the following message:

    Contao 3.2.x is still supported according to the Contao Check. Though, an error (timeout) occurs when installing this CMS. More precisely, a blank page is displayed when logging into the Contao install tool.

    How to fix it?
    You can fix it by importing the tables (of the CMS and the template) in the database manually.

    1. You first have to search for these data:
    -CMS tables: /contao/system/modules/repository/config/database.sql
    -Template tables: /contao/templates/music_academy.sql

    2. Import them in your database manually via phpMyAdmin

    etc.

    So, is there a way of installing the empty database of 3.2.x without the install tool? (the .sql file in the folder as they describe it is not to be imported with phpMyAdmin...)
    I also need to install a template after the installation is finished. (Swissy)

  9. #9
    Community-Moderator xchs's Avatar
    Join Date
    06-19-09.
    Posts
    1,287

    Default

    You may want to try to install Contao step-by-step, i.e.
    • set up a new fresh Contao 3.2.7 installation
    • go to "system/modules" and rename the subdirectories
      • "calendar" to ".calendar"
      • "comments" to ".comments"
      • "devtools" to ".devtools"
      • "faq" to ".faq"
      • "listing" to ".listing"
      • "news" to ".news"
      • "newsletter" to ".newsletter"
      • "repository" to ".repository"
    • then, run the Contao install tool and try to update the database (at this point only the "core" SQL statements will be processed)
    • if that works without any errors, rename the previously renamed folders back to the original directory name, i.e. ".calendar" to "calendar", ".comments" to "comments" etc. To be safe, rename only one folder at a time and after that run again each time the Contao install tool to update the new SQL statements for the respective back end module.
    • do this for all the module folders until the database is up to date
    Contao Community Moderator
    → Support options

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •