The Official Vivaldi.net Bug Thread (Not for Vivaldi browser!)
-
This morning it says there are two new posts in that thread… click it... top of page 103 and oviiione is still the last poster.
Funny if we've hit the thread limit here - in the Opera forums I was part of a gang trying for "The World's Longest Blog" and (somehow) by talking garbage and playing games with each other there we managed to reach far into the tens of thousands of posts on a single thread. Eventually it was us who got bored of it, not Opera's website!
-
Whenever I post something in the forum, I can't see it in that topic afterwards. Heck, I don't even know if someone can see this post here.
-
Aha, this one I can see, but not the one in the feature request topic – strange.
-
I am surprised that you guys are still using forum to keep track bug reporting. Why don't employee some real bug management system, e.g. Jira or bugzilla or whatever to manage bugs/issues/feature requests to both browser and your website?
-
I am surprised that you guys are still using forum to keep track bug reporting. Why don't employee some real bug management system, e.g. Jira or bugzilla or whatever to manage bugs/issues/feature requests to both browser and your website?
The official bug tracking system is at https://vivaldi.com/bugreport.html
-
Whenever I post something in the forum, I can't see it in that topic afterwards. Heck, I don't even know if someone can see this post here.
I've had that problem too before, on and off.
-
When I followed the last post link to the feature request thread in the forum index, there was no post on the last page (19) as in the screen shot below.
[attachment=3492]Page19Blank.png[/attachment]
Attachments:
-
When I tried to report a forum message to moderators, I got:
Error
Invalid address: kumiponiWhat does that mean?
-
Hi,
not sure how or why but my account is now listing everything in Russian. Please help me change this back to English,
HELP!
Thanks
Glen
-
Report to moderator link no longer works for me. I always get an error message:
Error
Invalid address: PesalaHas my name been blocked for using the link too much ?
I usually only use to report threads in the wrong language posted in the English forum (or for reporting spam).
-
@Gwen-Dragon:
As i heared from Steinar, one of the Webdevs for Vivladi.net, the CMS software's API has a mail handler bug; they have to wait until the producer fxes it.
Thanks. I didn't notice the previous post about the same issue.
Meanwhile, the moderators could look out for posts in the wrong language, and just move them to the right forum. The other language forums are easily missed by new members.
-
Hey! Sorry about this. Seems to be a bug in the latest kunena forum, we updated earlier this week. I've now set the checkbox to off by default (opt in)
The Quick Reply button still defaults to "Subscribe." Is that another oversight, or was it intentional?
How long will it be before the forum code gets transferred to a new system? What is it going to be?
-
The feature request thread apparently has more comments than the software can manage. It takes between minutes and hours for new comments to appear on line and be able to be read..
I don't think new posts ever appear. The thread has become useless.
Can the moderators not split the last twenty or so requests to a new thread, unstick the original thread, then stick the new thread?
Or post a new thread, with a link to the old one, stick the new thread, unstick the old one, and merge the last twenty or so posts with the new thread.
-
Mods are able to read all of the new comments in the Feature Request thread. Non-mods are not, as I could tell before I was a mod.
Let me investigate how your request might be implemented. I'm not sure comments can be transferred between threads. The least-worst solution might be to lock the old topic and begin a new one.
Edit - maybe they should both be sticky in case anyone wants to search or skim the old one before posting in the new one.
-
Edit - maybe they should both be sticky in case anyone wants to search or skim the old one before posting in the new one.
People won't know which one to post in. Just add a link to the old one from the new one, and lock the old one. Most of those FQs have been repeated umpteen times, and many have been implemented by now. If you have time, you could even add a bullet list in the new thread with the most notable Feature Requests.
On the old Serif forums, the moderator used to start a new thread every time the old one filled up.
-
If they are both sticky and one is locked, then obviously no one will post to the wrong one.
Edit: And, yes, it looks like I can move a comment to another topic.
-
If they are both sticky and one is locked, then obviously no one will post to the wrong one.
True, but users may open the wrong one without realising that it's locked until they try to post in it. If it's not sticky, they will always open the right one, and only view the old one if they want to check previous requests. Most probably won't bother if you can find time to summarise the most frequent requests in the first post.
[ol]- Sync
- Speed dial enhancement, etc.
- Improve Bookmark Organisation
- Enhance Mouse Gestures (FlipBack, Middle-click)
- Scroll zoom slider with mouse-wheel
- View Passwords in Settings
- Dock Developer Tools
- Drag and drop tabs to new window, and within tab-stacks
- Autohide toolbars
- Show image properties on context menu
[/ol]
That would save users a lot of time, and might reduce the number of duplicates slightly.
-
I would take me a few days to work up the summary.
-
I don't think it's worth spending a couple of days on. I spent a few minutes to collect ten points. If there's many more than that, people's eyes soon glaze over. The list can be added to gradually as you remember important stuff that keeps coming up.
-
I created the new topic and locked the old one. I left them both pinned.
People may message me with items they have noticed should be on the Frequent list. That saves repeating them in comments within the topic.
When I first moved some comments over from the old topic, they were all uniformly OLDER than my initial comment, so my introductory comment was 16 slots down, and there is no way to edit the dates on it or move it to the top. That also created the impression that the topic was initiated by someone else. So I imported one of my MUCH older comments from the old topic and made it the introductory comment, which now makes the topic look very old, but at least the comments are in an order that makes sense, and it's again clear that I opened the topic.
(Thanks, Pesala for the idea of importing and editing an older comment).
