jackpot posted:

I'm new to Macs and don't even know where my profile is saved, can someone just reply when a new version comes out so I can reinstall and get rid of this damned error message that pops up with every page?

Mr Crucial posted:

I'm getting a weird bug where if I try to go to the next page in the thread, for some reason it always loads about halfway down the page so I have to scroll back up to the top to begin reading. I don't know whether it's SALR, Firefox or the forums that is doing this. I'm on SALR v 1.99.080518 and FF 2.0.0.14, but it also seems to happen with my other machine with FF3 RC1.

Anyone have any ideas?

Demented Footstool posted:

It seems with the new forum version, the "new post" link now goes to a url like ?noseen=0&threadid=2571027&pagenumber=33#pti30 , which messes up the paginator. Clicking on the arrow to go to the next page, it passes the anchor along, resulting in Firefox jumping to the location rather than the top of the next page.

I'm using SALR version 080518 with Firefox 2.

duz posted:

Yeah, the paginator just copies the url, it needs to be changed to remove the anchor.

maketakunai posted:

Couldn't find anything on this, so..

In Firefox 2, hitting Alt-A when Find is open [un]checks "Highlight all" and overrides SALR's dropdown menu shortcut key. Is there a way to change it so SALR has precedence or that highlight all doesn't have Alt-A as a shortcut key?

Demented Footstool posted:

Edit: I read it wrong... I'm not sure what you're having an issue with.

ClydeUmney posted:

All right, I've read through the last couple of pages, and didn't see anything about this. If I missed it, please feel free to flame the poo poo out of me.

Every time I look at a single post since the new forum update, I get the following error message (click for larger):



The page seems to load fine, but SALR doesn't load for that page. So, it's more of a nuisance than anything, but I still wonder why.

astral posted:

The fix will be in the next nightly. See: http://forums.somethingawful.com/showthread.php?action=showpost&postid=343865802&forumid=22

astral posted:

The fix will be in the next nightly. See: http://forums.somethingawful.com/showthread.php?action=showpost&postid=343865802&forumid=22

duz posted:

Which is out now!

heiden posted:

[url =https://wi.somethingawful.com/ab/ab3b96a5b674c118f82b72647abb42778354366a.png]when accessing the fyad index[/url]

[url =https://wi.somethingawful.com/35/35bd5b1c2ceab88e28fcfcd68b519edecce6ecbf.png]when accessing a fyad thread[/url]

pik_d posted:

I'm getting this in this thread. I think it only started after your last post duz, though I'm not 100% certain on that, also I tried a few other random pages and it didn't happen. The FYAD thing happens to me too, did genericadmin just change something that broke stuff?

Nolgthorn posted:

Where is the link to the newest release? Not one works for me right now, thanks.

Nolgthorn posted:

Where is the link to the newest release? Not one works for me right now, thanks.

pik_d posted:

tools -> add-ons -> find updates

pik_d posted:

EDIT: Well after uninstalling and deleting some stuff in my Firefox profile it seems to have gone away. Seems like a crappy work around though.

jackpot posted:

Yeah, same here. I didn't like doing it (wish I'd known which file kept my saved passwords - bye bye!) but it worked. This is a small point that mac users probably already know, but don't delete the folder, just delete the files. Deleting the whole folder kept Firefox from opening because it thought it was already open. Somehow.

GobyWan posted:

Hijacking this thread over Opera SALR again: it's stopped working for me unexpectedly on Opera 9.27.

jegHegy posted:

Go back to 9.2x, 9.5's new security policies do not permit running Opera SALR the way it ran before.

PS: See the Opera 9.5 Beta thread for further info on why it's breaking.

jegHegy posted:

I've added the "Starred Threads" item to the pinned list in the SA menu, and the submenu shows up empty (says No have no threads starred [sic] ).

Enlighten me?

RedKazan posted:

Sorry about the typo, but if you are wondering why you have no threads listed, it doesn't use your SA accounts bookmarks, it uses an internal list of threads that have been marked with the "Star This Thread" option in the context menu.

jegHegy posted:

Any thoughts on the performance issue? Is it a known problem?

duz posted:

Yep, the showthread handler needs to be rewritten to be more like the forumdisplay one. It'll all get done eventually.

Bucket Joneses posted:

Is there a way to clear stored SALR settings? No matter what I do the extension gives me a huge JS error whenever I load a page.

moho/Operaman/Dr Videogames whatever/Dastardly Repressed posted:

What is it?
It's just like the Firefox SALR, but for Opera. Opera doesn't have extensions like Firefox, but using Opera's UserJS and a small webserver-like daemon, we can get something close. The original Opera SALR was written by ctz, but that version doesn't work any more so you're stuck with my new one.

[pictures and crap omitted]

FOR NEW USERS - Step-by-step install process!

1. You must be using Opera 9. I've been using the latest weekly build, but any build should work as long as it's v9. If you're upgrading from Opera 8, make sure to either install Opera 9 in a new folder, or backup your Opera 8 folder beforehand. These are betas/weeklies, after all.

2. Extract the entire contents of the zip to a folder somewhere (specifically your UserJS folder). If you don't have a UserJS folder set up, just make a folder somewhere and extract the zip to it. Then tell Opera to look in that folder. Tools -> Preferences -> Advanced tab -> Content tab -> JavaScript options... -> User JavaScript files -> Choose... (pick the folder). Obviously do not try to run both new and old versions of SALR at the same time, make a new folder for Opera 9.

3. Next, start the daemon. There are two versions packaged, 'background' is just like the old one and will run invisibly until you manually end its process. Just run that one unless you're having problems and need to see error messages, etc.

4. Open salr2_main.js in a text editor. At the top of the file you'll see a couple of lines like:

code:

this.saName = 'moho';
    this.postsPerPage = '40';

Change those variables to match your username (which is case-sensitive) and posts-per-page count. Save and close the file.

5. Restart Opera. Now everything should work. You may want to create a shortcut to the background daemon in your "Startup" folder in the Start menu, so that the daemon automatically starts with Windows. Otherwise you'll have to manually start it each reboot.

FOR UPGRADING USERS - How do I upgrade SALR?

Always shut down the daemon using Task Manager before upgrading, even if the daemon version isn't changing. Next, extract all the files from the new archive, overwriting the old ones. BUT--DO NOT OVERWRITE __salr_hash.js! If you do that you'll lose all your saved thread data. Don't ignore the /img folder either, it contains important, often-updated files. Remember to open salr2_main.js afterwards and edit your username and options at the top of the file. Finally, once all the new files are in place, restart the daemon.

If you notice weird appearance/behavior after upgrading, you may need to clear Opera's cache so that it reloads the CSS and image files SALR uses. Opera caches certain things very aggressively, and just hitting F5 often isn't enough.

If you edit files other than salr2_main.js during the course of your install, remember that upgrading will overwrite them too, so be careful. Obviously I don't know what images/files you've changed and shouldn't overwrite, so keeping track of that is up to you.

I use Linux or MacOS or something. Help?http://mars.illtel.denver.co.us/~abelits/sa/software/salrd2/salr2r4-unix-1.1.tar.gz

The UserJS part of SALR should work fine on any OS. The daemon is written in D (Windows version compiled in dmd), and will have to be compiled for your OS. teapot has graciously provided ports of the latest daemon for Linux:

source
Linux binary

Users of MacOS or other operating systems may be able to compile using GDC. Be sure to let us know if this works for you.

Alternatively, see the following section.

The daemon keeps crashing, is there an alternative?
There is now an alternative and much more stable version of the daemon, written in ruby. For details on how to convert your thread data and install this version, see my post here: http://forums.somethingawful.com/sh...6#post324896626 [see below if you don't have archives]. Also users of other operating systems that can't run the regular daemon should be able to run this one, provided ruby is available.

I just installed this but it doesn't work properly or even at all...!
The forum template is updated often these days, meaning SALR must be patched every so often, and each patch does not get a full release package. I suggest reading the thread backwards from the last post in order to find links the most recent update (which usually consists of updated replacement versions of 1 or 2 files).

moho/Operaman/Dr Videogames whatever/Dastardly Repressed posted:

EXPERIMENTAL ALTERNATIVE DAEMON FOR PEOPLE EXPERIENCING CRASHES

Sup guys, okay, first of all if you are not experiencing daemon crashes you don't need to try this new daemon at all. Personally my crashes are getting so bad they're happening about 10 times a day so in my case it's worth it.

What I've done here is a basic port of the daemon to ruby, with some changes that hopefully make it more stable. Therefore to run the experimental new daemon you need to have ruby installed. I see no reason why this shouldn't work on any platform ruby exists for, meaning MacOS dudes may be able to run this now too.

Here's a step-by-step breakdown of what you need to do to run the experimental ruby daemon. Be very careful to read and follow every step:

1. Install ruby. I use Windows to I just went over to http://www.ruby-lang.org/en/downloads/ grabbed the 1.9.0 binary and installed it somewhere, it's only about 10mb and doesn't pollute your PC or anything since it's just a zip.
2. Make sure ruby works. Just go to the command line and type like "D:\ruby-1.9.0\bin\ruby.exe -v" (obviously use your own install path) and make sure you get some output.
3. End the process of the current SALR daemon (salrd_background.exe) if you're running it.
4. Go to your SALR directory and back up __salr_hash.js, because it will be changed.
5. IMPORTANT NOTE: The daemon looks for its files in the current working directory, so make sure you cd to your SALR folder in the command line and just specify the full path to ruby.exe when you need to run it. So for example your command line should look like: "C:\Program Files\Opera 9\salr>D:\ruby-1.9.0\bin\ruby.exe blah.rb" if you were to run a file called blah.rb which is located in your SALR folder.
6. Download convert_drb.rb and put it in your SALR folder.
7. Run convert_drb.rb using ruby, for example like: "C:\Program Files\Opera 9\salr>D:\ruby-1.9.0\bin\ruby.exe convert_drb.rb"
8. It should only take about half a second to run and won't print anything, but you should probably notice the filesize of __salr_hash.js change a little as the convert script makes some minor adjustments. You only ever need to do this step once, it's just some preparation for the slightly different ruby daemon.
9. Download daemon.rb and put it in your SALR folder.
10. Run daemon.rb using ruby, for example like: "C:\Program Files\Opera 9\salr>D:\ruby-1.9.0\bin\ruby.exe daemon.rb"
11. Okay, the daemon should now be running and spamming your console whenever it saves thread info etc.

If you feel all advanced and want to run it in the background in Windows (no console window) then you need to do just 2 things. First, open daemon.rb in a text editor and uncomment the first line by removing the # character in front of it. Then, when you run the script use rubyw.exe instead of ruby.exe. The daemon should create a log file in this case.

If anyone actually bothers to do all this, let me know if it works or doesn't or whatever.

Edit: One of the changes in the current daemon is that it'll only ever write its data file once every 3 seconds at most. Now, I *think* this is going to be fine in 99.99% of cases, however if you notice weird behavior where things don't seem to update fast enough or in the right order or something, let me know because there might be some situations I didn't think of.

Edit 2: Also a new salr2_main with some minor updates on mod handling and other stuff is in the works, however one thing at a time for now.

quote:

Regarding daemon instability, if you're experiencing this to the point that it annoys you, make sure to read the last page or whatever it is where I posted the ruby daemon. Admittedly it's a little harder to use but it's also 100x more stable, seeing as I've never had a crash with it yet (and I was having a lot of crashes with the D version).

Also about the post-favourites idea, its an interesting concept (I'd probably use it myself if it worked well enough) and probably doable with the daemon, but it'd also be a pretty big project most likely and is generally outside of the scope of what I'm doing with SALR right now.

Regarding suppressing image loading in the reply view, this is probably pretty easy actually but I haven't looked into it yet. I added it to the to-do (aka to-try) list anyway.

There is actually a new WIP version up but literally the only change is that I added link rels to the forum view so doing a forward gesture/fastforward will generally take you to the next page now. Back is a bit iffy though cos there's some weird Opera "rewind" behavior unless you explicitly use the rel links via Ctrl+Shift+Left/Right or the Navigation Bar's buttons. If you don't care about this there's no reason to upgrade.

Furthermore I uploaded some miscellaneous SA-related UserJS files I wrote at various times for anyone interested, they're located here: http://junk.ionmine.com/salr2/misc_userjs/

Breifly:
- casaoswap makes the bottom page ad appear below the page links rather than above them.
- letsplaylink adds a link to Let's Play as a Games subforum
- leper turns the Leper's Colony into a rainbow of colour coded probation durations and mod/admin names and such.
- forumpin lets you define a list of forums/subforums to appear above GBS at the top of the main forum index (so you don't have to scroll around to find the forums you usually visit). You kinda need to be able to figure out how to edit a Javascript data structure to use this since that's how it's laid out at the top of the file.

GobyWan posted:

Hijacking this thread over Opera SALR again: it's stopped working for me unexpectedly on Opera 9.27. Nothing really caused it, it just quit doing anything at all - it's like I never installed it. I reinstalled the daemon.rb file and now the daemon won't even load anymore - daemon.log says this:

code:

daemon.rb:5:in `require': no such file to load -- base64 (LoadError)
	from daemon.rb:5:in `<main>'

Reinstalling Ruby 1.9.0 also didn't help. I vaguely remember having to change something in daemon.rb to get it to work when I first installed it, but the original thread is long archived and I don't have archives access. Anyone know what to do?

RedKazan posted:

Dastardly Repressed posted:

For starters I think various changes in 1.9.0 (final) have made the daemon incompatible, for one thing "base64" is no longer part of the standard library. My recommendation is to just run it with 1.8.6, 1.8.7 may also work but this is untested.

Assuming you get the daemon running and still nothing works in 9.27, first thing to try is load up a thread and type "java script:alert(window.SALR);" (remove the space) in the address bar and see if it shows you a huge rear end bunch of code. If you see code it means at least SALR is loaded, otherwise not. If you see code, next thing to check is is the daemon is running right by loading up http://localhost:55055/page.css or similar. Also checking the Opera error log is probably a good idea, as is seeing if any page changes are made before it stops working (e.g. addition of "1" and ">" links in the sidebar).


And yeah everything RedKazan posted is correct. As is the fact that 9.5 completely breaks Opera SALR in a way that's basically unfixable short of everyone hosting their own external proxy or some horrible bullshit like that. At this point pretty much the only ways forward are for Opera to add a bypass switch for the security feature that breaks SALR, or for functionality to be added to Opera itself that obsoletes the need to use the daemon.

GobyWan posted:

It really sucks that 9.5 prevents SALR from working properly, I want to eventually upgrade but I really rely on SALR and I don't want to switch to Firefox. Hopefully there's some way around that, but I really don't know where the priorities of the Opera dev team are (removing shell context menus from the transfers window? Really?) so I'm not sure they'll be in a hurry to change things for the sake of one addon.

Edit edit: Ok, stopping the daemon before I edit the hash file and then starting it again seems to have killed the problem, finally.

pik_d posted:

I've got a question for those of you who have been using Firefox3 beta/RC's, since I just got it today. With Firefox2 I would wait for the page to load, SA would make it jump to the first unread post, then SALR would resize some images causing it to not be at the first unread post. I would then click the green "enter" arrow to the right of the address bar which would make the page jump to the first unread post without reloading the page. With Firefox3, there's no green arrow, so how do you guys deal with this short of just scrolling to the post you want to be at?