Don
March 2, 2023, 11:35am
1
Hello,
There was a change to make follow page navigation compatible with the redesigned user navigation.
discourse:main
← discourse:update_plugin_to_be_compatible
opened 03:29AM - 23 Nov 22 UTC
Core has currently introduced a redesigned user page navigation which is
curren… tly considered experimental behind a feature flag. This commit
aims to make the plugin compatible with the redesigned user page
navigation.
## Screenshots
### Desktop
#### Before
![Screenshot from 2022-11-23 11-27-45](https://user-images.githubusercontent.com/4335742/203464058-65b625ff-14f2-4065-ba8f-d2333ddafb5b.png)
#### After
![Screenshot from 2022-11-23 11-27-30](https://user-images.githubusercontent.com/4335742/203464072-f671f2ab-f203-42e3-9d03-06f517ec8446.png)
### Mobile
#### Before
![Screenshot from 2022-11-23 11-29-00](https://user-images.githubusercontent.com/4335742/203464078-6e7b19cd-4503-4456-9a64-d9095533e813.png)
#### After
![Screenshot from 2022-11-23 11-29-14](https://user-images.githubusercontent.com/4335742/203464089-9c3af333-0390-4161-ab1b-dbd7b90344c9.png)
It seems to it uses the redesigned_user_page_nav_enabled
settings to change it and I think this setting has been removed so it changed back now to the follow page old navigation.
Thanks
1 Like
I am seeing this too:
Thanks for pointing it out.
2 Likes
I’ve got a PR ready here, this will fix it once merged
discourse:main
← discourse:new-nav
opened 09:30PM - 02 Mar 23 UTC
The new user nav is default in core now, so the `this.currentUser.redesigned_use… r_page_nav_enabled` prevents it from showing — this removes it as well as the old nav.
I've also pinned 3.1.0.beta1 to the previous commit, to avoid causing nav issues for older versions
2 Likes
This topic was automatically closed after 21 hours. New replies are no longer allowed.