chenejac
commented
5 years ago Ralph O'Flinn said:
Maybe just a default back to [https://wiki.duraspace.org/display/VIVODOC110x/Configuration+Reference] to remind them to change it.
Open chenejac opened 5 years ago
chenejac
commented
5 years ago Ralph O'Flinn said:
Maybe just a default back to [https://wiki.duraspace.org/display/VIVODOC110x/Configuration+Reference] to remind them to change it.
chenejac
commented
5 years ago Mike Conlon said:
Good. I don't want to link out to the VIVO web site or wiki directly – faculty click on the unconfigured support link, end up on the VIVO web site and send us support questions (regardless of what the pages say). So perhaps the support link could be pointed at the About page (we don't have a Support page) with a note there that the About page and the Support link need to be configured locally along with a link to the documentation. Thoughts?
chenejac
commented
5 years ago Ralph O'Flinn said:
Would it be better to make a default support page? Maybe a copy of the Contact Us page that simply talks about Support instead and mails a support email address?
chenejac
commented
5 years ago Mike Conlon said:
Perhaps. The solution can not send email to us. I'll take a look at creating a static page (I'd also like to see About be a static page – shouldn't need Java to display the about page.)
chenejac
commented
5 years ago Stefan Wolff said:
If you use a static page (without Java), then there is no multi language support.
chenejac
commented
5 years ago Mike Conlon said:
Good point. Like the properties, it becomes an artifact that must be provided in each language. It seems we have a lot of code just to display an About page. Perhaps there is a simpler way to get a page with language properties?
chenejac
commented
5 years ago Ralph O'Flinn said:
Well that is one reason I was thinking about the contact/feedback form page. Copy/Paste call it support and the email property would be configured like the feedback form is?
chenejac
commented
5 years ago Mike Conlon said:
Will take a look. Thank you both.
chenejac
commented
5 years ago Stefan Wolff said:
Or the link points to a static page related to the language, i.e. support_en.html, support_de.html, support_es.html. Then static support pages have to be created for all supported languages. A disadvantage would be the redundance.
chenejac
commented
5 years ago Stefan Wolff said:
But i think, it would be enough to remove this link. If someone needs it, there is no problem to add a link into the custome theme and configure a page (HTML directly or a template) to give specific support information.
chenejac
commented
5 years ago Christian Hauschke said:
I support Stefans solution. It's not really hard to add a link to the footer if needed. Let's remove this.
Mike Conlon (Migrated from VIVO-1657) said:
The support link in the footer on the bottom of every VIVO page points to a page on a VIVO Project web site. This is inappropriate. Support for VIVO is locally provided.
The link will be changed to point at something useful. Comments welcome.
A separate issue related to documentation will provide a new page in [https://wiki.duraspace.org/display/VIVODOC110x/Preparing+for+Production] instructing sites to change the Support link to something local.