Just installed the latest version, unfortunately I'm still having the problems:
1) incorrect integer value * for column......
The strange thing there is that it's refering to a table that does not exist: jos_jdownloads_templates_40x
2) No downloads shown (database table empty)
3) No files shown (database table empty)
4) Backend language is not in Dutch anymore (where it used to be Dutch in the previous environment), but only English language is used
See the attached screen pictures for more info.
And I'm still trying to upgrade directly from a cloned website (Joomla 3.10.11, PHP8 and jDownloads 3.9.8.6)
The new environment is running PHP4, Joomla 4.2.6 and directly using the last jDownloads 4.0.10, so no other beta releases in between
Hi
The database structure of jD 3.2 series is not compatible with either jD3.9 or jD4.0.6 (or higher)
Were you starting with a jD 3.2? If so you need to ensure it was at the latest version
Then upgrade to jD 3.9.6.9
The next seps involve upgrading from Joomla 3 to Joomla 4
From there to jD 4.0.10 beta. There is an article that describes the steps in going from 3.9 to 4.0.9 at
https://www.jdownloads.com/forum/index.php?action=dlattach;topic=13728.0;attach=16978
Colin
PS it is probably advantageeous to get your site to PHP 8 when it is at Joomla 4
Hi Colin,
I think you misread my post as I'm on JD 3.9.8.6 prior to upgrading to JD 4.0.10
Sjaak
Hi Sjaak,
would it be possible to get an akeeba backup from your website where you want to run the upgrade to jD 4? ::)
At best, with the status after Joomla 4 upgrade but before you have tried the jD upgrade.
Hi Arno,
Sure, I've just installed Akeeba and made the backup, however it's quite large (145 Mb)
It contains the updated Joomla 4.2.6 site with JD 3.9.8.6. So yes, prior to updating.
I've just send it via WeTransfer, hope that's okay.
https://we.tl/t-ZtOpDR10j7
Sjaak
Thank you very much for the backup, it has made troubleshooting much easier.
Result:
1. the old version 3.9.8.6 was installed but unfortunately deactivated in the extension manager. This made the update more difficult or even impossible. As described in the update instructions, only the jDownloads system plugin should be deactivated before the update. The main component must remain activated!
2. the current jDownloads tables are not those of version 3.9.x but seems to have partiell already the format of the new version 4? Presumably from an earlier update attempt.
3. the database still contained backups of the old tables from jDownloads version 3.2.x. These are not disturbing, but they are superfluous.
All this means that the state is not as normally expected by the upgrade routine. Therefore, the update had to fail.
I have now tried the following:
1. jDownloads component activated
2. deleted old jDownloads 3.2 tables
3. started the update
4. again I got the database error with the 'templates' table.
5. a check now showed that the structure of the table (i.e. the order of the data fields) does not correspond to the standard. This causes this error message and the abortion of the data transfer from this table.
On all my test environments, I could not find a single template table with this different order, so now I have to look for the reasons for the different table structure. I will also have to create an update adapted to this. So please be patient for another day or two. :)
Hi Arno,
Sorry that I missed the part of leaving only the jDownloads system plugin disabled prior to the update...
I'm causing you extra trouble in fixing this :'(
What I will do:
1) export all the jDowloads tables from my live site which is running jD 3.9.8.6
2) drop all the jDownloads tables from my upgraded TEST database
3) import the jDownloads tables from the live site
4) make sure the jDownloads system plugin is disabled
5) make a new backup of the TEST environment
Keep the fingers crossed an run another jDownloads upgrade with version 4.0.10
You have misunderstand me. Please read my hints again.
The jDownloads system plugin must be DISABLED!
But the jDownloads component ENABLED!
And wait on version 4.0.11.
Yeay, thanks for the warning. I noticed I read it the other way around.
One more thing I want to inform you about Arno,
With the plugin Content jDownloads 3.9 enabled, there's also an error shown in the backend prior to up.
See the pics for the evidence.
As a final note for now, I've just send you the latest Akeeba backup.
Status prior to updating jDownloads.
Please validate if this is the correct system state.
Sjaak
Hi Sjaak,
I have check it.
Unfortunately, not all your jDownloads DB tables are as they should be. :-\
About your templates table have we already talked.
But also your files table is not correct.
The field tags still exist here but should be removed a long time ago.
And there is also an error in the order of the data fields. The field featured is at the end instead of before the field published. I have no idea why this is the case with you. In any case, it's not normal.
I have now new sorted your files table and will be try again an update. ::)
Hi Arno,
I've no clue how this could happen... I've never tampered the jdownloads database tables. Always used the upgrade component feature as Joomla administrator.
I've included the SQL dump of the live site and in there it proofs what you are saying about the wrong datafield order sequence.
To get this fixed, can I modify the create table commands so the sequence is what you will expect? If yes, what is the correct order?
Hi Sjaak,
further checks have now also revealed missing data fields in the _jdownloads_usergroups_limits table.
I don't know how the unusual database tables could have happened. It is possible that important updates were simply skipped. Otherwise, there is only the possibility of faulty updates. Unfortunately, I don't have the time to check this more closely. I just hope that this is and remains an exception for you. Because if other users also have changed tables, I would have to extend the update script very extensively and try to take more eventualities into account (which would require a lot of extra work).
In any case, I have now invested a lot of time and work to make the update possible for you. Even if via a diversion.
I have your send an e-mail with a few small instructions.
Hi Arno,
I'm very thankfull that you managed to get my (strange) problem sorted!
I've run the update 4.0.11, deleted the tables and imported your dataset.
As far as I can see now, it looks like normal again. Downloads are visible, the layouts are there.
And even more, on the fronsite I do see the 'upload document' icon again, where as on my live site this disappeared all of a sudden. Remember that you took a look there, tried to fix it with AWT PCL, but still the upload button was not shown.
So I can continue testing the jDownload functionality to see if I have any more unusual things.
One question though: when we're at the point that my live site will be upgraded, do I need to apply the fixes as described in your email by dropping the tables and recreating them again?
As I need to ensure that in the meantime I have to keep track of added files.
Sjaak
Hi Sjaak,
QuoteOne question though: when we're at the point that my live site will be upgraded, do I need to apply the fixes as described in your email by dropping the tables and recreating them again?
As I need to ensure that in the meantime I have to keep track of added files.
Good question. :-\
I had to correct some things manually. So it is not so easy to do it again later.
Therefore, I would suggest that they now test the new version for a few more days, as far as possible, in the frontend and backend.
If these tests do not reveal any new major bugs, you should be able to dare to update this version with the submitted tables.
Another option would be for me to send you instructions (including a modified jdownloads_files table) so that you can do this yourself on your live site at a later date. With the then current data.
I will not be able to upgrade the live site to Joomla4 (and PHP8) on short notice, still waiting on 1 frequent used component to be made PHP8 proof.
Therefore, I was thinking the following scenario:
- I've already rebuild the live site in my TEST environment as far as possible (except this one component ChronoConnectivity, which is planned for end of this month, beginning februari)
- during the next weeks, I'll keep the TEST environment up-to-date with any new downloads that will be added in the live environment
- when my entire TEST site is 100% ready, I will move the live site apart and recreate the new site using my TEST environment
By doing so, I'm most confident that the new updgraded site will work as expected. Not having to manually fiddle around with tampered tables in the live environment as we just had done.
Does this make sense?
And let's hope that I am the one and only exception that ran into this weird situation ;)
Sjaak
Hi Sjaak,
I think this does make sense. :)
If you find any other problems, please post them in a new topic. ;)