Skip to content

[OPS] | Server Categories - Category forms and pages, paths are incorrect for OPS #12003

@kaitlinnewson

Description

@kaitlinnewson

Valid Title

  • I have updated the title to accurately reflect the bug description

Description

In OPS categories uses "preprints" (rather than "catalog" in OJS/OMP) for defining paths to content related to categories (including URLs to category views and images for the categories). This leads to a few issues in the code which don't currently account for this difference:

  • On the category editing form, the sample URL displays the incorrect path
  • When uploading images to a category, the resulting paths to the images are incorrect, meaning the image doesn't load on the form or on the front-end page for the category
  • In the "browse" plugin, the paths to the categories that appear in the block are not correct (see also Block links redirect and Highlight Issue in OPS 3.3 browse#7)

This issue has been partially fixed for OPS 3.5/main as part of #6002, except for the issue in the browse plugin.

Steps to Reproduce

  1. Login with a manager or admin role
  2. Navigate to Settings > Server > Categories
  3. Click Edit under an existing category, or make a new one
  4. Notice that the sample URL is not correct on the form
  5. Upload an image and save, then edit the category form again to see the broken image thumbnail
  6. Go to the front-end page for the category and also note the broken image link

Expected Result

The sample URLs and paths to images should be correct.

Actual Result

The sample URLs and paths to images are not correct and images for categories are broken.

Environment Details

No response

Application Version

OPS, all versions

Logs

No response

Additional Information

Incorrect sample URL which should use "preprints" and not "catalog"(OPS 3.4):

Image

Broken cover image on form (OPS 3.4):

Image

Pull Requests

Submodule updates only

Metadata

Metadata

Assignees

Labels

Bug:1:MinorA bug found in uncommon paths, with low consequences, limited users or has an easy workaround

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions