In addition I can tell that for me:
This works: http://newsroom.lds.org/ldsnewsroom/eng/
This does NOT work: http://newsroom.lds.org/
The last one is the one that end up pointing to http://policypoint.ldschurch.org/policypoint
If would be interesting to see if those for who the second link works could clear their cache and see if theirs still work afterwards
If not then there must be something in the web page script. Could it be its trying to be clever to detect which country we are from (hence why its working for some and not others)??? I am just guessing now.
Are there members of the lds.org team reading these messages??? It would be a comfort to just see an acknowledgement.
Link to newsroom.lds.org links to nonexistent page on lds.org
-
- Community Moderators
- Posts: 427
- Joined: Mon Sep 10, 2007 1:29 am
- Location: Alnwick, UK
- WelchTC
- Senior Member
- Posts: 2085
- Joined: Wed Sep 06, 2006 8:51 am
- Location: Kaysville, UT, USA
- Contact:
I'll make sure that they do read these posts.dkjorgi wrote:In addition I can tell that for me:
This works: http://newsroom.lds.org/ldsnewsroom/eng/
This does NOT work: http://newsroom.lds.org/
The last one is the one that end up pointing to http://policypoint.ldschurch.org/policypoint
If would be interesting to see if those for who the second link works could clear their cache and see if theirs still work afterwards
If not then there must be something in the web page script. Could it be its trying to be clever to detect which country we are from (hence why its working for some and not others)??? I am just guessing now.
Are there members of the lds.org team reading these messages??? It would be a comfort to just see an acknowledgement.
Tom
-
- Church Employee
- Posts: 4
- Joined: Wed Aug 13, 2008 10:24 am
-
- Community Administrator
- Posts: 34490
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
-
- Church Employee
- Posts: 4
- Joined: Wed Aug 13, 2008 10:24 am
[font="]I ran into this issue with an area (don’t remember which, but it wasn’t local) Public Affairs missionary couple. After checking into it, the prompt is coming from something to do with LDS Accounts. I'm pretty sure they ended up putting in their LDS Accounts username and password and it let them go to Newsroom. [/font][font="]As far as I could tell, it has nothing to do with Newsroom. So far, I've only seen this issue show up behind the Church's firewall.
[/font]
[/font]
-
- Community Moderators
- Posts: 427
- Joined: Mon Sep 10, 2007 1:29 am
- Location: Alnwick, UK
Kim, no church firewall here, just the company I work for.Kim S. wrote:Are you guys behind the Church's firewall or checking Newsroom.lds.org from home?
Funny enough its working for me at home but not at work.
Ok the first anyone will say is that it must be my works firewall but they are obviously pointing to lds.org as the site redirecting to the policy link.
-
- Senior Member
- Posts: 773
- Joined: Tue Jan 23, 2007 2:03 pm
From the first time I posted until two nights ago, clicking on a link directly to the Newsroom either from the homepage flyout, or the link on the left on the 'Around the Church' page gave me the error.
Tonight I tried it with the 'www' in the URL as I had before, and found it worked right, and the URL is resolving as normal to the Newsroom page.
What appears to have happened is the server was not recognizing URLs with the 'www' before newsroom.lds.org until someone fixed the problem and that appears to have been done in the last two days.
Did all mine from home going straight to the page via links, no other special access was used, such as LDS Accounts, etc.
Tonight I tried it with the 'www' in the URL as I had before, and found it worked right, and the URL is resolving as normal to the Newsroom page.
What appears to have happened is the server was not recognizing URLs with the 'www' before newsroom.lds.org until someone fixed the problem and that appears to have been done in the last two days.
Did all mine from home going straight to the page via links, no other special access was used, such as LDS Accounts, etc.
-
- Community Moderators
- Posts: 427
- Joined: Mon Sep 10, 2007 1:29 am
- Location: Alnwick, UK
Its great to see the lds.org team is now looking at the problem because the behaviour has now changed. Here is an update:
As of now the situation for me on lds.org is this:
When I hover over "News and Events" and then click on "Newsroom" then the link is http://www.newsroom.lds.org/
When I click on "News and Events" and then on the next page click on "Newsroom" then the link is
http://www.lds.org/newsroom
Both of these now return a different message from the previously reported one. The message is from our network is:
"Network Error (dns_server_failure)
Your request could not be processed because an error occurred contacting the DNS server. The DNS server may be temporarily unavailable, or there could be a network problem"
Both of them are now sitting at http://policypoint.ldschurch.org/policypoint but this time it took longer to get there whereas before it returned the previous error almost instantly. Not this time.
The more direct link of http://newsroom.lds.org/ldsnewsroom/eng/ still works fine.
I hope this will help tracking down the problem.
As of now the situation for me on lds.org is this:
When I hover over "News and Events" and then click on "Newsroom" then the link is http://www.newsroom.lds.org/
When I click on "News and Events" and then on the next page click on "Newsroom" then the link is
http://www.lds.org/newsroom
Both of these now return a different message from the previously reported one. The message is from our network is:
"Network Error (dns_server_failure)
Your request could not be processed because an error occurred contacting the DNS server. The DNS server may be temporarily unavailable, or there could be a network problem"
Both of them are now sitting at http://policypoint.ldschurch.org/policypoint but this time it took longer to get there whereas before it returned the previous error almost instantly. Not this time.
The more direct link of http://newsroom.lds.org/ldsnewsroom/eng/ still works fine.
I hope this will help tracking down the problem.