Page 1 of 2
../public_html/libraries/joomla/database/database/mysqli.php
Posted: 19 Jun 2011, 12:40
by jokrsolutions
Thanks Jan for latest version
After i upgraded to stable version (1.6) i got this message (3 times) in "file view" in backend
../public_html/libraries/joomla/database/database/mysqli.php on line 345
In the file its says:
return mysqli_num_rows($cur ? $cur : $this->_cursor);
The files is not shown in backend, only in frontend
Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 20 Jun 2011, 11:17
by Jokus
I've got the same problem.
Additionally in the backend you can't sort files by name, downloads, title, etc.. even if you may click on the name to sort.
Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 21 Jun 2011, 09:44
by SonRiab
After upgrading from 2.0.0rc3 to stable I got the same error!

By the way: PD Button shows the files correctly!

Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 22 Jun 2011, 16:08
by chrisd
Hi,
after upgrading form Version 2.0.0RC3 to the final version I get this error as well when clicking on files, it appears three times:
Warning: mysqli_num_rows() expects parameter 1 to be mysqli_result, boolean given in .../htdocs/pab/cms/libraries/joomla/database/database/mysqli.php on line 345
I'm wondering if this has something to do with the new column userid as advised in the change log, especially as I have upgraded the module rather than having done a fresh install as I liked to keep my data
I didn't have time to check this it is just an idea...
Any more detailed input and how to fix it is very welcome.
Best regards
chrisd
Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 23 Jun 2011, 14:02
by chrisd
OK,
I've done some more research and voilĂ I think I've got a fix...
My suspicion was correct. Obviously I have updated from 2.0.0 RC3 to the final 2.0.0 version and this has not created the 'userid' field in the 'jos_phocadownload'.
I have run the following SQL statement on my database
Code: Select all
ALTER TABLE `jos_phocadownload` ADD `userid` int(11) NOT NULL Default '0' AFTER `description`
and the error has gone, the file list is shown...
HTH
chrisd

Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 24 Jun 2011, 06:16
by sade
thank you chris!
Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 26 Jun 2011, 15:04
by dounne
chrisd wrote:OK,
I've done some more research and voilĂ I think I've got a fix...
My suspicion was correct. Obviously I have updated from 2.0.0 RC3 to the final 2.0.0 version and this has not created the 'userid' field in the 'jos_phocadownload'.
I have run the following SQL statement on my database
Code: Select all
ALTER TABLE `jos_phocadownload` ADD `userid` int(11) NOT NULL Default '0' AFTER `description`
and the error has gone, the file list is shown...
HTH
chrisd

You're the best man !! THanks a lot !!

Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 11 Jul 2011, 15:07
by lcdservices
i ran into this bug and traced it in a similar fashion.
adding the userid field resolves the error and the files tab works correctly. however, i question whether that's the correct fix. i note in that table the presence of an owner_id column, which presumably is a foreign key to the users table. is it possible the correct fix is to correct the query to use that column.
Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 12 Jul 2011, 22:30
by Jan
Hi, this was not a bug. See the information in this forum.
Alpha, Beta and RC versions are designed for testers only and every test version should be reinstalled not upgraded. In case you will install the stable, there will be no such problem, in case you have upgraded - the new column were not created in the database - because upgrade function didn't include the uprading of the column.
Such behaviour is only in development versions. Between stable versions the upgrade function will upgrade the new column too if some will be added.
Jan
Re: ../public_html/libraries/joomla/database/database/mysqli
Posted: 27 Jul 2011, 18:18
by chrisd
Hi Jan,
thanks for this clarification. I can see the point why it is done this way. Nevertheless I think it would be great if the upgrade feature is also available on not stable versions.
There are two arguments for it: First it ensures the upgrade works in the final version and second I can keep my data
Best regards
Chrisd