10-22-2009 09:35 AM
It is always interesting when you log into a site like this and there are wholesale changes. I try and work with the site for a day or so before commenting. However after a couple of days I have been struggling with two things that I want to bring to the attention of the moderators - maybe it is just me - but I notice the following:
1- Confirmation required - it seems that you now must do a lot of extra confirmation steps - IE - mark all messages read in a forum - change single message status from read to open - is there a way to eliminate that extra step - can't find anything in my setup pages.
2- Marking messages - Again - maybe I am just clueless - but prior to the changeover, if I was reading a message and wanted to mark it as "unread" I could do so anytime. Now - I am noticing that if I am reading a message (first time through) I can't do so. I have to go to another message - then come back to the one I had read previously, and now I can mark it as "unread" - Again, maybe I am just missing a setting.
Comments - anyone else?
JNCIS-ENT, FWV, SSL, WLAN
JNCIA-ER, EX, IDP, UAC, WX
Juniper Networks Certified Instructor
Juniper Networks Ambassador
Juniper Elite Reseller
J-Partner Service Specialist - Implementation
If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.
10-22-2009 04:42 PM
Thanks for the feedback Kevin, our platform software was upgraded to a new version this week. I will look into these issues with our platform vendor and get back to you ASAP.
10-27-2009 11:01 AM
Prior to this change, I was able to click on the up/down arrow to the right of the message board name, in the main listing. This would move that particular board up or down, in the list. It allowed me to put the boards I am most interested in at the top. I can no longer do this. Now, those message boards I had at the top the page are scattered.
Could this functionality be added back in?
10-29-2009 05:47 AM
Kevin, the vendor has confirmed that these 2 issues are bugs that will be fixed by end of Q4, I will keep the community updated.
We apologize for the inconvenience this may have caused