The links in the forum for MediaMonkey for Windows ... ... fixes and improvements -> all issues in MantisBT not just those for the current build.
Tested using Firefox v120.0.1 Windows 64 bit on Windows 10 professional fully updated.
For example the latest beta has 21 fixes and improvements
but clicking on the link shows "Viewing Issues 1-50/17470"
MM5 New Beta, fixes and improvement link -> search not occuring
Moderator: Gurus
Re: MM5 New Beta, fixes and improvement link -> search not occuring
Link works here.
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: MM5 New Beta, fixes and improvement link -> search not occuring
Same here as op, if i click on the link it takes me to the same page as his screenshot, if i copy the link and paste it in a new tab it works.
Re: MM5 New Beta, fixes and improvement link -> search not occuring
I see the same thing from the link in Rusty's post, ie. a list of 17470 issues, not filtered to the 21 items that he says were fixed.
Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
-
- Posts: 114
- Joined: Mon Dec 31, 2012 11:41 am
Re: MM5 New Beta, fixes and improvement link -> search not occuring
Ditto for me. Clicking on the hyperlink opens the full list. Copying the link and pasting in a new tab opens with a filters list for this release. Very strange.
Re: MM5 New Beta, fixes and improvement link -> search not occuring
Retested with DuckDuckGo, Firefox, & Safari on iPhone both on wifi and 5G. All same results.
Thanks for the work around.
Re: MM5 New Beta, fixes and improvement link -> search not occuring
Now works as expected for me.
Thank you who ever fixed it.
Thank you who ever fixed it.
Re: MM5 New Beta, fixes and improvement link -> search not occuring
I've been also experiencing this issue (depends on browser -- using Chrome)..
We were solving this issue with the team and should work fine now (at least works for me now in Chrome
We were solving this issue with the team and should work fine now (at least works for me now in Chrome