KT Walrus

I’m trying editing a reply to see if that throws an exception. Here is my edit. This edit showed up this time. It is working every time when the Web Inspector on my Mac is connected. Maybe this bug really is a timing issue with very fast iPhones. Disconnecting cable to MacBook Pro for this edit. Yes. With the cable disconnected I don’t see the edit until I reload the page. This last one worked while the previous one didn’t.

I know I said I wasn’t going to do this, but I did and the Web Inspector console shows no exceptions when replying to this topic and the keyboard doesn’t pop up to enter text into the editor. Here is a screenshot of the console:

This is what Claude says to see JavaScript exceptions on my iPhone. I’m not going to take the time to do this, but maybe this would explain what I’m seeing, if this works for debugging a PWA. Claude 3 response via duck.ai To see JavaScript exceptions in Safari on your iPhone, you can follow these steps: 1. Enable the Develop Menu in Safari: Go to Settings > Safari > Advanced and turn on the "Develop" menu. 2. Connect your iPhone to your Mac: Use a Lightning cable to connect your iPhone to your Mac. 3. Enable Web Inspector on your iPhone: On your iPhone, go to Settings > Safari > Advanced and turn on "Web Inspector". 4. Open the Web Inspector on your Mac: On your Mac, open Safari and go to the "Develop" menu (which should now be visible). Hover over the name of your connected iPhone, and then select "Show Web Inspector". 5. View JavaScript Exceptions: In the Web Inspector window, you should see a "Console" tab. This is where you can view any JavaScript exceptions that occur while you're using Safari on your iPhone. When a JavaScript exception occurs, it will be displayed in the Console, along with information about the error, such as the line of code where the exception occurred and the stack trace. Keep in mind that the Web Inspector feature is primarily intended for web developers, so it may not be the most user-friendly way to view JavaScript exceptions for non-technical users. However, it is the best way to access this information on an iPhone.

18.2.1 (the latest version I think). Maybe there is a JavaScript exception preventing the keyboard from appearing to input text? I do have the fastest iPhone and I think this prevents me from seeing edits to posts unless I force a page reload to see the changes. So, maybe the issue is only on very fast iPhones where there is some sort of asynchronous JS that gets handled out of the usual order sometimes. I did notice that around 10% of the time I can see edit changes without reloading making me think that some of my PWA UI issues are JavaScript related and maybe hard for you to reproduce?

I primarily use the PWA when visiting this site using an iPhone 16 Pro Max. There are several theme usability issues that would be obvious to anyone using the PWA for a couple of days. Please have your devs spend time on testing out the UX specifically on the iOS PWA before releasing the v5 GA. Specifically, I am unable to post using the PWA so I’m posting this in Safari. I think I might have taken time to report this one bug already, but almost every time I use the PWA I see issues with the theme that I simply don’t have the time or energy to report. A good week of thorough testing of the PWA would be very welcome by me as I intend to enable the PWA for my upcoming v5 site and it is important to me that the UX be as good or better than using a browser. The issues are undoubtedly from Webkit in the PWA being several releases behind Safari and your devs using Safari or Chrome and not the PWA for testing.

I was going to report the same thing, but the PWA doesn’t allow me to enter reply text into this reply editor as I’m doing now using Safari instead of the PWA. This is a screenshot on my iPhone 16 Pro Max using the PWA.

What would happen if you set max-width to 100% for .i-wrapper in your custom CSS?

Thanks for splitting. The quick fix would be to simply put back/reload/forward ( ) buttons in the Navigation menu in the default theme. This Navigation menu is quickly accessible is the navigation bar at the bottom of the page on mobile.

Note that this issue makes the PWA on iOS basically unusable for me. For example, I submitted an edit to my first reply above and the edit changes didn’t show up, only the edited by line. I then tried to reply with a screenshot of what I’m seeing but the editor got stuck when I pasted in the attachment. Apparently JS stopped processing some events maybe? I ended up going to the index page and the entering this topic as a workaround to not being able to reload a page in the PWA. Anyway, not having a dedicated refresh icon somewhere on the page is a big usability issue for me as I only browse forums on my iPhone and use PWAs for the sites I visit most.

No “pull to refresh” when using the PWA? I ended up force quitting the PWA to get by the “in maintenance mode” page. I’m using an iPhone 16 Pro Max. I had hoped that IC5 default theme would have a refresh icon somewhere on each page when using the PWA on iOS and that “pull to refresh” would be implemented. Maybe the PWA can get some more attention before GA? BTW, loving IC5 on this site.

I hate that so many search results these days point to AI generated content. The pages on the internet should all be human generated unless the domain uses the .ai TLD. Please don’t be tempted to integrate AI content into Invision Community. As a user, I want to read human generated content on the web. If I want an approximate answer, I will use an AI agent. Nothing would be worse than visiting a forum and later finding out that it is simply a bunch of AI agents discussing amongst themselves. What a waste of time reading content like this.

No. I haven’t coded my Invision app yet as I’m waiting for IC5 GA. I have contracted with Tighten to develop a Laravel app for the backend of my new IC5 app though. This should be finished in the next few weeks. The backend will manage the SQLite databases. Each user that visits my site will have the backend generate the SQLite database for just that session. Dynamically generating these SQLite databases are lightning fast and contain only the data the user has permission to see. You can check out this site that uses Laravel and SQLite in the meantime: https://pinkary.com

You could start with SQLite for caching data locally on the server. If settings, compiled theme templates, etc. were stored in SQLite, all those queries that are done on every page load would be lightening fast (even faster than fopen). Because SQLite PDO driver is built into PHP and creating a SQLite database is simply touching a file on the server you don’t really need any admin settings to deploy (you should connect to the database in WAL mode though). You could also use SQLite for the Database or Filesystem Storage Methods for files as a fast, easy to use database (as opposed to the local file system). Backing up SQLite is simply copying the database file (using sqlite3_rsync tool if database is live). Also, SQLite would be a better alternative for sessions than Redis (for installations on a single server) Everything about using SQLite is so easy and so fast. In my Laravel prototype, I was able to eliminate aggregate data about content (like stored in the forums table) to show this data like unread counts, last replier, etc. When you aren’t worried about doing 200 queries per page load, you can really simplify the SQL that you write to get the data for showing to a user and not worry about caching it for subsequent page loads. So, even if you don’t want to support storing everything in SQLite, you could make use SQLite to really eliminate many network round trips to the MySQL instance in the Invision Cloud. I really think you could make a difference that your customers would appreciate especially us self-hosting customers.

I just finished paying one of the top Laravel agencies over $100k to prototype this app in Laravel using SQLite (with me on Zoom pairing with the lead programmer for the last 2 months on exploring all my ideas for SQLite at scale) and I am convinced SQLite will scale quite nicely for a large busy site. I am now hoping to apply the knowledge I gained over the last 5 months to an IC5 app using SQLite. I got tired of waiting for Invision to release IC5 so I spent some money on prototyping my ideas in Laravel. Checkout Turso/LibSQL and also Fly.io for more on making SQLite scale for large busy sites. I prototyped LibSQL but ended up going with standard SQLite (with using the newly released sqlite3_rsync tool for syncing to UI servers instead of LibSQL’s embedded replicas). I believe Invision could absolutely replace MySQL with SQLite for Cloud customers and cut your database expenses to a fraction of what you spend with AWS on MySQL and end up with extremely fast queries as a bonus. SQLite queries execute in nanoseconds while MySQL queries take milliseconds.