Hi Jesse,

There are two settings in the config.rb file (in the config folder) that apply 
here:


AppConfig[:frontend_proxy_url]

For the url to your staff interface


AppConfig[:public_proxy_url]

For the url to your public interface


Update those and restart ArchivesSpace.


Best,

Mark


Mark Cooper
Technical Lead, Hosting and Support
LYRASIS
email: [email protected]
skype: mark_c_cooper
________________________________
From: [email protected] 
<[email protected]> on behalf of 
Teitelbaum, Jesse <[email protected]>
Sent: Wednesday, February 1, 2017 7:07:52 AM
To: [email protected]
Subject: [Archivesspace_Users_Group] "View Published" not resolving correct web 
address

After doing a test migration from ARCHON to AS (1.4.2), when I am logged into 
the staff interface, I can edit a RESOURCE.  I have the ability then to click 
on VIEW PUBLISHED to see what the record would look like on the public site.  
But when I click on it, I get an error stating "This page cannot be opened."  I 
tried it with several different records with the same result.

Now, I can open the regular public interface separately and view the record, 
but to have that logged-in feature not working is concerning.

It appears that it is not resolving the correct web address. When I look in the 
address bar when I click on View Published, it is using localhost:8081 instead 
of my test site, bmc-asmigrate:8081. I don't know if this is a support or a 
setup issue. Has this been fixed in later release (remember, this is version 
1.4.2) or if it is a setup issue?


[cid:[email protected]]



Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: [email protected]<mailto:[email protected]>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to