Yes, the only new thing there is "Watched" which could be on the old layer to save space.
But what about when you are in a thread? Is the new white menue bar useful there?
You didn't quote so I don't know if you're addressing my post, or the one above mine. If mine, when you say new and old, what is the new, and what is the old?
Hi Jason,
I appreciate the work that you and the team put into this migration and I like the new look of the site now. But isn’t one of the prime directives of a website migration is to preserve links to existing legcontent? Must all of these be manually edited now to remove the .xx added to the URLs of DIYA referenced images?
My threads typically start with dozens of inline images linked via URL’s to either images in same thread or images from other DIYA threads. These are typically architecture diagrams, schematics, sketches, errata photos, or images of the final build and examples. All very important for the viewer to understand the thread and what project is about.
I literally have hundreds of broken links in all my threads. Some threads are hundreds of pages long. It would not be practical to submit every broken link to what appears to be a global issue affecting the treatment of DIYA image URLs, post-migration. Is there a setting that can be applied globally so that cited inline URL’s do not get corrupted?
It’s ironic that only the referenced URL’s to externally hosted images were not corrupted. Citing DIYA hosted images because I wanted to avoid this for robust operation through time was my main reason I did so, only to find out that because of that, the links are no longer any good.
Thank you,
xrk971
some examples of highly viewed threads first post, new rendered unreadable:
nearly 1M views…
https://www.diyaudio.com/community/threads/mini-karlsonator-0-53x-with-dual-tc9fds.239338/
https://www.diyaudio.com/community/threads/10f-8424-rs225-8-fast-waw-ref-monitor.273524/
https://www.diyaudio.com/community/threads/alpha-nirvana-39w-8ohm-class-a-amp.344540/
I appreciate the work that you and the team put into this migration and I like the new look of the site now. But isn’t one of the prime directives of a website migration is to preserve links to existing legcontent? Must all of these be manually edited now to remove the .xx added to the URLs of DIYA referenced images?
My threads typically start with dozens of inline images linked via URL’s to either images in same thread or images from other DIYA threads. These are typically architecture diagrams, schematics, sketches, errata photos, or images of the final build and examples. All very important for the viewer to understand the thread and what project is about.
I literally have hundreds of broken links in all my threads. Some threads are hundreds of pages long. It would not be practical to submit every broken link to what appears to be a global issue affecting the treatment of DIYA image URLs, post-migration. Is there a setting that can be applied globally so that cited inline URL’s do not get corrupted?
It’s ironic that only the referenced URL’s to externally hosted images were not corrupted. Citing DIYA hosted images because I wanted to avoid this for robust operation through time was my main reason I did so, only to find out that because of that, the links are no longer any good.
Thank you,
xrk971
some examples of highly viewed threads first post, new rendered unreadable:
nearly 1M views…
https://www.diyaudio.com/community/threads/mini-karlsonator-0-53x-with-dual-tc9fds.239338/
https://www.diyaudio.com/community/threads/10f-8424-rs225-8-fast-waw-ref-monitor.273524/
https://www.diyaudio.com/community/threads/alpha-nirvana-39w-8ohm-class-a-amp.344540/
Excellent...the classic theme is fixed for visiting without logging in. Looks almost as it was before the upgrade and easier to navigate.
Well done and thanks for listening to users feedback and acting.
Well done and thanks for listening to users feedback and acting.
Anyway, back at desktop now. Just to be clear, I have not and will not reference the old site.
The added 2nd level nav does not work on iPhone/Safari in portrait but does in landscape. Appears the same on desktop/Safari and tablet/Safari. However, it is just a geography change on a single page as the buttons were moved from the stack menu to the 2nd level menu on the /community page only (half true, more below).
Once you navigate away from /community, the 2nd level nav changes to a forums index that isn't, and jump menus. This isn't how people will typically navigate, and the items that were moved from the stack menu are now inaccessible as they don't exist in the stack or the 2nd level nav. The only way to click New Posts, Watched, etc. is to go back to /community. I'm sorry, but this doesn't seem to make a lick of sense.
2nd level nav should be static, preferably always visible, and contain at a parent level at least New Posts, Watched Threads, Watched Forums, and Mark All Read as a minimum, as those are the actions the majority of people will use most.
There is no link to an actual forum index on mobile which would be really nice to have: https://www.diyaudio.com/community/forums/-/list. I can get there on desktop and tablet though it's a bit clunky.
On my phone in portrait mode there is the drop down on the upper left that takes me were i need to go. In landscape mode I see the same nav bar as on the desktop
Ya. Mobile's okay. Would be good if what you're calling Find Content was auto-expanded, and to have a real forums index (which is an index of forums).
Audentio said:
Wow your an admin too then?? (A co-admin here)
Thanx for helping us,I know Jason is busy and he might not have gotton it done as fast....
If you dont mind me asking,what is your site buddy??
Permanent column for mobile, no. Click the hamburger, get a menu auto-expanded to show those common actions.
Hi there, after the initial shock with the new layout/design, I'm afraid it's not for me.
Looks like every effort is made to be more accessible for iPad/iPhone readers instead for desktop use - too big letter set, too big icons, too little info on the front page unless you click and choose from menu... for an old user like me too confusing and hidden...
I did not try yet the classic mode...
I'm afraid this will be my last post... for similar reasons did not look or post at then new Audiokarma layout - so only left Audio Asylum for time being with "'normal"' look...
Thanks for everything you did and still do for Audio community!
Best regards from Tubemax!
Looks like every effort is made to be more accessible for iPad/iPhone readers instead for desktop use - too big letter set, too big icons, too little info on the front page unless you click and choose from menu... for an old user like me too confusing and hidden...
I did not try yet the classic mode...
I'm afraid this will be my last post... for similar reasons did not look or post at then new Audiokarma layout - so only left Audio Asylum for time being with "'normal"' look...
Thanks for everything you did and still do for Audio community!
Best regards from Tubemax!
For mobile it's already there - just need to make 'Find Content' expanded by default, and once you've enough analytics, order what's within by usage.
Yes, this has been reported half a dozen times now - there is no need to mention it again unless you enjoy typing, but I will continue to let you know I have read your comments about this and let you know the issue is being looked into and will be resolved.
Change is hard. If you are using desktop, there is a "Forums" dropdown mega menu in the top of the screen. It's always visible so you can navigate to every section of the site with two clicks at any time. Try using that.
I'm happy to see if there is something that can be done about that - I'm surprised it used to work differently.
Please give the new design some time, it may grow on you. Be sure to check out the classic theme if you liked the old look and know that it will be modified slowly over the next 2 months to get even closer to the original.
If you have some constructive criticism, please post it. It will be warmly received. Please ensure you have read my many-mentioned comments about the fact we launched earlier than I would have liked, with imperfect aesthetics but working features, so that we could avoid actual disaster.
The old site had been teetering on the edge of actual disaster for a long time, every day it remained up was a lucky day.
If you forgot to add a /s to the end of your post, I understand as well.
As mentioned later in this thread, all the same content is still here. As for making it beautiful, that's coming in due time.
XenForo curiously does not have this feature. I also had 50 as my setting as I prefer not to have to needlessly click around.
One interesting problem with having a changeable number of posts-per-page (PPP) is that in the old site people would copy the link to a post using their URL bar which contained "page XYZ". Of course that page was specific to the PPP setting they had, and those links never worked for people like us who were using 50 PPP.
Now we have (currently) moved from 10 PPP on the old site to 20 PPP as the (unchangeable) default. I think 20 is a good compromise for now. We might install a plugin to allow PPP to be changed in the future. The new links that XF produces (there is a share icon in the top RHS of each post, as well as you can right-click copy the link in the post number) are PPP agnostic, do not contain an HTML "named anchor" and will work forever, on any platform, no matter the PPP setting. So at least if we do allow changeable PPP in the future it shouldn't break anything like it did in vB.
Just one of the many new features in XF that is going to make the site better and more reliable for everyone in the community moving forward.
Life is only suffering and impermanence 🙂
What just happened to the menu bar?? I've been clicking on "my posts", but the heading along with others pertaining to my interaction are all of a sudden no longer there!
..and what's with the wonky answers I keep getting from Galu over at The Lounge? 😵
..and what's with the wonky answers I keep getting from Galu over at The Lounge? 😵
Last edited:
- Status
- Not open for further replies.