I've made it through step "3" and am now on the "Go" panel of the 4.2 Install tool {version 4.2.1 - downloaded 08.03.08} and was rewarded with this error message after trying to login as the admin:

Warning: fopen(/home/sqorg08/public_html/typo3temp/cs/charset_iso-8859-1.tbl) [function.fopen]: failed to open stream:

Permission denied in /home/sqorg08/public_html/t3lib/class.t3lib_div.php on line 2661

Warning: fopen(/home/sqorg08/public_html/typo3temp/llxml/misc.xml_3d7a9cf868.default.iso-8859-1.cache)

[function.fopen]: failed to open stream: Permission denied in /home/sqorg08/public_html/t3lib/class.t3lib_div.php on

line 2661
ERROR: File not written to disk! Write permission error in filesystem?

Suggestions?

Bob,

As you can guess, the issue appears to be related to the application having permission to write to files in the directory typo3temp. Have you changed the write permissions on the appropriate directories (like typo3temp) and all the files inside?

In Him,
Mark

That got me past a few hurdles. At one point, when it stated that the installation was essentially completed (but there still was some configuration to do) I attempted to access the home page just to see what it looked like, and got this error message:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 19456 bytes) in /home/sqorg08/public_html/t3lib/class.t3lib_htmlmail.php on line 926

... and I got this just by typing in www.mydomain.com (well, the real domain name) in the address line of the browser. This is not encouraging ....

Bob:
I got stuck with a similar problem with allowed memory size. I fixed that problem by adding a file named php.ini in the home directory. The file contains:

memory_limit = 64M
upload_max_filesize = 10M
post_max_size = 10M

The memory_limit got me past my allowed memory size problem. Essentially the php.ini file overrides the unix/apache system's memory limit.

I added the next two entries as solving the memory problem only caused further problems that were resolved by the upload and post entries. I don't know if you will need these or not.

Hopefully, this may get you a bit further.

I'm currently stuck trying to finish the Step 3+ set of instructions. I can't get to the place where one should set the site's URL. Last night I found a possible fix at: http://webempoweredchurch.com/support/howtos/single/error-set-the-site-url-in-wec-constants/?tx_wecknowledgebase_pi1[cat]=53&tx_wecknowledgebase_pi1[backPid]=440&cHash=e24ff89785

I got to this "howto" from support, selected howtos, catagories show all then "installing WEC".

I have not had a chance to try it out yet, but once I got past the problem you are having I got stuck on the site URL not being set problem. I suspect that you may hit that one too. If so, maybe this hint will help you.

In Christ.

Russ Archer

Thanks for the help, Russ. I've added the php.ini file, and now am getting this error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1245184 bytes) in /usr/local/lib/php/Date/TimeZone.php on line 4307

Any ideas?

Bob,

Have you run the WEC Server Checker? See:

http://webempoweredchurch.com/gettingstarted/installing/wec_server_checker/

If you have not, my guess is that it will help identify issues with the server configuration.

In Him,
Mark

Bob,
I'd agree with Jason's advice in your other thread at http://WebEmpoweredChurch.com/index.php?id=333&no_cache=1&view=single_thread&thread_uid=2841&flag=last.

In some hosting environments, changing the php.ini file only affects scripts in the same directory as the php.ini and doesn't flow down into the subdirectories at all. Since you're still getting errors related to a memory limit of 32M, it seems like this is probably the case for you also. Jason's solution should provide a workaround for this.

Out of curiosity, who is your hosting company? It seems like I've seen this behavior more and more often so I'm curious whether one prominent host has started this or if several are.

Thanks,
Jeff

I'm getting the same message, or at least the last part of it. I go to login into the back end with the default username and password and all I'm getting is this:

ERROR: File not written to disk! Write permission error in filesystem?

Sean,

The issue appears to be related to the application having permission to write to files in the directory typo3temp. Have you changed the write permissions on the appropriate directories (like typo3temp) and all the files inside?

In Him,
Mark