Phoca Forum

I just upgraded to Joomla 3.1.5, and I updated Phoca Download to 3.0.2, and now when I try to go to my download page, i am getting the below SQL error:

0 - SQL=SELECT a.filename as filename, a.type as type, a.menulink as menulink FROM jml_phocadownload_styles AS a WHERE a.published = 1 ORDER BY a.type, a.ordering ASC

How do I fix this?

Thanks!!

Hi, do you get some error message there, this is standard sql - testing now in phpmyadmin and see no problem.
Try to check if your database includes phocadownlaod_styles table

Hello,

I had the same problem. I received a 1416 (I think) error saying the styles table was missing. I done an 'upgrade' via the 'extension manager'. the only way I got it to work was to uninstall, and then reinstall 3.0.2, it's now OK. Luckily, I don't have any downloads as yet (new website) but if you do, I suppose you could lose your library.....

Hope this helps somewhat....

Jan wrote:Hi, do you get some error message there, this is standard sql - testing now in phpmyadmin and see no problem.

Code: Select all

Displayed items 0 - 2 ( 3 )
SELECT a.filename AS filename, a.type AS
TYPE , a.menulink AS menulink
FROM jos_phocadownload_styles AS a
WHERE a.published =1
ORDER BY a.type, a.ordering ASC
LIMIT 0 , 30

Try to check if your database includes phocadownlaod_styles table

No, I do not have a phocadownload_styles table. And no phocagallery_styles table. Did the upgrade not work through the extension manager? i have a huge Photo gallery and download gallery, that I can't afford to have to remove and reinstall these extensions.

Thanks.

Hi, the styles table is there from beginning 3.0.0 so there is no upgrade for this table as it is there from beginning - just see install/sql/mysql/install.utf8.sql script and add the table manually to your database.

Jan

Ok, so that fixed the issue of the page not showing up, but now when I click on the download link to download an item, I get the below SQL error;

SQL=SELECT c.catid, c.filename, c.directlink, c.link_external, c.access, c.confirm_license, c.metakey, c.metadesc, cc.access as cataccess, cc.accessuserid as cataccessuserid, c.tokenhits FROM jml_phocadownload AS c, jml_phocadownload_categories AS cc WHERE c.id = 42 AND c.published = 1 AND c.approved = 1 AND c.catid = cc.id AND cc.access IN (1,1,4) AND ( c.publish_up = '0000-00-00 00:00:00' OR c.publish_up <= '2013-10-04 16:42:00' ) AND ( c.publish_down = '0000-00-00 00:00:00' OR c.publish_down >= '2013-10-04 16:42:00' ) ORDER BY c.ordering LIMIT 0, 1

Thanks!

The same happens here after having upgraded to 3.0.2.

SQL=SELECT c.catid, c.filename, c.directlink, c.link_external, c.access, c.confirm_license, c.metakey, c.metadesc, cc.access as cataccess, cc.accessuserid as cataccessuserid, c.tokenhits FROM jos_phocadownload AS c, jos_phocadownload_categories AS cc WHERE c.id = 9 AND c.published = 1 AND c.approved = 1 AND c.catid = cc.id AND cc.access IN (1,1,5) AND ( c.publish_up = '0000-00-00 00:00:00' OR c.publish_up <= '2013-10-05 08:19:39' ) AND ( c.publish_down = '0000-00-00 00:00:00' OR c.publish_down >= '2013-10-05 08:19:39' ) ORDER BY c.ordering LIMIT 0, 1

Hi, something went wrong on your server - while upgrading, not sql changes except the one set in schema, are done. Really no idea what went wrong, install or upgrade is done by Joomla! itself, so the component does not manage it. Try to check if all the tables are in your database:
https://www.phoca.cz/documents/16-joomla ... ent-errors

But really cannot say why they are not there - upgrade functionality in Joomla! does not delete any tables

Jan

Hi,

after upgrading from 3.0.1 to 3.0.2 I got SQL-Error (1054) too. This is caused by the new fields 'token' and 'tokenhits' in phocadownload table.
I had seen your intention to alter table with your update file 3.0.2.sql. But something seems to go wrong.
Maybe it's the "mysql"? Our site is configured to "MySQLi", not "MySQL". But this is only an idea - I'm not sooo familiar with Joomla's code.

After execution of the two "ALTER..." lines from 3.0.2.sql (replacing "#_" by real table prefix) directly in phpmyadmin all works fine.

Maybe this helps a bit,
Hoffi

This helped indeed

Still looking forward to a solution of the linebreak problem in descriptions.

Thanks a lot, Harald