Skip to content
This repository has been archived by the owner on Aug 30, 2018. It is now read-only.

Nothing Works !!! #2410

Open
deathline94 opened this issue Apr 25, 2017 · 2 comments
Open

Nothing Works !!! #2410

deathline94 opened this issue Apr 25, 2017 · 2 comments

Comments

@deathline94
Copy link

Hey . it apears that youtube updated its code , couse suddenly nothing works for me .
im using the latest DEV version (548) . anyway , this is my debug log :

https://pastebin.com/qnHtANmR

@JohanPirlouit
Copy link

JohanPirlouit commented Apr 26, 2017

Hi, read and post in #2408, "Completely broken on Firefox, likely due to recent YT UI update", because we all have this issue ;-)
Regards

@CollinChaffin
Copy link

Issue: YTC in TamperMonkey on Chrome Broken

For those on Tampermonkey Chrome (I'm on TM stable - Chrome DEV x64 but should work on all), here is a workaround I have come up with that I can now confirm works 100% of the time - until the perm updates can be made:

Because of the size and parsing issues from local file URL with TM, you will need to perform the following steps below. This is to avoid having to increment the version number which will just cause issues later when @YePpHa can make the updates. You should already know how to perform a local TM full backup but if you do not - "Utilities" tab, check the box for "Include Tampermonkey settings", and click on the "File"/"Export" button and select a local zip file. You will use this below and should also keep a copy aside as a backup.

Workaround Steps to Re-Enable YTC

  1. Open the fresh backup zip
  2. Sort by file name and click CTRL-A hold CTRL and DESELECT ONLY the THREE files titled "YouTube Center Developer Build.XXX"
  3. Press DELETE to now leave only the THREE "YouTube Center Developer Build.XXX" files in the zip
  4. Drag/Extract and Edit the "YouTube Center Developer Build.user.js" with an editor capable of performing a single REPLACE ALL operation to replace all occurrences of "con.log" with "console.log" (minus the quotes) and save the file
  5. Drag the edited/saved file back into the fresh backup zip to perform an UPDATE of that file with the edited version and exit/close the zip
  6. Go to the TamperMonkey "Utilities" tab, "Zip" section, "Import" and "Choose File". Select the above edited zip file.
  7. A new TM window opens showing you a restore will be performed and should ONLY LIST the "YouTube Center Developer Build.XXX" files
  8. Click IMPORT button at top of window - THIS FINALLY ALLOWS A PROPER OVERWRITE WITH LOCAL YOUR LOCAL EDIT via a "restore"
  9. Verify that the newly imported FIXED version is present and ENABLED in your script list
  10. Navigate to youtube.com and all should again be working

Additional Information - Future Updates

In all my tests with various builds for some reason (I believe the sheer size of YTC script) is causing TM to crash/close the local import to simply overwrite with a locally edited version (and unless you manually increment the version num, TM will just overwrite you edits soon, anyway). The only working workaround I found which I believe also provides confirmation of a bug in the TM code is that the "restore" code routine is running a modified routine that properly pulls it back in to overwrite the internet-based source - unlike other smaller scripts this is the ONLY method I found that works in my testing.

Also, using my method above will NOT have any negative impact whatsoever on future updates. In fact, you can clearly see the original URL source that YOU HAD ORIGINALLY INSTALLED FROM remains unchanged - we are simply performing a local edit and the very next incremented release at the original URL will simply overwrite these fixes (so you may want to set updates to manual and VERIFY that this issue is fully resolved before manually allowing any updates to this script for the time being). This is basically "tricking" TM that does not actually perform any actual code checking and until it sees a newer version number, has no idea the "restored" version does not match the online version with the same version number.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants