Email registration settings

[David Brian Holt]

OK, this is my last task before this goes into production.  I want users to be able to register via the link in Dspace.  The problem I'm having, however, is that I have forwarded port 8080 to 80 (using iptables) and changed the root directory in Jetty in to xmlui.  When a user tries to register they get the setting I have in the dspace.cfg file.  I read in previous posts to this forum that you can modify the email templates directly but I don't see how that is done.

Here is what I have in dspace.cfg currently:

##### Basic information ######


# DSpace installation directory
# Windows note: Please remember to use forward slashes for all paths (e.g. C:/dspace)
dspace.dir = /dspace


# DSpace host name - should match base URL.  Do not include port number.
dspace.hostname = lgbtqbib.org


# DSpace base host URL.  Include port number etc.
dspace.baseUrl = localhost:8080


# The user interface you will be using for DSpace. Common usage is either xmlui or jspui
dspace.ui = xmlui

Here is the email generated when I try to register a new user:

To complete registration for a DSpace account, please click the link
below:

  localhost:8080/xmlui/register?token=d0ece0e5e9c942d53da8674f9a391650

If you need assistance with your account, please email
dspace-help@myu.edu or call us at xxx-555-xxxx.

The DSpace Team

I want the URL in that email to simply read: 

lgbtqbib.org/register?token......

How do I do that?  

[Bollini Andrea]

You need to change

dspace.baseUrl = http://lgbtqbib.org

dspace.url = http://lgbtqbib.org

If you want to further change the email the tempkates can be found in

/dspace/config/emails

register is the template of hour use case.

Hope this help 

Andrea

Inviato dal mio dispositivo Samsung

-------- Messaggio originale --------
Da: David Brian Holt <holt...@gmail.com>
Data: 27/12/2016 19:25 (GMT+01:00)
A: DSpace Technical Support <dspac...@googlegroups.com>
Oggetto: [dspace-tech] Email registration settings

--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[David Brian Holt]

Thank you!  That worked.  I'm still getting "/xmlui" in that URL though.   Is there a way to get that removed?

This is the sample email I received after changing those settings:

To complete registration for a DSpace account, please click the link
below:

  http://lgbtqbib.org/xmlui/register?token=d0ece0e5e9c942d53da8674f9a391650

I'd like to remove the "xmlui" out of the URL as I have already set it to the root directory.

David

[Bollini Andrea]

you need to change also

dspace.url = http://lgbtqbib.org

your probably will look like

dspace.url = ${dspace.baseUrl}/${dspace.ui}

Andrea

-- 
Andrea Bollini
Chief Technology and Innovation Officer

4Science,  www.4science.it
office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy
mobile: +39 333 934 1808
skype: a.bollini
linkedin: andreabollini
orcid: 0000-0002-9029-1854

an Itway Group Company
Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates

[David Holt]

Andrea,

I'm hoping you'll be able to answer another question for me.  I'm having problems with the Solr server.   This is my current setting in the dspace.cfg file:

##### Basic information ######

# DSpace installation directory

# Windows note: Please remember to use forward slashes for all paths (e.g. C:/dspace)

dspace.dir = /dspace

# DSpace host name - should match base URL.  Do not include port number.

dspace.hostname = http://lgbtqbib.org

# DSpace base host URL.  Include port number etc.

dspace.baseUrl = http://lgbtqbib.org

# The user interface you will be using for DSpace. Common usage is either xmlui or jspui

dspace.ui = xmlui

# Full link your end users will use to access DSpace. In most cases, this will be the baseurl followed by

# the context path to the UI you are using.

#

# Alternatively, you can use a url redirect or deploy the web application under the servlet container root.

# In this case, make sure to remove the /${dspace.ui} from the dspace.url property.

dspace.url = ${dspace.baseUrl}/${dspace.ui}

# Optional: DSpace URL for mobile access

# This

#dspace.mobileUrl = http://mobile.example.com

# Name of the site

dspace.name = LGBT and the Law: An Annotated Bibliography

# Default language for metadata values

default.language = en_US

# Solr server/webapp.

# DSpace uses Solr for all search/browse capability (and for usage statistics by default).

# The included 'solr' webapp MUST be deployed to Tomcat for DSpace to function.

# Usually it will be available via port 8080 and the 'solr' context path. But,

# But, you may need to modify this if you are running DSpace on a custom port, etc.

solr.server = http://localhost:8080/solr

##### Database settings #####

# DSpace only supports two database types: PostgreSQL or Oracle

# URL for connecting to database

#    * Postgres template: jdbc:postgresql://localhost:5432/dspace

#    * Oracle template: jdbc:oracle:thin:@//localhost:1521/xe

db.url = jdbc:postgresql://localhost:5432/dspace

When I try to run "filter-media" from the command line everything works properly.  But when I try to re-index authority fields ("index-authority") I'm getting an error message that the configuration isn't valid.  I've tried changing the URL for the Solr server to "http://lgbtqbib.org/solr" and "http://lgbtqbib.org:8080/solr" but it doesn't appear to be working.  If I forward a port (using iptables) do I also need to change this setting?  

I also noticed that some metadata fields are appearing in item records even though they're blank.  I don't know what's causing that.

Thanks,

David

[Bollini Andrea]

If you have port forwarding from 8080 to 80 try to setup

solr.server = http://localhost/solr

try to query your solr instance from the command line, you should get a 200 response
wget http://localhost/solr/search?q=*:*

Andrea

[David Holt]

I just tried that and I'm getting a connection refused message.

Do you think maybe I should do my port forwarding differently?  I'm using an iptable right now.  I noticed while reading the Dspace documentation last night that they recommend using a proxy in Apache.  

Thank you for responding,

David

[David Holt]

OK, I tried using Apache's proxy instead of iptables and I'm getting the same result.

When I try to query Solr from the command line I'm getting a 404 error.  Any other suggestions?  

[Bollini Andrea]

Hi David,

the best way is to setup mod_jk to connect apache http (port 80) with the tomcat backend (port 8080). This is true for the public webapps jspui, xmlui, etc.

the solr webapp should not be exposed over the web, so no need to be readdressed on port 80 at all.

Anyway if you get a 404 it means that the solr webapp is not running at all, stop you tomcat, clean the log files remove all the webapps from tomcat than solr and restart. Check the log file for errors.

Andrea