Your style should still be intact in the pre-Justin backup, but he's been very slow to fix problems and completely silent on what's been fixed, so you should re-upload it if you can instead of waiting.
Err, I've literally just seen this and it looks like I missed some stuff that went down.
I've noticed my theme has been cut off in places, resulting in it being broken. So will I have to redo the missing portions of the theme, or will this be fixed?
Edit: Nvm, funnily enough I remembered the freestyler site that rips styles from here and it still had the code from my last update, unbroken.
When one has like 100 dark themes for all the websites used daily, having a solid stylish add-on and updates is essential. Let's hope all these corrupt styles get a fix and or stylish gets good solid useful updates. Always moving forward >> is the only way.
Hi, sorry it took me time to reply. I usually prefer to answer when I have actual information to share. Just so you'll be in the loop, I'm still going over the migration, trying to look for possible discrepancies that could be the cause of any or all of the remaining issues (which I'm still mapping). I'll be working on this throughout the weekend and hope to have some news for you sometime next week.
For now you should know that it's safe to upload new styles. Some uploads of updates might still have issues.
Please be patient and take under consideration that I’m not Jason and all this is new to me. I'm still learning the infrastructure.
Hi, sorry it took me time to reply. I usually prefer to answer when I have actual information to share.
You have had; you just don't recognize it. "I'm (not) still working on it", "Not this week", "I do(n't) have a plan", "I can('t) say went wrong with the last plan", etc. It's all actual, actionable information.
Please be patient and take under consideration that I’m not Jason and all this is new to me.
We do. But, we don't know you, so we can only guess how much patience is needed. Personally I worry that you'll reprise "The Sorcerer's Apprentice" when the wheels fall off again (they will, sooner or later). This time instead of a three-hour detour we've been stranded on "Gilligan's Island." Next time ...?
Quick update: I see that the current MD5 is not matching the MD5 in the DB for this list of 3700 styles (1,400 of them are obsolete): https://clbin.com/SYoi0
The style code seems to be ok, which leads me to believe that the issue is with the style setting rules, which got corrupted during the migration. If anyone here is the owner of one of these styles, let me know if you can confirm this.
I couldn’t find a pattern explaining why those specific styles were effected. If anyone sees one, feel free to share.
I’ll get back to you about the possibility of retrieving this data.
My style has fixed, thanks, but it looks like updating of styles doesn't work in Chrome and Opera. It says "Update completed", but code of the style remains old. Stylish is finding new updates over and over, but can't install them. In Firefox and Safari everything works well.</blockquot
I see that the current MD5 is not matching the MD5 in the DB for this list of 3700 styles (1,400 of them are obsolete)
So strange. No style created after Jun 15, 2013 (id > 89124) is in the list, but some styles updated after Jun 15 (89124) are included.
I spot-checked four of those styles (881, 89052, 89097, 89124) and the .md5 file and the .json originalMd5 value both match the md5 of the .css file. Do you mean that styles.md5 has a different value than these, or did you already update the user-facing files?
The style code seems to be ok, which leads me to believe that the issue is with the style setting rules, which got corrupted during the migration.
I'm confused. I understand how the bulk of a blob or longtext might be left behind when files were copied, but how could the md5 (char(16) [1]) be corrupted but not the other metadata in the same record?
Also, the last several styles in your "bad hash" list don't have any style settings.
My style has fixed, thanks, but it looks like updating of styles doesn't work in Chrome and Opera. It says "Update completed", but code of the style remains old. Stylish is finding new updates over and over, but can't install them. In Firefox and Safari everything works well.
This is an old issue, as far as I know, that was fixed. I just checked again and it works fine. Can you explain where you still see it?
The Chrome Style Manager built-in update function is a separate, older issue. The fix has been sitting on Github for many months now, but Jason never pushed an update. He wasn't kidding when he said he lost interest.
The Chrome Style Manager built-in update function is a separate, older issue. The fix has been sitting on Github for many months now, but Jason never pushed an update. He wasn't kidding when he said he lost interest.
Got it. So yeah, I'm definitely planning to release a version with this very soon, together with some other cool stuff I think you'd like. I'm also going to share with you my ideas fir future improvements and let you vote on it. I just want to make sure we're over the bump of these migration issues before I move forward.
I see that the current MD5 is not matching the MD5 in the DB for this list of 3700 styles (1,400 of them are obsolete)
So strange. No style created after Jun 15, 2013 (id > 89124) is in the list, but some styles updated after Jun 15 (89124) are included.
I spot-checked four of those styles (881, 89052, 89097, 89124) and the .md5 file and the .json originalMd5 value both match the md5 of the .css file. Do you mean that styles.md5 has a different value than these, or did you already update the user-facing files?
The style code seems to be ok, which leads me to believe that the issue is with the style setting rules, which got corrupted during the migration.
I'm confused. I understand how the bulk of a blob or longtext might be left behind when files were copied, but how could the md5 (char(16) [1]) be corrupted but not the other metadata in the same record?
Also, the last several styles in your "bad hash" list don't have any style settings.
tl;dr: The data doesn't seem plausible, and the explanation doesn't apply to the styles in the dataset.
Comments
Why using PM when the answer will benefit all scriptwriters/users ? :bz
My theme is no longer working if I choose embedded fonts, it used to be working fine.
I've noticed my theme has been cut off in places, resulting in it being broken. So will I have to redo the missing portions of the theme, or will this be fixed?
Edit: Nvm, funnily enough I remembered the freestyler site that rips styles from here and it still had the code from my last update, unbroken.
For now you should know that it's safe to upload new styles. Some uploads of updates might still have issues.
Please be patient and take under consideration that I’m not Jason and all this is new to me. I'm still learning the infrastructure.
I see that the current MD5 is not matching the MD5 in the DB for this list of 3700 styles (1,400 of them are obsolete):
https://clbin.com/SYoi0
The style code seems to be ok, which leads me to believe that the issue is with the style setting rules, which got corrupted during the migration. If anyone here is the owner of one of these styles, let me know if you can confirm this.
I couldn’t find a pattern explaining why those specific styles were effected. If anyone sees one, feel free to share.
I’ll get back to you about the possibility of retrieving this data.
I spot-checked four of those styles (881, 89052, 89097, 89124) and the .md5 file and the .json originalMd5 value both match the md5 of the .css file. Do you mean that styles.md5 has a different value than these, or did you already update the user-facing files? I'm confused. I understand how the bulk of a blob or longtext might be left behind when files were copied, but how could the md5 (char(16) [1]) be corrupted but not the other metadata in the same record?
Also, the last several styles in your "bad hash" list don't have any style settings.
This is fixed.
Google Chrome version: 54
OS: Windows 10
You can only update directly on the style page.