github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-31 10:47:57 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

"You must provide a project view ID when sorting by position" when trying to access a collection #2058

New Issue
Closed
opened 2026-03-22 13:53:39 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-03-22 13:53:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @tmortagne on GitHub (Dec 31, 2024).

Description

Every time I'm trying to access the list view of project, I get a "You must provide a project view ID when sorting by position" short popup and none of the tasks of that project are listed. To be a bit more precise, when I click a project the HTTP request https://myhost/api/v1/projects/4/tasks?sort_by[]=position&order_by[]=asc&filter_by[]=done&filter_value[]=false&filter_comparator[]=equals&filter_concat=and&page=1 the server respond with the JSON {"code":4026,"message":"You must provide a project view ID when sorting by position"}.

I first thought it was only with a project created with an older version, but it does not work better with a new project, actually.

Note that it's specific to the list view. The Gantt and Table views seems to work (no error, at least, and I do see the tasks in the table). The Kanban view does produce an error, but a different one related to a "missing, malformed, expired or otherwise invalid token provided" (did not check if that one was already reported).

What I get in the About is a bit surprising:

Version : 0.22.0
API version : v0.24.6

but maybe this discrepancy is expected ?

It's installed (and upgraded several times) using the Debian package, and I have the following configuration:

/etc/vikunja/config.yml
the Apache HTTPd configuration (in case you feel like the problem is a proxy misconfiguration)

Vikunja Version

0.24.6

Browser and version

Firefox 133.0.3

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @tmortagne on GitHub (Dec 31, 2024). ### Description Every time I'm trying to access the list view of project, I get a "You must provide a project view ID when sorting by position" short popup and none of the tasks of that project are listed. To be a bit more precise, when I click a project the HTTP request `https://myhost/api/v1/projects/4/tasks?sort_by[]=position&order_by[]=asc&filter_by[]=done&filter_value[]=false&filter_comparator[]=equals&filter_concat=and&page=1` the server respond with the JSON `{"code":4026,"message":"You must provide a project view ID when sorting by position"}`. I first thought it was only with a project created with an older version, but it does not work better with a new project, actually. Note that it's specific to the list view. The Gantt and Table views seems to work (no error, at least, and I do see the tasks in the table). The Kanban view does produce an error, but a different one related to a "missing, malformed, expired or otherwise invalid token provided" (did not check if that one was already reported). What I get in the `About` is a bit surprising: ``` Version : 0.22.0 API version : v0.24.6 ``` but maybe this discrepancy is expected ? It's installed (and upgraded several times) using the Debian package, and I have the following configuration: [`/etc/vikunja/config.yml`](https://github.com/user-attachments/files/18282785/config.yml.txt) [the Apache HTTPd configuration](https://github.com/user-attachments/files/18282789/vikunja.conf.txt) (in case you feel like the problem is a proxy misconfiguration) ### Vikunja Version 0.24.6 ### Browser and version Firefox 133.0.3 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:53:42 -05:00
Author
Owner
Copy Link
Copy Source

@kolaente commented on GitHub (Dec 31, 2024):

Did you upgrade the Frontend as well?

@kolaente commented on GitHub (Dec 31, 2024): Did you upgrade the Frontend as well?
GiteaMirror commented 2026-03-22 13:53:43 -05:00
Author
Owner
Copy Link
Copy Source

@tmortagne commented on GitHub (Dec 31, 2024):

Well, I kind of expected that https://vikunja.io/docs/installing#debian-packages would take care of everything, actually. But I'm slowly starting to understand that it's not the case, sorry for the noise (might be good to be a bit more explicit about that in https://vikunja.io/docs/installing). Would be nice to have support for both in the Debian package (or two Debian packages), but I get that it's a lot of work to support so many packages.

@tmortagne commented on GitHub (Dec 31, 2024): Well, I kind of expected that https://vikunja.io/docs/installing#debian-packages would take care of everything, actually. But I'm slowly starting to understand that it's not the case, sorry for the noise (might be good to be a bit more explicit about that in https://vikunja.io/docs/installing). Would be nice to have support for both in the Debian package (or two Debian packages), but I get that it's a lot of work to support so many packages.
GiteaMirror commented 2026-03-22 13:53:44 -05:00
Author
Owner
Copy Link
Copy Source

@kolaente commented on GitHub (Jan 6, 2025):

The frontend and api were merged into one in 0.23.0. You should be able to install just the Vikunja deb and remove the proxy configuration.

@kolaente commented on GitHub (Jan 6, 2025): The frontend and api were merged into one in [0.23.0](https://vikunja.io/changelog/whats-new-in-vikunja-0.23.0#api-frontend-and-desktop-are-now-merged-in-one-repo). You should be able to install just the Vikunja deb and remove the proxy configuration.
GiteaMirror commented 2026-03-22 13:53:44 -05:00
Author
Owner
Copy Link
Copy Source

@tmortagne commented on GitHub (Jan 7, 2025):

The frontend and api were merged into one in 0.23.0. You should be able to install just the Vikunja deb and remove the proxy configuration.

I'm not sure what you mean, I cannot remove the proxy configuration as I have to tell Apache how to access Vikunja. Do you mean the frontend included in the Debian package use a different port than 3456 ?

@tmortagne commented on GitHub (Jan 7, 2025): > The frontend and api were merged into one in [0.23.0](https://vikunja.io/changelog/whats-new-in-vikunja-0.23.0#api-frontend-and-desktop-are-now-merged-in-one-repo). You should be able to install just the Vikunja deb and remove the proxy configuration. I'm not sure what you mean, I cannot remove the proxy configuration as I have to tell Apache how to access Vikunja. Do you mean the frontend included in the Debian package use a different port than 3456 ?
GiteaMirror commented 2026-03-22 13:53:45 -05:00
Author
Owner
Copy Link
Copy Source

@kolaente commented on GitHub (Jan 7, 2025):

The Vikunja binary also serves the frontend files since 0.23.0. That means you can replace your httpd config to something like this:

<VirtualHost *:80>
    ServerName myhost

    RewriteEngine on
    RewriteCond %{SERVER_NAME} =myhost
    RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

<VirtualHost *:443>
    ServerName myhost

    <Proxy *>
      Order Deny,Allow
      Allow from all
    </Proxy>
    ProxyPass / http://localhost:3456/
    ProxyPassReverse / http://localhost:3456/

    <Location />
      require all granted
    </Location>

    SSLCertificateFile /etc/letsencrypt/live/myhost/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/myhost/privkey.pem
    Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>

Check out the linked changelog post for more details about this.

@kolaente commented on GitHub (Jan 7, 2025): The Vikunja binary also serves the frontend files since 0.23.0. That means you can replace your httpd config to something like this: ``` <VirtualHost *:80> ServerName myhost RewriteEngine on RewriteCond %{SERVER_NAME} =myhost RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> <VirtualHost *:443> ServerName myhost <Proxy *> Order Deny,Allow Allow from all </Proxy> ProxyPass / http://localhost:3456/ ProxyPassReverse / http://localhost:3456/ <Location /> require all granted </Location> SSLCertificateFile /etc/letsencrypt/live/myhost/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/myhost/privkey.pem Include /etc/letsencrypt/options-ssl-apache.conf </VirtualHost> ``` Check out the linked changelog post for more details about this.
GiteaMirror commented 2026-03-22 13:53:45 -05:00
Author
Owner
Copy Link
Copy Source

@tmortagne commented on GitHub (Jan 8, 2025):

Much better! Thanks a lot for your patience.

@tmortagne commented on GitHub (Jan 8, 2025): Much better! Thanks a lot for your patience.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2058