GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Search is broken on macOS/Safari 15 · Issue #192 · textpattern/textpattern.github.io

Search is broken on macOS/Safari 15 #192

New issue
Copy link
New issue
Copy link
Open
Open
Search is broken on macOS/Safari 15#192
Copy link
Assignees
philwareham

Description

@petecooper
petecooper
opened on Oct 21, 2021
Issue body actions

STR: search docs site for anything, no results are shown. For example:

https://docs.textpattern.com/search/?q=form

macOS/Safari 15.0 shows the following console log:

[Error] QuotaExceededError: The quota has been exceeded.
	setItem (search.js:1:119221)
	(anonymous function) (search.js:1:119221)
	i (search.js:1:28112)
	fireWith (search.js:1:28876)
	l (search.js:1:79576)
	(anonymous function) (search.js:1:82019)

Likely fixable with #162 but if we can bodge something in the meantime, that would be super.

Activity

  1. petecooper
    assigned
    philwareham
    on Oct 21, 2021
  2. philwareham commented on Oct 21, 2021

    @philwareham
    philwareham
    on Oct 21, 2021
    Member
    More actions

    Works in Chrome and Firefox, broken in Safari 15. Will see if upstream project that provides the search JS has any reported issues.

  3. philwareham commented on Oct 21, 2021

    @philwareham
    philwareham
    on Oct 21, 2021
    Member
    More actions

    No issues at upstream project, but to be honest that project has been abandoned for a number of years.

    Worth consideration: https://github.com/christian-fei/Simple-Jekyll-Search

    I don't have time to implement until at least w/c 1st November. If someone else wants to try a fix, then by all means have at it.

    Also, would be nice to get the self-hosted site up in the near future and end our reliance on GitHub Pages.

  4. petecooper
    changed the title [-]Search is broken[/-] [+]Search is broken on macOS/Safari 15[/+] on Oct 21, 2021
  5. petecooper commented on Oct 21, 2021

    @petecooper
    petecooper
    on Oct 21, 2021
    MemberAuthor
    More actions

    would be nice to get the self-hosted site up in the near future and end our reliance on GitHub Pages.

    Agreed. On my roadmap when I have time, hopefully sooner rather than later.

  6. jools-r commented on Nov 13, 2021

    @jools-r
    jools-r
    on Nov 13, 2021
    SponsorMember
    More actions

    I wanted to mention this too. Likewise QuotaExceededError: The quota has been exceeded in Safari 15 and still working on Brave (i.e. Chrome).

  7. philwareham commented on Nov 13, 2021

    @philwareham
    philwareham
    on Nov 13, 2021
    Member
    More actions

    Will try to fix on Monday, can spare an hour that day.

  8. jools-r commented on Apr 28, 2022

    @jools-r
    jools-r
    on Apr 28, 2022
    SponsorMember
    More actions

    May I nudge on this one too?

  9. philwareham commented on Apr 28, 2022

    @philwareham
    philwareham
    on Apr 28, 2022
    Member
    More actions

    Yeah, I can't fix this without the Jekyll site being self-hosted. Basically, Lunr.js tries to build the search using LocalStorage but because the site is quite large it's exceeding Safari's default local storage limit.

    If the site were self-hosted, we could use a proper Ruby plugin to achieve search.

  10. petecooper commented on Apr 28, 2022

    @petecooper
    petecooper
    on Apr 28, 2022
    MemberAuthor
    More actions

    I have issues with getting it to rebuild non-interactively, I am working on it.

  11. petecooper commented on May 16, 2022

    @petecooper
    petecooper
    on May 16, 2022
    MemberAuthor
    More actions

    Docs site is now self-hosted.

    Reacted by jools-r
    Reacted by jools-r
  12. philwareham
    added a commit that references this issue on Nov 25, 2022

    Initial files for search update/fix

    b329c14
  13. jools-r commented on Sep 22, 2023

    @jools-r
    jools-r
    on Sep 22, 2023
    SponsorMember
    More actions

    Could I nudge this one once more? It looks like you've added the packages and that the site is now self-hosted. I guess a puzzle piece is missing?

  14. philwareham commented on Sep 22, 2023

    @philwareham
    philwareham
    on Sep 22, 2023
    Member
    More actions

    @petecooper Hi Pete, I assume we use the self-hosted branch for development now (for the self hosted docs on our own server)?

    Reacted by Pete Cooper
  15. philwareham commented on Sep 23, 2023

    @philwareham
    philwareham
    on Sep 23, 2023
    Member
    More actions

    For investigation: https://www.algolia.com/developers/code-exchange/integrate-jekyll-with-algolia/

  16. philwareham commented on Sep 23, 2023

    @philwareham
    philwareham
    on Sep 23, 2023
    Member
    More actions

    TBH Jekyll seems fair dead nowadays. I guess we could look at Eleventy or just bring the docs into a Textpattern installation itself - don't know how we could maintain user editable pages on GitHub along with Textpattern database though?

  17. petecooper commented on Sep 23, 2023

    @petecooper
    petecooper
    on Sep 23, 2023
    MemberAuthor
    More actions

    There's an issue somewhere (don't ask where) that I have to track viability of docs hosting on a docs-centric, non-GitHub service…I need to find it, and I'll link it, and we'll make it happen…it's been a while, so I'll go searching.

    Getting Textpattern docs into Textpattern in a non-kludgy, maintainable way is a whole heap of work, and I'm inclined to use a reputable service with good search, being mindful of the huge amount of work @wion & @Bloke put into docs (and not undoing that).

    Textpattern isn't the right platform for our docs, at least not in the sense that it can plug into GitHub and maintain syncing, we're not there yet. There's no shame in using other tools, we're progressive enough to avoid NIH syndrome, and if it lets us divert energies into core then that's a heavy tick in the box from me.

  18. petecooper commented on May 10, 2024

    @petecooper
    petecooper
    on May 10, 2024
    MemberAuthor
    More actions

    Tagging #212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @philwareham
    philwareham

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.