Jump to content

CannonFolly

Clients
  • Posts

    31
  • Joined

  • Last visited

Reputation Activity

  1. Like
    CannonFolly got a reaction from Miss_B in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    OMG, that did it!
    IT COMPLETED THE UPGRADE!!!!
    Don't take this the wrong way, but I could kiss you right now lol.
    Thanks for the reply. My host does have me on a MySQL VPS. Apparently this database was originally checking in at over 6GB for some reason, but all of the recent file checks have been varying between 20 to 200 MB.
    It looks like Adlago's query fixed it, so fingers crossed it was just corrupted and not a disk space issue.
  2. Like
    CannonFolly reacted to Miss_B in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Regarding the error mentioned in your screenshot: "Incorrect Key File for Table", it usually happens because of either a disk space issue or a corruption in the aforementioned table.
    The disk space issue is caused when the sql query is fetching data greater than the /tmp folder 's size. That 's the folder used for storing temporary tables btw. To fix this, you must change the folder location to a disk having enough free space
    The corruption issue can be be fixed with the query posted above. If that won't help, you can drop the table altogether from the dataabse then re create it and re insert the data.
    But if it is related to the disc space issue, it is best if you talked to your host about this, unless you manage your own vps/dedicated box.
  3. Like
    CannonFolly got a reaction from Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    OMG, that did it!
    IT COMPLETED THE UPGRADE!!!!
    Don't take this the wrong way, but I could kiss you right now lol.
    Thanks for the reply. My host does have me on a MySQL VPS. Apparently this database was originally checking in at over 6GB for some reason, but all of the recent file checks have been varying between 20 to 200 MB.
    It looks like Adlago's query fixed it, so fingers crossed it was just corrupted and not a disk space issue.
  4. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Have you tried this:
    In a list of tables in your database, select this table.
    Scroll to the bottom, under a list of tables in the drop-down menu With selected, select Repair table.
  5. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Once you swim in that stream, it will happen in a moment 🙂
  6. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Apparently there are more "bugs" here and there...One by one remove and you will see a finish.
  7. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    This is my table

    Create a row you are missing
  8. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Mark and delete 1_core_spammer row
  9. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Did you run an upgrader?
  10. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Try (1,core_NewVersion,1,always)
  11. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Replace ? with 0
     
  12. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Copy and Go this command in SQL
  13. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Try this
    ALTER TABLE ibf_core_pfields_data ADD pf_admin_only varchar(255);  
  14. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Try this:
    In this command, replace DROP with ADD
    This will create the missing column, then upgrader will successfully remove it.
    I.e. After successfully creating it, run upgrader
  15. Like
    CannonFolly reacted to Adlago in Errors trying to upgrade from 4.2 to 4.7 after switch to php8   
    Open your PhPMyAdmin - your database, open menu SQL
    Copy the last line in the red message, and paste in

    Then Go.
    Once done, repeat site/admin/upgrade
     
     
×
×
  • Create New...