Tuesday 18 January 2005 2:01:07 pm

I had read this issue with PHP, and set the memory limit to 20MB. Let me try it with a really big number and see if that helps. I will redo the install wizard and report back...

Tuesday 18 January 2005 2:25:56 pm

The error message just means eZ publish didn't manage to compile it's templates in the 60 seconds it was given. Just hit refresh when you see the error message to let it continue its job.

Kristian

http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used
http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute

Tuesday 18 January 2005 2:53:18 pm

> The error message just means eZ publish didn't manage to compile it's templates in the 60 seconds it was given.

Wow! Some success! I increased the timeout limit to 600 and got a successful start page.

How do I get rid of the "AcceptPathInfo" complaint? Or do I not need to worry about it?

Wednesday 13 July 2005 6:56:00 am

Hello Doug,

Are you still getting the <i>AcceptPathInfo</i> message or did you get to solve it? I am having the same trouble, with Apache 2 and need help.

greetings
Roberto

Wednesday 13 July 2005 1:26:15 pm

Frederik, thanks for the quick reply, and the good news. How would I <i>know</i> AcceptPathInfo is <i>On</i>? Is there Any specific test I could do or configuration file that I could look at before proceeding with the instalation?

Thanks! Roberto

Thursday 28 July 2005 7:29:52 am

After I finally got to install 3.6.0, I came to know of 3.6.1, with native pt-BR and lots of fixed bugs. So I decided to install 3.6.1 and at the end of the installation, after the Registration screen, I got:

Fatal error: A database transaction in eZ publish failed.

The current execution was stopped to prevent further problems.
You should contact the System Administrator of this site with the information on this page.
The current transaction ID is TRANSID-67fd571ce3dda3760d01a0610d9f24bc and has been logged.
Please include the transaction ID and the current URL when contacting the system administrator.

Thursday 28 July 2005 8:22:54 am

Why should I have to fish anything out? Why don't all the necessary messages appear on screen? Anyways, the last messages that appear on mysql.log are:

123 Query INSERT INTO ezcontent_translation (name, locale) VALUES('Português', 'por-BR')
123 Query SELECT id, name, locale
FROM ezcontent_translation
WHERE locale='eng-US'
ORDER BY id ASC
123 Query INSERT INTO ezcontent_translation (name, locale) VALUES('English (American)', 'eng-US')
123 Query BEGIN WORK
123 Query INSERT INTO ezcontentobject_name( contentobject_id,
name,
content_version,
content_translation,
real_translation )

SELECT con.contentobject_id,
con.name,
con.content_version,
'eng-US',
'por-BR'

FROM ezcontentobject_name con

WHERE con.content_translation = 'por-BR'
123 Query UNLOCK TABLES
123 Query ROLLBACK
123 Quit

Here's the system information that shows during install... what else should I inform? You asked about the database. It&acute;s a standard MySql 3.23.54 where I successfully installed 3.6.0 before.

Comments:

Site info:
Template - Plain
Title - A Biblioteca Virtual do Estudante de Língua Portuguesa
URL - http://carraher.futuro.usp.br/ezpublish/index.php/bibvirt
Admin URL - http://carraher.futuro.usp.br/ezpublish/index.php/bibvirt_admin
Access type - url
Access value - bibvirt
Functionality - contact_us, files, gallery, links, media, news, poll, weblog

PHP info:
Version - 4.3.1

OS info
Name - Linux carraher.futuro.usp.br 2.4.21-28872cl #1 Sex Mar 21 22:55:39 BRT 2003 i686
CPU Type - AMD Duron(tm) Processor
CPU Speed - 1000.047 MHz
Memory Size - 245788672 (234.40 MB)

Database info:
Type - MySQL
Driver - ezmysql

Email info:
Transport - sendmail

Image conversion:

ImageGD extension was found and used.

Regional info:
Primary - por-BR
Additional - eng-US, esl-MX, por-PT, por-BR

Critical tests

directory_permissions - Success
database_extensions - Success
image_conversion - Success
open_basedir - Success
safe_mode - Success
memory_limit - Success
execution_time - Success
magic_quotes_runtime - Success
php_session - Success
file_upload - Success

Other tests:

php_magicquotes - Failure
zlib_extension - Success
mbstring_extension - Success
imagegd_extension - Success
imagemagick_program - Failure
database_all_extensions - Failure
php_register_globals - Failure
texttoimage_functions - Success

I've posted this here at this forum section so we don't lose history. But following your suggestion I also reported it in the bug report section.

Thanks.

Thursday 28 July 2005 9:04:27 am

I agree, sensitive information should be protected. Fortunately I have some Linux background so I could find and read and post the last lines of mysql log. But on behalf of the programmers and other mortals who can't do that: how does one turn debugging on? Obviously it's not in the Admin interface, since at the time of the error the Admin interface was not working yet.

Looking at the last lines mysql log I had the intuition of trying to install it again, but this time not chosing por-BR as the main language (actually I didn't chose it even as a secondary language, I completely left it out) - - and it worked. I posted this info at the bug reporting section too.

Still I have the problem of not being able to use the provided .htaccess_root which is intended to heighten the security level but which makes my Apache 2.x get an "internal server error". (you see, I said I had <i>some</i> Linux background - not an <i>ideal</i> one)

Thursday 28 July 2005 12:52:49 pm

You want to turn on global debugging and SQL debug in site.ini (you can find it in settings).
http://ez.no/doc/ez_publish/technical_manual/3_6/reference/configuration_files/site_ini
the settings you want to enable are named SQLOutput and DebugOutput.