[solved] jdownloads_cats doesn't exist (with AceSEF)

[LUCiD]

Hi there,
I'm using Joomla! 3.4.3
PHP-version   5.4.44
jDownloads Version 3.2.35 / 3.2.36

After updating to the latest version of jDownload yesterday (3.2.35) from version 1.9.2.11 beta (the update went well in the backend) I got the SQL error message  '1146 table jdownloads_cats doesn't exist' in the frontend with the standard menu link (show all categories - I've updated the link in the backend first and cleaned the cache of joomla and the browser).
After renaming the new table jdownloads_categories to jdownloads_cats I got the message 'jdownloads_categories doesn't exist'.
Today I've seen the new version (3.2.36) and made the update, but I've got the same message in the frontend. I don't know why this happens and which file from jD is responsible for the query.
Cause it is my life site, I've now re-uploaded my backup with the old 1.9.2.11 version.
Please, could you give me an advice what I can do to fix this problem, when I'll make the update to V3.2.x again?

[ColinM]

Hi Lucid
You have the most important part of the process - a backup!!
You cannot update directly from jd1.9.2.11 to the jd3.2 series - you need to migrate.

Please see the documentation
http://www.jdownloads.net/documentations/item/how-to-upgrade-jdownloads-component-from-1-9-x-to-latest-3-x-version
where the process is carried out step by step.

Very many people have followed this sequence and had a good result.  Please allow yourself plenty of time and also make sure you have copies of the other articles.
I suggest you print out the sequence and mark off each step as you go! It is easy to miss a step

Please let us know how you get on

Colin

[LUCiD]

Hi Colin,

thanks for you reply and your advice, but I have to say sorry for my wrong description "update", my English is not the best.

I've done that what your link to the documentation describe - the migration. I followed all the steps there and as I said before, It went well in the backend but after updating the menu link (first I tried to update the existing link and second, I deleted it and made a new one), I got that SQL error message I wrote above - That is really strange. Can you imagine where this error came from?

Greetz

[LUCiD]

Hello again,

no idea why this happened?

I tried the migration again on last weekend and I got the same error

Edit:
Question: How important ist this migration from the 1.9 to the 3.2 branch - in a security manner?
I would try it first at home locally, to figure out the issue, but that would take some time to setup a localhost environment and most likely your help.

Greetz

[ColinM]

Hi

You said earlier

It went well in the backend but after updating the menu link (first I tried to update the existing link and second, I deleted it and made a new one),

What menu link do you mean?
Do you have links in Content pages as that uses ids that may well have changed.

Colin

[LUCiD]

Hi Colin.

What menu link do you mean?

I mean the menu link (e.g. at the main menu), to show the frontend part with all categories according to point 19. in the tutorial:

You may also need to visit the Menu Manager to re-enable any menu links.  This is because Joomla! may disable links associated with a component when it is uninstalled. Rightfully Ii does not re-enable them when the component is re-installed as it cannot know that it is the 'same' one.  This does not occur during regular update.

I didn't checked all the article links jet, atm it makes no sense to do it.
The SQL message in the frontend, after clicking the menu link to show all categories says "xxx_jdownloads_cats doesn't exist", but this is a table from the old version 

Greetz

[ColinM]

Hi
Have you tried creating a new menu item?  And does that work?

As another thought do you have URL rewriting enabled?  If so could you try with it turned off.
Also for completeness whilst that is off try with SEF turned off as well . 
Whilst thinking on those line do you have any SEF plugins/modules - if yes could you disable please.

If the above are still do not cure then it looks like we may have to check in detail on your website.  If you would like us to do that then please send by PM super user login details.  If needed I will also send to Arno.

Also could you advise which type of database you are using please. And could you make a list or pic of all the jD table names please.  They have names like <your prefix>_jdownloads_name-specific.  It would be best if you either blocked out the prefix part or sent pic attached to PM.

Colin

[LUCiD]

Hi.

Yes, I made a new menu item, but it also doesn't worked.

I had similar thoughts in mind, may it has to do with the SEF part.

Thanks for your help Colin. I'll check this out on next weekend, maybe tomorrow and report back then.

Greetz

[LUCiD]

Hello there, Colin.

Finally and as far as I can see atm, the migration worked well (again) and the component works now as it should, only the redirect after a download gives back a 404 page not found. I have deactivated this again, its not important for me.

So please Colin, move this thread to a better place if you want, cause it was not a bug. It was the SEF-Component I'm using - AceSEF.

AceSEF uses some own extensions for each component and there are some options, e.g. the router to use for a component and the AceSEF extension for jDownloads was still the actual, the old one and made this queries to the old jD tables.
After switching the router from AceSEF-extension to the components own one, all URL's are now fine, are working well and the SQL error message is gone.

Now I can tweak the fontend templates a bit again and check the articles about deep links.

So here are the steps to make it work with AceSEF.

   
• Backup Joomla, site and database.
• Unpublish the menu item to the downloads and switch jD to maintenance mode.
• Purge all SEF-Urls that point to the old jDownloads component from the AceSEF tables (can be filtered in the URL's  backend).
• Make the jD migration with the data backup first a.s.o., as the tutorial describe. (if you tried the migration before, like me, then it may have left backup tables; these must be deleted before installing the new V3 jD, otherwise it can not create these tables again and will fail)
• Switch the router option for jDownloads in the AceSEF / extension section to "Component's router"
• Update the menu item and publish it.
• Clean all caches.

Thanks again Colin for your thoughts, advice and help, lots appreciated, and thanks for the great component to all who are involved and made it.

[ColinM]

Lucid
Thanks for your update.  I have moved the posting to the main 3.2 Forum.  Also made minor 'English' adjustments to your very helpful instructions.  I particularly noted the bit about removing backup tables if you have a failed migration.  Will edit the migration article to add a footnote about that situation.

Colin

[LUCiD]

Thanks for moving and the adjustments!

In the meantime I had some additional thoughts about the SEF part in that migration process. But its not tested yet by me - so make all backups before trying.

Between step 3 and 4 of my list above, before migrating jDownloads and after purging the old urls, uninstall the AceSEF-extension for jDownloads at the AceSEF / Extension section. And after the jD component migration is done, start searching for updates about this extension (atm. it is "1.5.3 Up-to-date"). The license is described as free, so this is probably a additional good Idea in mind, especially if more control over the SEF-urls is needed.

Have a good time folks!

=/\=