Feature on Forum not Working

[Jan-Horn]

Somehow the problem was resolved. It is fully functional again 👍

[Jan-Horn]

Using the "users on line" as a starting point worked for 8 months and still working on both IE and Fire Fox, It only became a problem since the January Windows 10 update. 

 A new error this morning 

So mods there you have a reference number

[Luke7777]

---

@Jan-Horn wrote:

---

I changed the Page set on the tab I used to access the forum from the users on line page to the discussions page and that solved the problem for me. 

---

---

I've always used the Discussion tab... makes it easy to see new posts

[TebogoM_DStv1]

We will bring this to their attention. Thanks. 

[Jan-Horn]

---

@TebogoM_DStv1 wrote:

Cool. Glad to hear that everything is sorted. 

I would  not call it sorted. I found a work around for the  problem but it is still an issue with the compatibility with this software and the Windows Edge browser. 

I suggest that your software gurus or Lithium look into solving the problem. 

---

[TebogoM_DStv1]

Cool. Glad to hear that everything is sorted. 

[Jan-Horn]

---

@Thoko_DStv1 wrote:

Hi @Jan-Horn,

Thank you for bringing this to our attention. We have sent this to the relevant team.

Thanks Thoko. 

I changed the Page set on the tab I used to access the forum from the users on line page to the discussions page and that solved the problem for me. The problem is likely cause by some security settings made to the firewall in the update of the 8th of January. 

A new feature update 1809 loaded last night but that did not effect the issue. 

---

[Thoko_DStv1]

Hi @Jan-Horn,

Thank you for bringing this to our attention. We have sent this to the relevant team.

[Jan-Horn]

The problem is caused by the January update for Windows 10. Seem that the update is causing compatibility issues with Edge and the Community Forum software. Switching to IE11 or Firefox restore the functionality.

[Jan-Horn]

I use the option in my second screen shot to navigate and find unread posts quite extensively. Since this morning it is non functional see my first screen shot.