If I attempt to link http://ref.ly/pr28.26;nasb I get an error:
Sorry, you don't have permission to view that book. (error 403)
Same for http://ref.ly/Pr28.26;nasb95which is what the twitter link on Biblia generates.
Same problem when using your links. I can open them manually on Biblia, but not the generated link. I am signed in.
UPDATE: How are you creating the link above? I hit the share button and the get the following link which works fine.
http://biblia.com/bible/nasb95/Pr28.26
Thanks Thomas, we'll get it fixed asap. This is happening because Bible.Logos.com only had the NASB '95 update available, but Biblia has both the old and new versions available. The ID for the old version is 'nasb', while the new one is 'nasb95'. Because of the conflict we just have to assume that 'nasb' really means 'nasb95', and redirect appropriately.
UPDATE: How are you creating the link above? I hit the share button and the get the following link which works fine
The ref.ly link is currently only used when you use the Twitter share link.
And honestly, I didn't use the twitter link creator until my hand crafted link kept failing. Hence both links listed in my first post.
UPDATE: How are you creating the link above? I hit the share button and the get the following link which works fine The ref.ly link is currently only used when you use the Twitter share link.
OK. Makes sense. Fewer characters.
The NASB / NASB95 issue should be resolved now. Sorry about inconvenience
Thanks,
Bryan
Bryan,
Even if I click refresh in my browser, the two links in my first post still lead me to the forbidden page.
[quote]
Is the NASB95 one of the bibles that isn't "free"?
The NASB95 is free, but the old NASB is not. Ref.ly was incorrectly forwarding both of your URLs to the old NASB, giving you the forbidden message.
I suspect your browser may have cached the redirect & is not actually asking ref.ly any more. Could you try either clearing your cache, or trying another browser that may not have cached the response?
Clearing the Cache did it. ODD: I thought that CTRL+F5 was supposed to force a real refresh. It didn't in FF.
Great
I thought that CTRL+F5 was supposed to force a real refresh
Ctrl+F5 will refresh your current page (probably this forum page) without cache. It won't clear your entire browser cache. We needed to clear the cached redirect that ref.ly sent your browser, which was what contained the incorrect Biblia URL.
