AintNobody

I've done something that has effected the live site.😢 Things seemed okay, but even though I changed the dev sites conf_global to point to the right direction. I've caused issues on the main site. PS. Once upon a time we were promised one upgrade, I never used it. I don't suppose that still exists? 😂 That's a j/k.

Sorry, I remembered only after my last post. I need to disable the plugins, and apps. I'll report back in awhile when I have re-backed up and re-imported everything. I bet this is causing the upgrade issues. 🤦🏻‍♂️

I got a bit further: It's sleep time. Upgrade Status Status: 1 Application: gallery Current Version: 5000012

Next Up: "Table 'prideofn_test.core_content_promote' doesn't exist". I had followed @Gary's advice, but I have since imported the missing part. So, it's in my datbase. No idea why I am getting this error in the upgrader now.

I have located the v5 beta 9.1 files, I'm going to try upload those and see if I can get past this issue. 🙂 I didn't come across it previously, the upgrade process was flawless. So, hopefully this can shed some light on why I can't get past the core_reputation_index.

Thanks, @Gary. I'm encountering "ALTER TABLE `core_reputation_index` ENGINE=InnoDB, ADD KEY `item_lookup` (`rep_class`,`item_id`,`reaction`);" I have followed the steps you provided by deleting the promoted.php file and dropping the 'promote'.

No, I am getting the same message again. ALTER TABLE `core_reputation_index` ENGINE=InnoDB, ADD KEY `item_lookup` (`rep_class`,`item_id`,`reaction`); The database is new. The imported database is from my live site, which is unconnected to any v5 updates. 😞 I switched back to PHP 8.1, as I forgot that it had been changed.

Sorry, you caught me in the process of clearing and re-starting again. I can get past the previous part I said I couldn't in the v5 upgrader, but then I hit a 500-page error.

Initially, I dropped everything in my old database. I have since deleted my development site's database, created a new one, and uploaded the working database of my version 4.7 site. However, I am still getting the same message despite this being a new database. ALTER TABLE `core_reputation_index` ENGINE=InnoDB, ADD KEY `item_lookup` (`rep_class`,`item_id`,`reaction`); The new database has nothing to do with my previous version 5 database. As I said, it's a fresh backup of my live version 4.7.19 site. 😞

I did everything fresh, so I dumped and restored a new backup from my live site. I had v4.19 running fine, so I proceeded to download a fresh set of beta 10 files from the client area. I then uploaded, and tried to install the update. To clarify, you are telling me to dump "ALTER TABLE core_reputation_index DROP KEY item_lookup;"? I don't want to interrupt what you mean incorrectly.

I wish trying to upgrade (fresh) from v4.19 to v5 beta 10 was as straight forward. *Sigh

I'm having issues with the v5 beta 10 upgrader. I am being told to run: ALTER TABLE `core_reputation_index` ENGINE=InnoDB, ADD KEY `item_lookup` (`rep_class`,`item_id`,`reaction`); But I get:

I have started to restore a new backup of my live site, so that I can run the upgrader again. This can be closed. I'll open a new one if I encounter errors. Sorry, it has become too much hassle to remotely try to fix the beta. I also politely note that uploading files six times likely means the issue isn't with missing files. It could be related to folder accessibility or another factor, but it's certainly not due to files being missing unless they aren't in the source.

Can an IPS team member please clarify that extensions can be used for the checkout process in v5? My solution would be to work with @teraßyte. If that's not possible and a third-party developer can't restore the store functions removed in v5, I may need to find a different solution for my site.

For Dev sites, use. If you are 100% sure, I have found deleting the payment gateways in the test/dev area to be fine also. I don't think this would be recommended, but the code above didn't work for me due to my environment. It does if you are running NGINX.

I used the init.php from my backup before upgrading to v5. Is this safe? I assumed it would be okay since it was what I originally used. I'm afraid I still can't access the ACP, and the site is completely white. Could you please look at this new error log? It seems different from the first one and longer. Although it all goes over my head, if it turns out to be more of a headache, I'm happy to persist with repeating the upgrade from 4.7 to 5. https://www.noterip.com/view-note?Id=8c7ddb9b-d293-f995-c247-80574a29d375 -- Jim, You and the team work incredibly hard, and I appreciate your efforts. I don't wish to keep bringing things up, but I appreciate your response, apology, and explanation. I was trying my best to resolve the footer issue. I found the error, but I was only told that files were missing. Marc said, "You appear to be missing files and a table according to that message," which led me to check if the files were present. In hindsight, I believe the files were there, and something more complicated was happening. I'm not being difficult, but the response wasn't very detailed. I followed up with what I did, explaining that I uploaded fresh files, and at that stage, the site was still working with the footer error. I acknowledge that I could have been clearer, but when I saw the comment, "Please be respectful to those trying to assist you," about a simple emoji posted in frustration, it felt unjustified. I have documented my responses and what I have been doing. I never say I did something I didn't do, and I think it was clear the issue stemmed from the Beta 10 files I downloaded from the Client Area. I don't want to play the blame game, but I want to be clear that this has caused frustration on my end. I respect the team and love Invision as a product. I appreciate the apology and just want to move forward from this issue. Thank you.

Here's the server log: https://www.noterip.com/view-note?Id=4bdf531f-07c4-aa45-0dad-03c7892a47b6 It's password-protected, and that info is listed in my client area's notes.

I thought Invision might be interested, more so with the issues due to version, that it be bug, and my site only became inaccessible after downloading the v5 Beta 10. I find it weird the white pages and 505 errors came only after trying to make sure that there wasn't any files missing. Again, something which I reported but was overlooked. Why report errors, if dismissing the user or pasting a very generic response which is extremely unhelpful. I get that you guys are busy, I'm not remotely unreasonable but to take offence over frustration was rude. You guys are professionals, if a client isn't clear then please ask to clarify. Whilst I try to make sure I'm clear, I get that it might not come across that way. However, I was going in circles and again this is a place to report bugs and issues. Provided the majority aren't, I suppose that's fine but rudeness can be taken from my point of view too - especially when you repeatedly mention an issue only to be ignored.

I would not want to post any information publicly. Can you please escalate this further up the chain. Any information I am mindful about targeting by hackers.

Nothing I wrote was disrespectful. We're back to the generic responses, I have provided errors and generic replies were given. I have been asked if I had ran the upgrader, I have said my sites inaccessible before. I have mentioned that every step and actions I have taken without any practical support. Please don't try to be patronising, I've been more than fair.

It could be, but the previous download said 5 when I upgraded. I delete all files, so no previous ones are on my laptop. Not the zip's at least. 🙄

The 6th time of uploading fresh files and my dev site is still inaccessible, I won't be trying anything else because I am going out to a panto shortly. I would appreciate it if Invision could investigate this. This might be a rare issue, but I don't see why it's happening and even with a fresh set of files (multiple times applied) and now I can't even access the site. To be clear: I had an issue where the footer of v5 (I believe the mobile navigation) was throwing an error. I reuploaded files multiple times throughout this issue (6 times). I really hope that Beta 10 wasn't a 4.17, but whatever has happened could occur to my live site and since v5 is in beta almost in final. I would have thought this would be something a client might get a bit more help with.

Upgrading from v4.19 to v5's beta 9.1 was very easy. Despite encountering a few complications and errors in my dev site, the process of upgrading to beta 10 through the ACP was remarkably straightforward. (Issues concerning version 5 and theme-related elements).

@Marc: Uploaded the new files, my dev site is inaccessible now. I really hope the Beta 10 download wasn't 4.19, but it seemed to be correct. There wasn't a plugin folder. Could this please be looked into? It's not urgent, but it's apparent that something isn't right. I would very much appreciate it. It might be useful with V5. Just not note, I didn't download the v4.19 files. I clicked and downloaded the Beta 10 files, I then inspected them and it seemed right.

Aye, but I'm downloading v5 Beta 10. I am currently uploading a fresh set of files from the Beta 10 download. Hopefully, it will fix the footer issue, but I did this twice with the previous Beta, so I am not really certain it will make a difference. Thanks for confirming.