Bug #64170
closed
[ TYPO3 + PostgreSQL ] Problems to render TYPO3 Template
0%
Description
Dear TYPO3 Community,
Happy New Year to All. We are trying to setup PostgreSQL with TYPO3 Installation. Thanks in advance, to take a look at following issue:
1. Testing Environment:
1.1 TYPO3 6.2.9
1.2 PostgreSQL 9.3.5
1.3 Apache 2.4.7
1.4 PHP 5.5.9
1.5 Ubuntu
2. Problem:
2.1 Backend: We have checkout TYPO3 backend and it's really works fine.
2.2 Frontend: Somehow, Frontend templating does not able to render, we have tried lots to debug it too. We always got this error 'No pages are found on the rootlevel!' - Checkout screenshot for the same http://awesomescreenshot.com/08944ox363 (We have already setup Root level Page and TS Template).
3. Backend template setup: We have setup simple 'Hello World' - Checkout this screenshot - http://awesomescreenshot.com/00344oxl6e
4. Need Clarification: At the TYPO3 documentation, There has been defined something at 'Database specific issue' with "Currently altering an existing column is not supported, as the underlying ADOdb library needs a full table description to do that, as on PostgreSQL you need to drop and recreate a table to change it's type (this has changed in PostgreSQL 8, but ADOdb doesn't support this yet)." Checkout: http://docs.typo3.org/typo3cms/extensions/dbal/KnownProblems/DatabaseSpecificIssues/Index.html
5. Error Logs:
5.1 Administration Log: http://awesomescreenshot.com/005451817e
5.2 PHP Debug error: http://awesomescreenshot.com/013451b96d
Hoping to get suggestion/solution asap, Thank you!
TC
Sanjay
Updated by Markus Klein over 9 years ago
Updated by Sanjay Chuahan over 9 years ago
Dear Markus,
Thanks for your response. Let's keep it up our conversation here. We will checkout your mentioned following things:
It looks like your DBAL configuration is not correct. Can you please check the error.log of your webserver? There should be some more messages. In any case, go to the Install Tool and enable the "Development Preset".
Keep in touch together here, Thank you!
TC
Sanjay
Updated by Jigal van Hemert over 9 years ago
- Status changed from New to Needs Feedback
Did you run typo3/sysext/dbal/res/postgresql/postgresql-compatibility.sql ? This add some compatibility functions to PostgreSQL.
Maybe you can turn on debugging in the DBAL configuration. Debugging information is written to the table 'tx_dbal_debuglog'.
The Administration Log you included suggests that a query fails completely and because of that FALSE is returned as result. This can explain the messages about converting a variable to a default object. The challenge is to find out which query fails, why it fails and why it was constructed incorrectly.
Hopefully you can dig up some details.
Updated by Alexander Opitz almost 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.