Shortcuts in top-right corner A.K.A. The Red Square (TM) broken

I use the Red Square button in top-right corner of desktop to quickly list unpaid invoices, unbilled delivery notes., but since some recent commit to staging it no longer works. :frowning:

ERPNext: v11.0.3-beta.19 () (staging)
Frappe Framework: v11.0.3-beta.22 () (staging)

(click on “Delivery Note”)

There also general problems with clicking various shortcuts, like sales orders pertaining to an item… Someone seriously broke something and nobody cares, or is it some wild local problem that I should be investigating?

What version are you running? You haven’t given enough information for anyone to reproduce the bug you’re seeing. And generally with UI bugs you should provide a screen shot.

Sorry; mentioned it was ‘staging’, but here goes:

ERPNext: v11.0.3-beta.19 () (staging)
Frappe Framework: v11.0.3-beta.22 () (staging)

Screenshots uploaded.

Hitting F5 renders the table, but without extra filters
URL in browser: hxxps://XXX/desk#List/Delivery%20Note/List

This is still happening, and makes day-to-day tasks harder on:

ERPNext: v11.0.3-beta.20 () (staging)
Frappe Framework: v11.0.3-beta.25 () (staging)

Could someone on this or previous version tell me, that it’s only me? I don’t know what would cause this on my end, since I pretty much run the stock version and do ‘bench update --reset’ to update.

Hi,
I have
ERPNext: v11.0.3-beta.19 () (staging)
Frappe Framework: v11.0.3-beta.22 () (staging)

So, when I push on the Red button and choose Sales Invoice(unpaid) it isn’t loaded, I have a white screen without any errors in the console.
When I reload the page everything works.

OK, great; then it’s not only me. Do you also have this problem when clicking for example sales orders link on the item master?

Hi, yes and sorry in the browser’s console. I have error message

Uncaught (in promise) TypeError: a.startsWith is not a function
    at frappe.views.ListView.parse_filters_from_route_options (list_view.js:1126)
    at frappe.views.ListView.setup_defaults (list_view.js:53)
|parse_filters_from_route_options|@|list_view.js:1126|
|---|---|---|
|setup_defaults|@|list_view.js:53|
|Promise.then (async)|||
|show|@|list_view.js:37|
|frappe.views.ListView|@|list_view.js:22|
|(anonymous)|@|list_factory.js:31|
|with_doctype|@|model.js:97|
|make|@|list_factory.js:12|
|show|@|factory.js:24|
|show|@|list_factory.js:48|
|frappe.route|@|router.js:48|
|(anonymous)|@|router.js:179|
|dispatch|@|jquery.min.js:3|
|r.handle|@|jquery.min.js:3|
|hashchange (async)|||
|(anonymous)|@|router.js:146|
|frappe.set_route|@|router.js:127|
|load_last_view|@|list_view.js:14|
|(anonymous)|@|list_factory.js:22|
|callback|@|model.js:134|
|success|@|request.js:73|
|200|@|request.js:98|
|(anonymous)|@|request.js:217|
|i|@|jquery.min.js:2|
|fireWith|@|jquery.min.js:2|
|z|@|jquery.min.js:4|
|(anonymous)|@|jquery.min.js:4|
|load (async)|||
|send|@|jquery.min.js:4|
|ajax|@|jquery.min.js:4|
|frappe.request.call|@|request.js:199|
|frappe.call|@|request.js:77|
|with_doctype|@|model.js:107|
|make|@|list_factory.js:12|
|show|@|factory.js:24|
|show|@|list_factory.js:48|
|frappe.route|@|router.js:48|
|i|@|jquery.min.js:2|
|add|@|jquery.min.js:2|
|n.fn.ready|@|jquery.min.js:2|
|n.fn.init|@|jquery.min.js:2|
|n|@|jquery.min.js:2|
|init|@|event_emitter.js:7|
|trigger|@|event_emitter.js:11|
|(anonymous)|@|router.js:181|
|dispatch|@|jquery.min.js:3|
|r.handle|@|jquery.min.js:3|
|hashchange (async)|||
|(anonymous)|@|router.js:146|
|frappe.set_route|@|router.js:127|
|show_open_count_list|@|notifications.js:111|
|(anonymous)|@|notifications.js:95|
|dispatch|@|jquery.min.js:3|
|r.handle|@|jquery.min.js:3|
1 Like

It’s exactly this error and I think it’s since this commit : fix(listview): Smart parsing of route options (#6404) · frappe/frappe@fc7a4a7 · GitHub

do we have @netchampfaris in the house? :slight_smile:

I reverted this commit in my installation and it doesn’t seem to help, hm.

Fix is done here : [Minor] Routing from Notifications opens blank page by Zlash65 · Pull Request #6443 · frappe/frappe · GitHub

It’s merged into staging-fixes and I think it will be merged into staging this friday.

You can see the diff to test the correction.

1 Like

Thanks for the info. Everything seems to be working. :slight_smile: