Hello
After carefully following the instructions for migrating PhocaDownload from Joomla 2.5 to Joomla 3.0 it still doesn't work. The error message I get is the following:
1146 - Table 'mellink7_baken_st4.rpi72_phocadownload_styles' doesn't exist SQL=SELECT a.filename as filename, a.type as type, a.menulink as menulink FROM rpi72_phocadownload_styles AS a WHERE a.published = 1 ORDER BY a.type, a.ordering ASC
What can be wrong. Would it be better to clean install the latest Phoca download and re upload the data?
Thanks for help, Fred
Migration from Joomla 2.5 to 3.0 fails
- Benno
- Phoca Hero
- Posts: 9611
- Joined: 04 Dec 2008, 11:58
- Location: Germany
- Contact:
Re: Migration from Joomla 2.5 to 3.0 fails
Hi,
https://www.phoca.cz/documents/50-phoca/ ... o-joomla-3
Benno
Did you read this migration guide?Would it be better to clean install the latest Phoca download and re upload the data?
https://www.phoca.cz/documents/50-phoca/ ... o-joomla-3
Kind regards,All import actions must be done directly after installation of Phoca Gallery (Phoca Download) in Joomla! 3. All Phoca Gallery (Phoca Download) database tables must be empty before importing data from backup file.
Benno
-
- Phoca Newbie
- Posts: 3
- Joined: 18 Dec 2014, 20:07
Re: Migration from Joomla 2.5 to 3.0 fails
Has this problem solved ? Because this problem has been posted on the 4th of dec 2014. If so, than I like to know the solution and can go on with the migration.
Regards,
Kees
Regards,
Kees
- Benno
- Phoca Hero
- Posts: 9611
- Joined: 04 Dec 2008, 11:58
- Location: Germany
- Contact:
Re: Migration from Joomla 2.5 to 3.0 fails
Hi,
do you receive same error as fmlk4u ?
Benno
do you receive same error as fmlk4u ?
Kind regards,1146 - Table ''#__phocadownload_styles' doesn't exist SQL=SELECT a.filename as filename, a.type as type, a.menulink as menulink FROM #__phocadownload_styles AS a WHERE a.published = 1 ORDER BY a.type, a.ordering ASC
Benno
-
- Phoca Newbie
- Posts: 3
- Joined: 18 Dec 2014, 20:07
Re: Migration from Joomla 2.5 to 3.0 fails
Yes I do and I think I solved the problem. In my case it works.
I have the intention to put it on paper but my English is not so good. Can I do it in Dutch?
Within 1 or 2 days you get the answer in Dutch or broken English. Please be patience.
Regards
Kees
I have the intention to put it on paper but my English is not so good. Can I do it in Dutch?
Within 1 or 2 days you get the answer in Dutch or broken English. Please be patience.
Regards
Kees
- Benno
- Phoca Hero
- Posts: 9611
- Joined: 04 Dec 2008, 11:58
- Location: Germany
- Contact:
Re: Migration from Joomla 2.5 to 3.0 fails
Hi,
I'm afraid my dutch is even worse than your English. Therefore let us better use English.
Kind regards,
Benno
I'm afraid my dutch is even worse than your English. Therefore let us better use English.

Kind regards,
Benno
-
- Phoca Newbie
- Posts: 3
- Joined: 18 Dec 2014, 20:07
Re: Migration from Joomla 2.5 to 3.0 fails
Hi,
The manual "https://www.phoca.cz/documents/50-phoca/ ... o-joomla-3" is ok.
In the first time I saw that I was missing two tables after upgrade prefix_phocadownload_styles and prefix_phocadownload_styles.
Started again from scratch and used Joomla_3.3.6-Stable-Update_Package.zip. And now I had all the tables from phocadownload.
Now it was time to import the .sql file. Went wrong. After more times to start from scratch I noticed that it is very imported dat the prefix from the tables in the database must be equal to the import tables. When I figured that out it was no problem for migration. In phpMyAdmin you can change the prefixs.
Hopefully you are satisfaction with my answer.
Kind regards,
Kees
The manual "https://www.phoca.cz/documents/50-phoca/ ... o-joomla-3" is ok.
In the first time I saw that I was missing two tables after upgrade prefix_phocadownload_styles and prefix_phocadownload_styles.
Started again from scratch and used Joomla_3.3.6-Stable-Update_Package.zip. And now I had all the tables from phocadownload.
Now it was time to import the .sql file. Went wrong. After more times to start from scratch I noticed that it is very imported dat the prefix from the tables in the database must be equal to the import tables. When I figured that out it was no problem for migration. In phpMyAdmin you can change the prefixs.
Hopefully you are satisfaction with my answer.
Kind regards,
Kees
- Benno
- Phoca Hero
- Posts: 9611
- Joined: 04 Dec 2008, 11:58
- Location: Germany
- Contact:
Re: Migration from Joomla 2.5 to 3.0 fails
Well done!
Kind regards,
Benno

Kind regards,
Benno
-
- Phoca Newbie
- Posts: 4
- Joined: 30 Dec 2014, 00:26
Re: Migration from Joomla 2.5 to 3.0 fails
Hi,
I follow this discussion (and others) but i still don't understand the step of importing datas and the renaming of the prefix. Can you give me details on this point ? Actually, i have saved my old database with "jos_" prefix. The new installation of phoca also gives a "jos_" prefix to the tables. What do i have to do ? Step by step for this step
Thank you for your help.
I follow this discussion (and others) but i still don't understand the step of importing datas and the renaming of the prefix. Can you give me details on this point ? Actually, i have saved my old database with "jos_" prefix. The new installation of phoca also gives a "jos_" prefix to the tables. What do i have to do ? Step by step for this step

- Benno
- Phoca Hero
- Posts: 9611
- Joined: 04 Dec 2008, 11:58
- Location: Germany
- Contact:
Re: Migration from Joomla 2.5 to 3.0 fails
@ouioui9,
if the new prefix is the same as the old one, there is no need to change anything. Export data as described and import this data (as described) without changing prefix.
Kind regards,
Benno
if the new prefix is the same as the old one, there is no need to change anything. Export data as described and import this data (as described) without changing prefix.
Kind regards,
Benno