Gary, Lissa... Since the recent URL changes to the online campaigns section of the boards, I've found that lots of older links no longer work as they used to.
Used to go to the corresponding post on the correct page of the thread, however now it simply takes me to the first post of the PbP and shows the following URL in the address bar:
http://paizo.com/campaigns/WardovesRumbleInTheJungle/gameplay#1863
The desired/old behavior would have been to get taken here:
http://paizo.com/campaigns/WardovesRumbleInTheJungle/gameplay&page=38#1 863
Now if the server is able to forward/redirect the old URL path to the new one, I'm not sure why the page parameter would get dropped, but is there any chance this will get addressed (no pun intended)? I frequently cross-link between important posts in the forums and my wiki, and this just really made me go "Oof!"
On a side-note, is there any way we can link to a specific post by number without knowing the page it's on? Any insight into either or both matters would be appreciated. :)
Speaking of old URLs...
I'm not sure what's going on because my other lists are loading just fine, but for some reason my most important one (the table of contents for the first ~9000 posts of my PbP) is simply refusing to load. Without this working, it's become something of a ponderous task to reference and link back to prior posts — something I do all the time to keep important clues fresh in the minds of long-time players, and to bring newer players up to speed.
About 5-10 minutes after trying to load that list, I get the page with the Paizo golem stating that the store is down in spite of the fact that I can browse other lists and posts without issue.
Is there any chance you can salvage that list and maybe email me the contents? I have several days in man hours invested in maintaining it and it would be a nightmare to have to recreate it from scratch.
On a side-note, is there any way we can link to a specific post by number without knowing the page it's on?
Well, there's fifty posts per page, so if you know the post number, you ought to be able to divide by 50 and figure out what page number to plug into the url. For instance, 1863 / 50 = 37.26, so it's the 26th post on page 38.
Thanks for the pointer, Joana, but I'm trying to figure out if there is actual syntax to do that with only a single parameter rather than needing both. :)
e.g. ...&post=1863 or some such
ceiling( post # /50)? if you were writing program not sure how to implement that.
Wu: Yeah, I suppose I could write a script for MediaWiki to do that, but it would only be necessary if my ToC List really is lost to the void (i.e. in which case I'd have to rebuild it off-site). Otherwise, I'd really rather leverage functionality already built into this site.
I'll keep those suggestions in mind though if Gary and Lissa come back to me with bad news about my list.
PostMonster General
|
You're correct, we weren't properly putting the page number back into the URL for redirects, that will be fixed sometime this afternoon or tomorrow.
I don't see any reason your ginormous list shouldn't load properly, it works for me.
There's no "&post=<number>" for linking directly to an individual post in a thread since posts aren't super useful without the surrounding thread's context. I guess we could do a redirect or something but it's not a super high priority at the moment.
You're correct, we weren't properly putting the page number back into the URL for redirects, that will be fixed sometime this afternoon or tomorrow.
Cool, glad to hear it.
There's no "&post=<number>" for linking directly to an individual post in a thread since posts aren't super useful without the surrounding thread's context. I guess we could do a redirect or something but it's not a super high priority at the moment.
No biggie on this one, was just wondering.
I don't see any reason your ginormous list shouldn't load properly, it works for me.
Hmm, that's certainly odd. I just retried using IE 9 on my laptop and it loaded, same in Safari, FF, and IE on my desktop. It's also working in the stock browser on my friend's Droid.
The strange thing is that it craps out in both the stock and Chrome browsers on my Droid and Chrome on my laptop and desktop unless I logout sync and purge everything but passwords. Then it will load until I sign back into the Google sync. Mind you, all my other lists still load regardless.
Gotta love computers, right?
OK, it gets weirder still...
.
.
.
.
- I just signed out of Chrome sync on my desktop, laptop, and Droid
- Purged everything but passwords on all 3 devices.
- Blew away all synced data in my Google acct.
- Visit Paizo click on that list and it loads right up.
- Sign into my Paizo account, retry and it refuses to load the list.
- I sign-out of Paizo, retry and it loads.
- With that list on the screen, I try clicking the Sign In link at the top and it takes 2 minutes to load the sign-in page.
- After signing-in again, the list goes back to being unloadable.
As a test, went into IE, Safari, and FF, and it's the same there. If I'm signed into my Paizo acct the list simply will not load, yet so long as I'm signed out it's all good.
Also, in FF (which is what my roommate uses his Paizo acct in usually), if he's signed-in he can load that list just fine, but if I sign him out and login as myself, it refuses to load the list.
If you want to reset my password and try for yourself to see if you can replicate the behavior then feel free, but it seems to be specific to my Paizo sign-in rather than ISP, browser, or Google acct.
Roger that, I'll make certain to not load it again whilst logged in until you give the all-clear. Thanks for looking into it at this late hour!
Just checked and it's loading up properly now. Thanks so much! :)
Just out of curiosity, what happened, and is there anything I can do to ensure it doesn't recur? (Note that all new entries are going in a separate list so the one you just fixed should be largely static at this point.)
Hehe. Well to be fair, I did ask first. :D
Anyway, I am at once amused at my unintentional beta-testing, and grateful for the quick fix. Thanks again!