Moshe1010
Well-known member
I don’t see why would users need to refresh a single page on my boardWe use this script for that. If you're not sure how to implement it, I'd see about hiring @Russ.
I don’t see why would users need to refresh a single page on my boardWe use this script for that. If you're not sure how to implement it, I'd see about hiring @Russ.
I don’t see why would users need to refresh a single page on my board
Not to mention they can just click the site logo to refresh, it's the same thing you just don't drag to do it. To me this is a trivial issue that doesn't seem to impact anyone in any real way.I don’t see why would users need to refresh a single page on my board
That wouldn't refresh the current page though, it would just link to the home page.Not to mention they can just click the site logo to refresh,
/* add refresh fontawsome image */
.p-navgroup-link
{
&.p-navgroup-link--refresh i:after
{
.m-faContent(@fa-var-refresh);
}
}
<div class="p-navgroup p-discovery{{ !$xf.visitor.canSearch() ? ' p-discovery--noSearch' : '' }}">
<a href="javascript:window.location.href=window.location.href"
class="p-navgroup-link p-navgroup-link--iconic p-navgroup-link--refresh js-badge--refresh"
title="Refresh">
<i aria-hidden="true"></i>
</a>
Seems too crowded out there in your navbar.I've added a refresh button to the top that will reload any existing page the user is on. Here's how if anyone's interested.
View attachment 284372
Add this to the extra.less template
CSS:/* add refresh fontawsome image */ .p-navgroup-link { &.p-navgroup-link--refresh i:after { .m-faContent(@fa-var-refresh); } }
In the PAGE_CONTAINER template find:
HTML:<div class="p-navgroup p-discovery{{ !$xf.visitor.canSearch() ? ' p-discovery--noSearch' : '' }}">
Add this just above it:
HTML:<a href="javascript:window.location.href=window.location.href" class="p-navgroup-link p-navgroup-link--iconic p-navgroup-link--refresh js-badge--refresh" title="Refresh"> <i aria-hidden="true"></i> </a>
Hey, that’s a cool idea actually.I've added a refresh button to the top that will reload any existing page the user is on. Here's how if anyone's interested.
View attachment 284372
Add this to the extra.less template
CSS:/* add refresh fontawsome image */ .p-navgroup-link { &.p-navgroup-link--refresh i:after { .m-faContent(@fa-var-refresh); } }
In the PAGE_CONTAINER template find:
HTML:<div class="p-navgroup p-discovery{{ !$xf.visitor.canSearch() ? ' p-discovery--noSearch' : '' }}">
Add this just above it:
HTML:<a href="javascript:window.location.href=window.location.href" class="p-navgroup-link p-navgroup-link--iconic p-navgroup-link--refresh js-badge--refresh" title="Refresh"> <i aria-hidden="true"></i> </a>
I wonder if this is coming with 2.3 since we know 2.3 will have a dark style.and enabled automatic dark mode via this js:
I'd be down for this as long as it can be over-riden by users.I wonder if this is coming with 2.3 since we know 2.3 will have a dark style.
It's coming.Any updates?
It's already here and there's no need to wait if you don't want to. We've been using it on my site since iOS 16.4 came out and it's working great, engagement has really picked up as a result of notifications (especially response times).It's coming.
Only problem, it's not fully implemented in 2.2.12. There are still some issues that need to be addressed.It's already here and there's no need to wait if you don't want to. We've been using it on my site since iOS 16.4 came out and it's working great, engagement has really picked up as a result of notifications (especially response times).
He referred to the fact that there is an add-on for that without waiting for stock implementation.Only problem, it's not fully implemented in 2.2.12. There are still some issues that need to be addressed.
I'm well aware that there is an add-on to do it.. BUT the fact remains, it's not here in 2.2.12 and there ARE bugs in the 2.2.12 implementation. Not everybody is crazy about jumping onto an add-on that could cause issues in the changeover to a 2.2.13 implementation.He referred to the fact that there is an add-on for that without waiting for stock implementation.
The only issue that we couldn't overcome (which involves a core js file) is to show the number of notifications on the app's icon. Other than that, there are no bugs or issues that I know of (nor the developers of the add-on).ARE bugs in the 2.2.12 implementation
This is not true. Worst case scenario users will need to re-install the app.jumping onto an add-on that could cause issues in the changeover to a 2.2.13 implementation.
You really don't think that's an issue? How many will actually read a notice on your site saying "we need you to remove the icon from your "desktop" and then recreate it"?This is not true. Worst case scenario users will need to re-install the app.
Agreed...and I am pretty sure that's what I already stated. There are tons of bugs being listed as fixed for ANY admin that will take the time to check, and that usually means that a xx.yy.ZZ release is in the near future.I think honestly that license holders just lost hope (and maybe trust) in XF devs' timelines, so that's why they are ready to jump pretty fast on add-ons that solve their issues or implement new features they want.
If it was really helpful for them, and they liked it, they will remove the current app and re-add the new one. It's a process that takes less than 30 seconds to do. If they are too lazy to do so, they can keep using it without notifications like they "used to" a few weeks back.You really don't think that's an issue? How many will actually read a notice on your site saying "we need you to remove the icon from your "desktop" and then recreate it"?
Not having forward/back and refresh buttons is not an issue. It's more of a feature request. You can move forward/back via touch – iPhone users are doing it for years in many apps.In addition, I've seem a few posts of more issues than simple "number of notifications".
HYS (just screenshots or a video) of XF 2.3 was also promised to be out in the next "coming weeks". These promises will celebrate a year in the next 2 months. So technically a year is around 52 weeks, but I think this wasn't the intention.Agreed...and I am pretty sure that's what I already stated. There are tons of bugs being listed as fixed for ANY admin that will take the time to check, and that usually means that a xx.yy.ZZ release is in the near future.
Historically, when we've seen this many bugs addressed this quickly, it's a VERY strong indicator that at least a point release is near.... now, what all "goodies" that gives extra remains to be seen.It happened more than once, by various XF devs, so that's why users just don't really believe this anymore.
We use essential cookies to make this site work, and optional cookies to enhance your experience.