Bug in the filter of the plugin portal catalog when switching pages

[funfried]

Apache NetBeans version

Apache NetBeans 24

What happened

If you set the NetBeans version to e.g. 24 in the plugin portal catalog and hit "Go!" it filters all the plugins which are compatible with that version, but as soon as you use the paging and switch to another page you loose the filter of the NetBeans version (as well as the category). So when switching to another page, only the search term will be kept, but not the filters.

Language / Project Type / NetBeans Component

Plugin Portal

How to reproduce

Just go to the plugin portal select 24 in the NetBeans version, hit "Go!" and switch to another page, you will then see, that the filter is gone and there are more all plugins visible again.

Did this work correctly in an earlier version?

No / Don't know

Operating System

Browser: Brave v1.74.48

JDK

Doesn't matter as it's related to the plugin portal

Apache NetBeans packaging

Other

Anything else

No response

Are you willing to submit a pull request?

No

[jkovalsky]

@matthiasblaesing, can you please take a look at this when you find some time?

[matthiasblaesing]

@jkovalsky will do. Thanks for the headsup. I plan to create a stage version, that fixes this and includes the options to request verification for a new plugin version without dropping the prio verification and simplification to verification that will require only a verification per plugin version and not per netbeans-version/plugin-version pair.

[matthiasblaesing]

@jkovalsky please have a look at these two PRs:

• PP3: Enhance indexing page with function to remember search parameters in session netbeans-tools#74
• PP3: Improve verification process netbeans-tools#72

I would like to merge both and deploy the new portal version. A Staging version is available here: https://pp3.doppel-helix.eu/ and has both PRs merged. Login is only possible with Apache Credentials, but then you are getting automatic admin rights and can add yourself as author to plugins and play with verification requests. The only draw back is, that normal verification requires two votes, but "Master Go" can be used to override.

[jkovalsky]

@matthiasblaesing, does the Apache authentication work for you? I get An error occurred in handling this OAuth request:
Invalid username or password supplied! error message despite using the same username/password when signing in via https://github.com/login which however requires 2nd factor verification.

[matthiasblaesing]

@jkovalsky yes I tested the changes on the staging system and I logged in through https://oauth.apache.org/. For the login credentials: These are the same that are used to log into other apache systems, for example https://whimsy.apache.org/roster/committer/__self__ . These are most probably not identical with your github credentials.

If you don't have access to the password anymore, here are the instructions how to reset them: https://selfserve.apache.org/identity.html#reset