I come back with these errors : they are still there with sqlite3.
Much less than at first (only 5)
They only appear on first clean install even with ~E_strict error param.
I can continue the install by reloading the page at least with Firefox.
Are there any consequences, apart a non clean install ?
Alain
""
Strict Standards: Declaration of MDB2_Driver_sqlite3::_doQuery() should be
compatible with that of MDB2_Driver_Common::_doQuery() in
/shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 909
Strict Standards: Declaration of MDB2_Driver_sqlite3::prepare() should be
compatible with that of MDB2_Driver_Common::prepare() in
/shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 909
Strict Standards: Declaration of MDB2_Result_sqlite3::fetchRow() should be
compatible with that of MDB2_Result_Common::fetchRow() in
/shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 1035
Strict Standards: Declaration of MDB2_Statement_sqlite3::execute() should be
compatible with that of MDB2_Statement_Common::execute() in
/shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 1334
Strict Standards: Declaration of MDB2_Statement_sqlite3::_execute() should
be compatible with that of MDB2_Statement_Common::_execute() in
/shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 1334
Warning: session_regenerate_id() [function.session-regenerate-id]: Cannot
regenerate session id - headers already sent in
/shares/Public/WWW/WWW-pub/master/lib/user.php on line 203
Warning: Cannot modify header information - headers already sent by (output
started at
/shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php:909) in
/shares/Public/WWW/WWW-pub/master/lib/setup.php on line 26
-----Message d'origine-----
From: Thomas Tanghus
Sent: Sunday, May 13, 2012 5:41 PM
To: [email protected]
Subject: Re: [Owncloud] V4.0.0 - Current Git - Clean install :
StrictStandards messages
On Sunday 13 May 2012 06:30 Frank Karlitschek wrote:
On 13.05.2012, at 00:31, Thomas Tanghus <[email protected]> wrote:
> On Saturday 12 May 2012 22:07 Frank Karlitschek wrote:
>> Hi,
>>
>> this is not good.
>> Is there something we can do to fix this? Or do we have to revert to
>> the
>> old MDB driver?
>>
>> I just released RC anyways but we have to fix this for the final
>> release.
>>
>> I recommend all developers to run ownCloud with notices switched on.
>> Because it easier for debugging and motivates us all to do cleaner
>> coding. ;-)>
> I actually just pushed a commit that suppresses notices when importing
> events or contacts from the files app. To be honest I think that hook
> should be disabled for this release because it has inter-app
> dependencies
> that aren't properly handled, it introduces two extra writable
> directories, and there's hardly any error checking.
Your´re the expert here. :-)
Let´s disable it if it´s not working properly.
Not really because I have no idea how the filesystem hooks work - yet ;-)
I may have found what caused the errors, and in the process also found some
errors in my js code.
If I add more error checking and reporting, would it then be OK to push
those
changes? I guess I was a bit grumpy when I wrote the last mail, because I
really think we should have the import functionality.
--
Med venlig hilsen / Best Regards
Thomas Tanghus
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
