AltoRetrato Author

Re: @mightysparks

A follow-up to my previous post... I didn't check here for a few weeks and when I came on my issue was closed

Just as Marti said, it would be better to check once in a while to see if there is a reply to any issue you open.

So apparently there's not enough space to post it all. I had 106 errors and 33 warnings. How should I share these?

First, it would be nice if you could describe your issue with some more details.

  1. Are you changing the script source code to add custom colors?
  2. Does color highlighting works with the original (unmodified) script code?
  3. When you don't change the code, or after you do a change (but NOT between two changes!), does highlighting behaves consistently the same way after you refreshes the data? Or does it behave differently (without you changing the code) when refreshing a couple of times?

To report errors, I'd suggest you to:

  1. Open the page where errors happen (e.g., "your lists" page)
  2. Open the Javascript console
  3. Clear the console (to remove other errors)
  4. Click the script's refresh button (or do the operation that triggers the error)
  5. Only then you should copy the errors. If the list is long, you can use a service such as http://pastebin.com or similar to paste the contents there and just post a link for it here.

Re: @Marti:

That would entail more cookies on your end and would need session forwarding

That is not necessary. Since I'm submitting a form, all data (i.e., the message content and URL) can be included in the sign in form as hidden fields (no session information nor cookies are required). After signing in, you redirect the browser to the previous URL, but including the message content in a new reply.


Re: @Marti:

Idleness is currently detected. If you don't initially navigate somewhere on the site you will be logged out within about five minutes with intendend behavior. So either type faster eg or visit another page first. ;)

Wouldn't it be much nicer to save the message and either submit it or go back to editing after signing in? The sign in page could have the message (and/or any other auxiliary data) in a hidden field form, as well as a redirection URL (so the user navigation could continue no matter why/where sign in was requested).

You do know you can click the line number for current published revision and get a link for that revision right?

Now I do! :) Thanks!


FWIW, this bug is a know issue since the day the latest Greasemonkey version was released, and seems to affect any update or new installation of any script including 'single quotes' in the name. If baffles me that such crippling error wasn't already fixed and a new version released!


I can confirm that my script doesn't run with Greasemonkey version 4.8. Thanks for bringing this to my attention. This issue is caused by a Greasemonkey bug, but there is a simple workaround:

  1. Click the Greasemonkey icon > IMDb 'My Movies' enhancer > Edit.
  2. Change the 13th line, removing both apostrophes (i.e., change 'My Movies' enhancer to My Movies enhancer).
  3. Click the "Save" icon (floppy disk at the top left corner).
  4. Reload https://www.imdb.com/mymovies/

I've never seen that type of error before. It is not a message emitted by my script, but by Greasemonkey - and it is not helpful at all (even its source code says it needs "Better indication of the root cause").

This is one of the reasons I'm currently rewriting this script as an add-on: one less puzzle piece to solve when there are problems...

Have you changed the source of the script? If so, I'd recommend to revert any changes or reinstall it first.

And what is your version of Greasemonkey? I've found I'm using 4.3 (according to about:addons), but it seems the latest version is 4.8 (which is only 18 days old)! I'll try the latest version soon.




I love OpenUserJS! I sign-in, write you a long reply and the site deletes it and asks me to login again... 🤦

Anyway, do you have any other IMDb related script or add-on installed? My script works for me on Chrome and Firefox. I suggest you to open a new tab, open the JS console, load https://www.imdb.com/mymovies/ , then copy-and-paste any errors and warnings here.


This looks more like a connection problem than a script problem (but I could be wrong). It would be interesting if you could open the Javascript console ([Ctrl]+[Shift]+[J]) and note if there are any errors or warnings there. If you find any, please share them here.


Please check the Javascript console. If you can't figure out the problem on your own, please share here any warnings and errors and I'll give it a try.



It seems that IMDb won't really have a check-in list for a user that never added anything to that list. You can't even edit it!

The new version of the script should handle this better, also telling the user at the end which lists (if any) could not be loaded. You can keep using it as is until you get the update automatically (v. 1.45), or force an update.

Please let me know if you find any other problem.


Hi, Dan!

Sorry about that. Here's the changes in the latest versions (up to 1.44):

  • 2018.07.03 [1.43] Added support for lists of people - but since I don't use this feature, I'll only see problems via bug reports.

  • 2018.07.05 [1.44] 10 year anniversary edition! :D
    Fixed bug from v. 1.43 where movie titles and people names were getting mixed.
    New default highlight color for lists of people.
    New & improved way to set color priority (search for listOrder).
    Now supporting check-ins list.

So, the script is reading one new list for you (check-ins), so that's why it shows one more during loading.

As for it not completing, could you tell me what appears in the Javascript console?


I think Monk-time is right. Until at least a few weeks ago, IMDb didn't seem to support https - it would always redirect to http when I tried.

I've just updated the script. The best / easiest solution for now is to use either the http or the https scheme. The script saves your data in the local storage, and the storage is different between http and https URLs. This means that if you use both schemes, you would need to download your data twice (and I don't think there's an easy fix for that).


Thanks for the link.

As I wrote before, I'd love to add a preferences tab so users won't have to update the source, but that's not my priority at this time. Maybe in the future...


You should check the Javascript console for errors, there might be something there to help you figure out the problem and fix it.

One thing I wanted to do was to save color information in the browser instead of in the code. Another idea was to (optionally) add emojis (as a prefix or suffix), but I never find the time to do that... I believe those features would be helpful to people who likes to customize their lists.


Re: @Marti: thanks for your reply. I know what you mean, but to be more precise, I don't plan to visit this site daily and manually check for open issues - I'd rather receive an e-mail notification, for example. A RSS feed with new topics and replies would work as well. Is there any chance for this to be implemented?


I can't find anything in my profile or settings on OpenUserJS related to notifications or RSS feeds, so I guess I'll write a script to monitor the site daily... That way I'll answer / fix things faster.


Fixed today with v. 1.41. Auto-updated worked with Tampermonkey on Google Chrome, you can try it by opening the Tampermonkey dashboard and clicking the "last updated" entry for this script.

BTW, I get no notification if someone posts a problem here. Does anyone know if there's a fix for that?



Hi everyone!

There were some changes in the last few days:

  • The "export link" for each list (which is used by my script) has been producing broken CSV files for a few years, causing the script to fail to refresh the data in some occasions (such as when a title have a special character). It seems this was finally fixed, but the file format have changed, requiring a script update.

  • The layout of Your Lists page was changed, requiring another update.

  • The "export link" for your watchlist is a bit "hidden" now, and the script have to download another page to be able to find your watchlist. BTW, if it seems that your watchlist is not being loaded, please make it public at least once: you can revert it to private right after that, but we need IMDb to give your watchlist an internal ID (and it might not do that by default for everyone, so that might require you to make the list public).

I just published v. 1.40 of the script, and tested on both Chrome and Firefox. To be on the safe side, clean you browser's cache after the upgrade then proceed to Your Lists and you should see the golden buttons.

Merry Xmas & holidays to all! And next year the script will celebrate its 10th anniversary, I'll let you know where we will celebrate! ;)


Sure, monk-time, go ahead - and thanks for asking! :)

I try to keep the script as simple and backward compatible as possible. I remember I could run it on my phone (a Nokia N900, some years ago), and I guess someone else might still be using old hardware / software that can't be updated.

BTW, I've just updated the script to v. 1.40.