[GH-ISSUE #218] Error: path isundefined #208

Closed
opened 2026-02-25 22:36:29 +03:00 by kerem · 9 comments
Owner

Originally created by @bernd-wechner on GitHub (Dec 27, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/218

Wow, another error. Cryptic message alas. Was synching fine, but today I updated my Bookmarks app on Nextcloud to 0.15.1 as per a notification request, and the NextCloud itself to NexCloudPi v0.67.8 and NextCloud 14.0.4.2. And Now I see this error:

image

I checked the debug log but I can't see an obvious answer, the term "Path is" appears nowhere, and "undefined" is all over the log. I can as ever send one along by email for diagnosis but don't know of a way to send personal info along to a developer without it going public - I noticed recently GitLab supports confidential issues that can only be seen by the submitter and project members. Neat.

Originally created by @bernd-wechner on GitHub (Dec 27, 2018). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/218 Wow, another error. Cryptic message alas. Was synching fine, but today I updated my Bookmarks app on Nextcloud to 0.15.1 as per a notification request, and the NextCloud itself to NexCloudPi v0.67.8 and NextCloud 14.0.4.2. And Now I see this error: ![image](https://user-images.githubusercontent.com/7296506/50476359-f7d77c80-0a1b-11e9-929a-3c6676d27c05.png) I checked the debug log but I can't see an obvious answer, the term "Path is" appears nowhere, and "undefined" is all over the log. I can as ever send one along by email for diagnosis but don't know of a way to send personal info along to a developer without it going public - I noticed recently GitLab supports confidential issues that can only be seen by the submitter and project members. Neat.
Author
Owner

@bernd-wechner commented on GitHub (Dec 27, 2018):

More info I have:

  • It works on Google Chrome still
  • My Firefox has Floccus 3.2.1
  • My Chrome has Floccus 3.2.1
  • I backed up my Firefox Bookmarks to be safe then did Reset Cache on the Floccus settings and synched, and it all worked fine again.

Conclusion is something was broken with the Firefox Cache .... how that happened and why it correlated so well with my NextCloud upgrades is a mystery. I sent the log file by email, maybe it lends a clue. Maybe not worth pursuing.

<!-- gh-comment-id:450131929 --> @bernd-wechner commented on GitHub (Dec 27, 2018): More info I have: - It works on Google Chrome still - My Firefox has Floccus 3.2.1 - My Chrome has Floccus 3.2.1 - I backed up my Firefox Bookmarks to be safe then did Reset Cache on the Floccus settings and synched, and it all worked fine again. Conclusion is something was broken with the Firefox Cache .... how that happened and why it correlated so well with my NextCloud upgrades is a mystery. I sent the log file by email, maybe it lends a clue. Maybe not worth pursuing.
Author
Owner

@marcelklehr commented on GitHub (Dec 27, 2018):

Mh. Weird. 👍 for sending the log -- it seems I didn't get your email, though :/

<!-- gh-comment-id:450209063 --> @marcelklehr commented on GitHub (Dec 27, 2018): Mh. Weird. :+1: for sending the log -- it seems I didn't get your email, though :/
Author
Owner

@marcelklehr commented on GitHub (Dec 30, 2018):

I noticed recently GitLab supports confidential issues that can only be seen by the submitter and project members. Neat.

Yeah, that's a good idea.

<!-- gh-comment-id:450583304 --> @marcelklehr commented on GitHub (Dec 30, 2018): > I noticed recently GitLab supports confidential issues that can only be seen by the submitter and project members. Neat. Yeah, that's a good idea.
Author
Owner

@marcelklehr commented on GitHub (Jan 12, 2019):

@bernd-wechner ?

<!-- gh-comment-id:453760608 --> @marcelklehr commented on GitHub (Jan 12, 2019): @bernd-wechner ?
Author
Owner

@bernd-wechner commented on GitHub (Jan 13, 2019):

Marcel the problem is gone, but I did send the log by email to: mklehr@gmx.net at Thu, 27 Dec 2018 22:09:44 +1100.

I did just forward it to:
- mail address redacted -

as that is the ReplyTo address on an email I got from you via github once and so might reach you.

<!-- gh-comment-id:453819673 --> @bernd-wechner commented on GitHub (Jan 13, 2019): Marcel the problem is gone, but I did send the log by email to: mklehr@gmx.net at Thu, 27 Dec 2018 22:09:44 +1100. I did just forward it to: \- mail address redacted - as that is the ReplyTo address on an email I got from you via github once and so might reach you.
Author
Owner

@marcelklehr commented on GitHub (Jan 13, 2019):

This mail created a new comment over here, but didn't carry on the attachment :D Could you try the normal address again? 😄 🙈

<!-- gh-comment-id:453825608 --> @marcelklehr commented on GitHub (Jan 13, 2019): This mail created a new comment over [here](https://github.com/marcelklehr/floccus/issues/198#issuecomment-453819555), but didn't carry on the attachment :D Could you try the normal address again? 😄 🙈
Author
Owner

@bernd-wechner commented on GitHub (Jan 22, 2019):

I did resend it a few days ago. No luck getting it? Low priority given it works again, but I imagine I'd be curious what caused it if I had more time ;-).

<!-- gh-comment-id:456302009 --> @bernd-wechner commented on GitHub (Jan 22, 2019): I did resend it a few days ago. No luck getting it? Low priority given it works again, but I imagine I'd be curious what caused it if I had more time ;-).
Author
Owner

@marcelklehr commented on GitHub (Feb 7, 2019):

No luck. I did sort out some mail issues recently, so hopefully I'm reachable again :/

Anyway, closing this for now.

<!-- gh-comment-id:461491433 --> @marcelklehr commented on GitHub (Feb 7, 2019): No luck. I did sort out some mail issues recently, so hopefully I'm reachable again :/ Anyway, closing this for now.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 21, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1477569857 --> @github-actions[bot] commented on GitHub (Mar 21, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#208
No description provided.