Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolver plugin not matching on page ranges #10786

Closed
kaitlinnewson opened this issue Jan 8, 2025 · 5 comments
Closed

Resolver plugin not matching on page ranges #10786

kaitlinnewson opened this issue Jan 8, 2025 · 5 comments
Assignees
Labels
Bug:1:Low A bug that does not have a severe consequence or affects a small number of users.
Milestone

Comments

@kaitlinnewson
Copy link
Member

kaitlinnewson commented Jan 8, 2025

Describe the bug
When using the Resolver plugin to resolve a URL to an article, the matching is not working when a page range is used.

To Reproduce
Steps to reproduce the behavior:

  1. Find an appropriate article that has a page range, and note the volume, number, and page range
  2. Open a URL for the Resolver plugin that should match to an article (where brackets at the end of the URL are volume/number/page or page range), e.g.: http://localhost:8000/index.php/publicknowledge/gateway/plugin/ResolverPlugin/vnp/1/2/71-98
  3. Note that article does not resolve for page range

What application are you using?
OJS 3.3/3.4/main

Pull requests

@kaitlinnewson kaitlinnewson added the Bug:1:Low A bug that does not have a severe consequence or affects a small number of users. label Jan 8, 2025
@kaitlinnewson kaitlinnewson added this to the 3.3.0-21 milestone Jan 8, 2025
@kaitlinnewson kaitlinnewson self-assigned this Jan 8, 2025
kaitlinnewson added a commit to kaitlinnewson/ojs that referenced this issue Jan 8, 2025
kaitlinnewson added a commit to kaitlinnewson/ojs that referenced this issue Jan 8, 2025
kaitlinnewson added a commit to kaitlinnewson/ojs that referenced this issue Jan 8, 2025
kaitlinnewson added a commit to kaitlinnewson/ojs that referenced this issue Jan 8, 2025
kaitlinnewson added a commit to kaitlinnewson/ojs that referenced this issue Jan 8, 2025
@kaitlinnewson
Copy link
Member Author

Hi @asmecher, could you give the PRs above a quick review & merge if all looks good? I've also done a couple of fixes for the plugin to work in 3.5. Thanks!

@asmecher
Copy link
Member

asmecher commented Jan 8, 2025

@kaitlinnewson, those look good -- but at the risk of punishing a good deed, a similar regexp appears in the JATS Template plugin (classes/ArticleFront.php in main, elsewhere in previous branches). At least for the main branch, I'd suggest syncing this change there.

asmecher pushed a commit to pkp/ojs that referenced this issue Jan 8, 2025
kaitlinnewson added a commit to kaitlinnewson/jatsTemplate that referenced this issue Jan 9, 2025
kaitlinnewson added a commit to kaitlinnewson/jatsTemplate that referenced this issue Jan 9, 2025
kaitlinnewson added a commit to kaitlinnewson/jatsTemplate that referenced this issue Jan 9, 2025
@kaitlinnewson
Copy link
Member Author

@asmecher I've done the PRs for the JATS template plugin and they are ready for review:

asmecher pushed a commit to pkp/jatsTemplate that referenced this issue Jan 9, 2025
asmecher pushed a commit to pkp/jatsTemplate that referenced this issue Jan 9, 2025
asmecher pushed a commit to pkp/jatsTemplate that referenced this issue Jan 9, 2025
@asmecher
Copy link
Member

asmecher commented Jan 9, 2025

Thanks, @kaitlinnewson, I've merged all those!

kaitlinnewson added a commit to kaitlinnewson/ojs that referenced this issue Jan 9, 2025
@asmecher
Copy link
Member

Thanks, @kaitlinnewson, both PRs merged re: the test fix; this should all be working now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug:1:Low A bug that does not have a severe consequence or affects a small number of users.
Projects
None yet
Development

No branches or pull requests

2 participants