Jump to content

PiotrR

Clients
  • Posts

    10
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PiotrR's Achievements

  1. I have some additional observations that have emerged since last week in case of my community. So far I had a member who experienced following: Broken display on Android chrome V110 Reinstalling Chrome on V110 continued to yield broken display Display working fine upon downgrade to Chrome V109 I have asked said member to perform some additional experiments that yielded following results Upon forward upgrade to Chrome v110 the display broke again When installed Chrome v111 as Chrome Beta (it's separate app in the Play Store) the display works fine All above applies to one user on one device. Addtionally my own Android Chrome now updated to v110 and display works fine. I have had additional reports from a small number of users experiencing that issue and they were reporting using Chrome v110.
  2. It also works for me and seemingly most of the users. The one device I know to have experienced it was Hauwei Mate 20 Pro on Chrome v110. Reinstalling Chrome did not solve it but downgrade to 109 did solve, in this particular case. This could of course be a red herring. I am unable to currently update my own phone beyond v109, through the normal Play Store at least. The user I know to have experienced it is very regular and reports only starting to encounter this last week. Here is a video as well. received_1169264907061422.mp4
  3. It was reported to me to happen at least on topic view page, and frequently enough to make forum borderline unusable for the user in question. I have seen a video recording in topic with small number of picture attachments and intra-board embedded topic link but I cannot assert as to whether it only happens with them. Here is example topic where I can confirm at least one user experienced that issue https://forum.karawaning.pl/topic/42011-jej-budowa-campervana/
  4. So, I have been alerted to same/similar issue by one member of my board. He also observed it on another board running on Invision. I have asked my community and nobody else so far came forward as suffering from this. I am running default theme with very minor modifications. The other board mentioned is running other theme. I have spent some time with the member having issues and we managed to isolate this as issue likely only occuring on Android Chrome v110. They had a second phone, exact same model, that happens to run Chrome v109 and it works fine. I had them downgrade the offending device to Chrome 109 and issue did go away. It does make me nervous as Chrome v110 gets rolled out further. I have a video of the issue as well, should that help. Whereas it does appear to be Chrome rendering related issue sadly it's so ubiquitous that I think it'd be best for Invision to try to get to the bottom of issue, and possible workaround
  5. I have run into an issue with the Who's Online widget. My community is configured to restrict profile access to guests. I therefore expected a behaviour where: Who's online widget displayed for authenticated users would render profile links Who's online widget displayed for guest would render member names only, without links However what I am observing is that the above two behaviours are alternating seemingly randomly, while the observer remains being logged in (or logged off, i.e. continuing in same authentication state). Additionally whatever the current rendering state is in given moment (i.e. profile links or just member names)- it is same for both logged in users and guests. It feels to me that the widget is perhaps cached with disregard to user authentication state- and just displays in whichever way was appropriate while it was actually computed before caching? See screenshots below, they are both from the same authenticated user; maybe 10 mins apart.
  6. My community is running on old version, 4.4.10. I am currently performing test upgrade to latest and running into multiple issues. I suspect a overdue upgrade and forced php 8 upgrade at the same are part of the problem. I would like to perform a staggered upgrade, going first to 4.7.3 (the last supporting PHP 7.4), then isolate the PHP8 issues and perform second upgrade to latest. I would need to access the 4.7.3 installation pack which I don't seem to find in the client area- which apparently only allows latest.
×
×
  • Create New...