Bug 8656 - outgoing links to no longer existing PKP services
outgoing links to no longer existing PKP services
Status: NEW
Product: OJS
Classification: Unclassified
Component: Open Journal Systems
To be determined
All All
: P3 minor
Assigned To: PKP Support
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-28 16:19 PDT by Marco Tullney
Modified: 2014-04-02 10:42 PDT (History)
1 user (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Tullney 2014-03-28 16:19:02 PDT
While checking outgoing links I've stumpled upon links to former PKP web services that don't exist anymore since the relaunch.

This is not only a matter of links, but of the mentioning of those services in many locale files.

PKP Blog
http://pkp.sfu.ca/blog
http://pkp.sfu.ca/blog/feed

PKP's Harvester
http://pkp.sfu.ca/harvester/
http://pkp.sfu.ca/harvester/add.php

"stay informed"
http://pkp.sfu.ca/informed

registering OJS journal
http://pkp.sfu.ca/ojs/register
Comment 1 Marco Tullney 2014-03-28 16:27:24 PDT
maybe http://pkp.sfu.ca/informed could be replaced by https://pkp.sfu.ca/category/news/
Comment 2 Chris MacDonald 2014-04-02 10:10:44 PDT
Hey Marco - I've added redirects to these links to point to their respective replacements where there are some, or to relevant pages in the case where a replacement doesn't quite exist.

Feel free to have a look and if you're satisfied with the results you can close the bug.
Comment 3 Marco Tullney 2014-04-02 10:42:35 PDT
thanks, Chris.

that keeps people from running into a page not found, but there remain issues:

* There's still text announcing "the blog" in the xml locale files. I am thinking about fixing the blog mentioning in the English locale to prevent that (and the redirect helps people using locales that haven't been updated). After I've done that (or after I've decided not to do that or someone has told me not to do it ;)), I could close this bug.

Maybe you could have another look at the redirect rules, because it looks as if you only redirect unencrypted connections - all https:// links aren't redirected.