At this point I am less interested in figuring out “how it got damaged” - there are apparently no answers or solutions anyway. I am not even entirely sure which problems are connected. I am looking for the least invasive solution to restore and be able to move forward.
I received a notification for the problem of @modifiercontent, by clicking on the link to come read and help it I come across someone who is participating in the discussion to ask for help for another problem.
I am a new user and I knew how to read the rules and apply them without problem because we are well guided with information popups displayed throughout the forum to guide us through the steps. So no real error, especially since the response form can’t really be confused with the form to create a new message.
In short, it’s just a matter of respect. If he wants to have access to the functionality then who follows the steps as we have all done or you may have to delete the steps to allow the new member to participate in the forum as soon as they register.
My answer was not excessive but fair. It’s a pity that I have to troll the discussion to answer you on the other hand.
@Nick_J - I don’t seem to have that path on my server. My Bluehost VPS is configured via WHM/cPanel/EasyApache etc. I don’t think mariadb is used anywhere; it’s all mysql even if it presumably links to mariadb stuff.
I have /var/lib/mysql/username_mautic/ - CentOS default - with lots of .opt, .frm and .ibd files that Bluefish editor can’t read and in Notepad++ it’s lots of NULL NULL with gibberish sprinkled in. Googling now what this is…
FRM file is used by MySQL Server to store table schema and .IBD file is used to store data and indexes of a MySQL database .
You can only read these .frm and .ibd files “with MySQL”, so I guess somehow via command line or PHPMyAdmin? There is no Windows desktop MySQL client that would be able to read these files I guess?
@techbill, problems apparently start when you (try to) convert the database from MYISAM to InnoDB or/and change collation - utf8_unicode_ci or utf8mb4_sumthing_?
I think I’ve solved my original issue related to that, but my database is now a mix of InnoDB and MYISAM - some MYISAM tables won’t convert, not sure if I’d only cause more problems if I forced it somehow. Also not sure what recommended collation etc. is.
I am still curious to see an answer to the original question of this thread, how to do a clean surgical rebuild of the database without losing data and without having to reinstall everything.