4.0.10 install bugs - [Solved - Seems to be an isolated case]

[Arno]

Hi Sjaak,

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.

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.

[svherpen]

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

[Arno]

Hi Sjaak,
I think this does make sense. 

If you find any other problems, please post them in a new topic.