I have to learn how to use TYPO3 for an end-of-study internship. I use the last version of TYPO3.
And I want to use the local server Xampp on Windows 10. But I never used it before and I don't know how to configure it for TYPO3. I try to use the documentation on TYPO3's website but I don't really understand.
Could you help me ?
The first three messages can be resolved by changing the entries in the „php.ini“ file with an editor.
1);extension=php_soap.dll will be activated by removing the semicolon
2) max_execution_time = 30 has to be increased to 240
3) ; max_input_vars = 1000 will be activated by removing the semicolon and has to be increased to 1500 characters
Now restart Apache and MySQL with the XAMPP Control Panel and reload the website.
The „ThreadStackSize“ has to be raised to 8MB. In order to change this setup write the following lines with a text editor in the file „httpd.conf“:
<IfModule mpm_winnt_module>
ThreadStackSize 8388608
</ IfModule>
The last error „PHP OpenSSL extension not working“ can be ignored, since it’s just a local test system. So security is not that important in this case.
This information and more you can find here: https://www.pagemachine.de/blog/install-typo3-8-0-local-test-system-windows-tutorial/
Related
I use xampp for half a year now, with xdebug and some other extensions. Everything is fine but now, over the weekend it magically went horrible slow. Does not matter if i enter "localhost", "127.0.0.1" or my LAN-IP.
So i installed WAMP. As i know now, WAMP for x64 is a waste of time - (CURL not working) so i installed WAMP x32.
CURL is working so far but the page still takes over a minute to load! Not building the page, not processing the code, to me it looks hardly like it takes a minute to start processing.
Sadly, can anyone recommend a fully working php-apache-mysql bundle for windows that is working as expected with all provided extensions in 2014?? Would be nice if that package/software (if it exists) would work as expected without need to modify registry, systemfiles, dll's and without spending hours and hours to get a simple page-request working.
Last but not least, the content of my host-file:
#::1 localhost
127.0.0.1 localhost
127.0.0.1 127.0.0.1
I tried really everything i found on the web so far. Nothing helps. Theres a similar question to this on Stackoverflow - without any useful (fixing) answer.
Collective Information:
XAMPP and WAMPP are slow
localhost/127.0.0.1/LAN-IP in URL does not
affect performance
the webserver does not take long to perform
requests
the websever does need about 60 seconds to recieve a request
cross-browser tested
with killed session tested
You could try removing the line
127.0.0.1 127.0.0.1
from your HOSTS file.
It is an illegal instruction anyway, but I have know it to cause loops. Does you PHP error file or Apache error file tell you anything useful?
Was this something you added, just before the system slowed down?
ADDITIONAL SUGGESTION:
Also changing these settings has been known to help on Windows systems, you may need to add then to your httpd.conf if they dont already exist.
AcceptFilter http none
AcceptFilter https none
In wamp php.ini turn off displaying errors and change type of displaying errors! :)
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT
display_errors = Off
enter php.ini via wamp
edit these lines
Enable gzip
a) enable apache modules: deflate_module and headers_module
b) than paste code below to ur main wordpress folder .htaccess
<IfModule mod_deflate.c>
<FilesMatch "\.(html|php|txt|xml|js|css)$">
SetOutputFilter DEFLATE
</FilesMatch>
</IfModule>
Ok I got Drupal 7.19, mySQL 5.1.66-cll PHP 5.3.21
Now I searched for he above error and found various answers of various age, however it doesn't address, my problem.
I get the error for any file bigger than 100k
went through php.ini settings.php as well as account settings, which is now 5000k.
and max post and max file are way higher.
The site has only 2 image fields, the original as well as one other. It doesn't matter which one is used in a content, the field settings for the original one were never changed and the themed installation came with images larger than 500k.
While for the time I can live with resizing images before uploading, it nevertheless is a pain in the .... and I really would appreciate any help.
I had a similar problem which i resolved via the php.ini file as well as the apache mod_security user.conf file.
My httpd is apache2, which has mod_security enabled, which also did not allow me to upload over 100k image file in Drupal. Apparently this is a common problem for the web-hosting provider (liquid web) because it took no more than 3 minutes to resolve.
First the php.ini file was altered (on CentOS it is in /usr/local/lib/) with lines:
;upload_tmp_dir = /tmp (yes it has a semi-colon at the start)
and also the line:
session.save_path = "/tmp"
Second file that was altered is the modsec2.user.conf file located on (CentOS) at /usr/local/apache/conf/
(appended at the bottom of the file in the last 2 lines):
SecUploadDir /tmp
SecTmpDir /tmp
Then /etc/init.d/httpd restart (or reload) apache and you should be able to bypass this limit for file uploads by mod_apache if it is enabled. Best of luck and please know that this is my first answer on stack so please be considerate.
just you can request your hosting provider
to added into the sites whitelist.conf file :
<IfModule mod_security2.c>
<LocationMatch .*>
SecRuleRemoveById 340147
</LocationMatch>
</IfModule>
I've recently purchased a virtual server in order to use it as a stage development for my site which is based on a forum script (ipb).
Problem is that before the installation and after it, ipb shows me some messages about suhostin limits. For example
'suhosin.post.max_vars' is 1000 and has to be changed to 4096
'suhosin.request.max_vars' is 1000 and has to be changed to 4096
For both occasions, it says that these settings are on my php.ini. After looking up, couldn't find any mention of suhosin there. But I found them at /etc/php5/conf.d/suhosin.ini and I proceed and changed them with the correct values.
Problem is that I keep gettin the error messages and when I load phpinfo, I see that the old values are still there. I restarted apache, I even restarted the server but suhosin still has the old values even if I edit the suhosin.ini file and see my edits are there.
Could anyone explain what I'm doing wrong ? I even added the lines to php.ini but still nothing changed.
Thanks
You need to make a file called "php.ini" in your admin directory (you find this through the root where you have your forums) and put the following in. Change the values as needed.
suhosin.request.max_varname_length = 400
suhosin.get.max_value_length = 2000
suhosin.request.max_vars = 4100
suhosin.post.max_vars = 4100
I've tried win xp and 7
Apache 2.2.19
php-5.3.6 (tried php 5.1.x)
Mysql 5.1.44
The install process runs ok until the database creation screen.
After 1 minute, the process stops at:
http://127.0.0.1/magento/index.php/install/wizard/installDb/
with a BLANK page
The database has only 199 tables (sometimes stops with less tables)
If i refresh the webpage, sometimes more tables are created, but then i get a database error.
Tried to IMPORT the database manually and start the install, but i get an error at the same step!
Also retried the install (deleting the cached data in the Magento folder).
What am i doing wrong?
thanks.
I used to get the same behavior. Other observation is you do not get the blank screen if you are running installation wizard while magento sample data imported to the database.
I did some googling and find the following poge which resolved my issue.
http://www.magentocommerce.com/boards/viewthread/76240/
that is modify apache httpd.conf and add following lines:
Options FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
I would suggest trying to install via the Command Line Interface:
http://www.magentocommerce.com/wiki/groups/227/command_line_installation_wizard
Open the index.php file (at the root) and write the following line at the top
<?php
set_time_limit(0);
?>
Empty the tables in your database and try again. The white page appears because the script times out and when you refresh that same page Magento gives you an error page where it says the table already exists. The SQL script which creates the tables in the database does not check whether the table exists in the database or not.
A blank screen in PHP is a strong sign of running out of memory. Check the memory limit according to the requirements and then maybe add a bit more too.
Change the name localhost file
with any www.example123.com in
c:\Windows\System32\drivers\etc\hosts
and add
127.0.0.1 www.example123.com
after wards follow these steps through this torrent link.
http://tinyurl.com/3r6dpop
After installing some images may not upload so even uploaded the books.
I got blank screen too, and the following error:
[09-Feb-2012 15:27:43] PHP Fatal error: Maximum execution time of 30
seconds exceeded in D:\creation\software
developer\projects\magento\document root\lib\Zend\Db\Statement\Pdo.php
on line 228
I'm pretty sure, that you have execution timeout too...
You have to setup your php.ini, and increase the max_execution_timeout, and in the iis manager you have to increase the fastcgi request and activity timeouts too.
Hello guys can anyone help me with the issue im having with installation of magento.
my problem is that i have downloaded the magento on wamp and during my installation i got the error and the msg it si giving is FATAL ERROR : Maximum execution time of 60 sec exceeded in
c:\wamp\www\magento\lib\varien\db\adapter\pdo\mysql.php on line 276. plz provide me with the solution any one coz im stuck on this for long enough thanks in advance
Modify your php.ini with this setting:
max_execution_time = 1800
I also modify the memory limit allocated to php when using Magento
memory_limit = 512M
Alternatively you can edit index.php, if you don't have php.ini access.
ini_set('max_execution_time ', 1800);
The exact resolution is as below
This is not an apache or php timed-out message. It really means that the mysql engine timed out. So we will give the mysql some more time to wait until it reports that the operation failed. To make this happen, lets go ahead and change the line with value
mysql.connect_timeout = 60
to
mysql.connect_timeout = -1
in the php.ini file and it will do the trick. The value -1 means unlimited seconds to wait before the mysql connection times out.
HI,
I had the same problem. None of the solutions provided above helped me.
What I did was change both the max_execution_time and max_input_time to 1800. This worked for me. I was able to then get Magento installed.
Change the value of max_input_time in php.ini to a safest value; time is expressed in seconds. Do give a try of 1800
max_input_time = 1800
You would get it worked
If its giving you the same error then it means that you have not changed the settings in php.ini file.
In windows if you install wamp you will have, php.ini in php folder and apache folder.
Make sure that you have modified in both files and restart your server. (I know its strange)
Try 1
Browse wamp's root folder and click on phpmyinfo link under tools section. This will give you the information of your php installation and settings.
look for "Loaded Configuration File", there you will have the location of your exact php.ini file that is used in your wamp installation.
Try to update the Max_execution_time in that file. Hope this will solve your problem.
Usually, you will not get problems like this.
Try 2
May be your antivirus is stopping the request to execute for more than 60 seconds, just trying stopping your anti-virus for a moment and check another time.
I hope this will solve your problems.
I got the same problem, as suggested I did the following changes.
(wampserver-path)\bin\apache(Apache Version)\bin\php.ini - Set the
value max_execution_time = 1800
(wampserver-path)\bin\php(PHPVersion)\php.ini - Set the value
max_execution_time = 1800
But it didn't work. Then I made the next change
In the host/(path-to-magento)/index.php, just after the opening <?php
tag, added the following. set_time_limit(1800);
<?php
set_time_limit(1800);
//** Other bunches of code
?>
Then tried to install a fresh copy. It worked! Hope this helps...