No, the Upgrade::moveCSSFiles() didn’t move the files! But I’m trying in production now and after the first SQL I’ll see if it throws 0 affected rows again.
It worked when I manually moved one file and renamed it, and at least that way there is success.
Sorry to bother you: did Upgrade::moveCSSFiles() throw any errors/warnings? Could you tell me how was the file name before you manually moved it? – to see if something is wrong with the login in that function, so that I can improve/fix it…
THANKS!!!
Hmmm… for some reason the script did not find that genre again – the genre with key = STYLE for all journals… Do you have those default genres for each journal?
I only corrected the genres for this journal, didn’t change the others that had no keys too (and didn’t thought it would be needed now because this was the only case) But I’ll correct them all and try again!
@bozana, ran the fix and all files were renamed and migrated. HTML galleys and CSS are presented as they should! My mistake trying to solve it by half and wasting all this time.
Thank you for your time and patience looking at this!