Nick W Posted April 2, 2023 Report Share Posted April 2, 2023 I recently upgraded our site from v11.1.2 to v14 and everything appears to be working well apart from the import/export function. When I try to upload a Gedcom file I just get the spinner which goes on for ever, but when I try to download a file I get the attached error and clicking the “resume” link leads to a similar error. I tried going through the database structure part of the upgrade again, via the readme file, but this doesn’t alter the error. The situation is also confused by my webhost recently upgrading the SQL database from MariaDB 10.3 to MariaDB 10.6 and I don’t know if this is affecting the import/export function. Any help would be much appreciated. Nick https://woosterfamily.co.uk/TNG/index.php Quote Link to comment Share on other sites More sharing options...
Ken Roy Posted April 2, 2023 Report Share Posted April 2, 2023 28 minutes ago, Nick W said: Nick, That error indicates that you skipped a database upgrade step when upgrading your site some time in the past. Sorry, I do not remember when the field name was changed Quote Link to comment Share on other sites More sharing options...
Nick W Posted April 3, 2023 Author Report Share Posted April 3, 2023 Thanks Ken, Partial success! I found the name in the database to be foffset and changed it to fileoffset and that results in the export function working again. No luck with the import function yet, so I'm going to try going through the upgrade process again and see if that leads to success. Many thanks, Nick Quote Link to comment Share on other sites More sharing options...
Ken Roy Posted April 3, 2023 Report Share Posted April 3, 2023 You may need to use a database upgrade from the TNG upgrade readme. There are likely other changes to the database. Quote Link to comment Share on other sites More sharing options...
Nick W Posted April 4, 2023 Author Report Share Posted April 4, 2023 I think you were right about something in the previous upgrade to v11 not working and it all still worked in spite of this error. I may well have to go back to a previous upgrade readme to correct this, but first I'll try going through the current one again. Nick Quote Link to comment Share on other sites More sharing options...
theKiwi Posted April 4, 2023 Report Share Posted April 4, 2023 The current one won't do it. Go back to the TNG downloads page and download the upgrade from TNG 11 to TNG 14.0.1 and then upload the dbupgrade script from that and run it. Roger Quote Link to comment Share on other sites More sharing options...
Nick W Posted April 4, 2023 Author Report Share Posted April 4, 2023 Thanks Roger, The one I received with the upgrade is readme11x-14x and that's the one I've been using. Is that the current one and is there a specific one I should be using? Nick Quote Link to comment Share on other sites More sharing options...
theKiwi Posted April 5, 2023 Report Share Posted April 5, 2023 10 hours ago, Nick W said: Thanks Roger, The one I received with the upgrade is readme11x-14x and that's the one I've been using. Is that the current one and is there a specific one I should be using? Nick It's not so much a matter of the "current" one, but more of finding the one that includes what you had apparently missed at some stage when the name of the file offset field was changed. If you're still having problems, try the upgrade from 10x to 14.0.1 and see if that makes a change to the database that hasn't already been done. Roger Quote Link to comment Share on other sites More sharing options...
Nick W Posted April 5, 2023 Author Report Share Posted April 5, 2023 Thanks Roger, I'm thinking needles and haystacks here and maybe the best way is to get Darrin to re-do the upgrade. At least then I'll know for certain that everything is where it should be and if he can't fix this gedcom import function it would indicate it to be a problem with the host. I still have this nagging feeling that the SQL database upgrade they did might be responsible and something hasn't transferred across properly. Many thanks to everyone for their help in this matter. Much appreciated. Nick Quote Link to comment Share on other sites More sharing options...
FGvM Posted May 6, 2023 Report Share Posted May 6, 2023 Just upgraded to 14.0.2 Export gedcom dont function TNG/admin_gedcom2.php is in the line of the browser Message on screen: cant connect to the webside - closed connection unespected Quote Link to comment Share on other sites More sharing options...
Ken Roy Posted May 7, 2023 Report Share Posted May 7, 2023 Did you clear cache or do a Forced Reload to get the latest js and css files? Quote Link to comment Share on other sites More sharing options...
FGvM Posted May 10, 2023 Report Share Posted May 10, 2023 On 5/8/2023 at 1:31 AM, Ken Roy said: Did you clear cache or do a Forced Reload to get the latest js and css files? Yes, and Darrin has tryed to with same result My Web-host is now working on this issue Quote Link to comment Share on other sites More sharing options...
mycroft Posted June 26, 2023 Report Share Posted June 26, 2023 @FGvM Have you managed to resolve your case? If so, what was the workable solution? Quote Link to comment Share on other sites More sharing options...
Nick W Posted June 27, 2023 Author Report Share Posted June 27, 2023 I contacted Darrin and he sorted it out. I think it was a bug associated with the saveimport table. I've attached the saveimport table as it was prior to Darrin fixing it and as it is now and fully functioning. The only two things I can see which are different are row 6 where fileoffset is now foffset and row 10 where offset is now fileoffset. If you are having the same problem I was then you could try changing these two rows to the new values. If that doesn't work then I would think contacting Darrin would be the best option as there may have been other fixes applied which I am unaware of. Best regards, Nick Quote Link to comment Share on other sites More sharing options...
Ken Roy Posted June 27, 2023 Report Share Posted June 27, 2023 3 hours ago, Nick W said: I think it was a bug associated with the saveimport table More likely this was caused by failure to do a database upgrade step some time in the past. I do not remember when the column name was changed Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.