All Astronauts

public static function roundedDiffFromSeconds( $seconds, $memberOrLanguage=NULL ) { $now = static::ts( time() ); $then = static::ts( time() - $seconds ); return $now->roundedDiff( $then, $memberOrLanguage ); } Don't panic! This is not related to all the other DateTime shenanigans going on. Just a small bug with a big return - routinely 52 years. The problem is having $then calculated as time() - $seconds. That needs to just be seconds: $then = static::ts($seconds); You only use this in one spot (admin\stats\timeToSolved.phtml) that I can see so probably just been overlooked for a while. Full Explained working on something not quite two minutes old: $now: 1663390800 $then: 1663390800 - 1663390700 = 100 $now->roundedDiff ($then); roundedDiff then immediately calculates its own difference: $this->diff($date) which in this case is $this->diff(100) which is the difference between right now and 100 seconds after January 1, 1970 midnight UTC.

Based on that plugin what formatting do you want? This is just a few minutes of work, if that.

Version 14 submitted! 4.7 compatible Changed hook points in post templates "Month Day, Year" format now actually "Month Day, Year" instead of IPS relative. The hook points needed changing to account for newer structure there. The first option to force it to the bottom remains as is. The other two options, above or below post count, are now technically, above and below the data-role="stats" section which contains the post count stuff. Within that is another UL list and it is all flex based so rather than deal with all that I'm just staying out of it. And yes, the former MDY option was just IPS relative style so you probably had 1 year ago, 2 years ago, and so on there. This is patched now. If there is a want/need for the relative style just yell, it's just a few minutes to add to the template and an additional setting. Available in the MP when approved.

Care to remind me exactly what this was?

What restrictions (on what section or app) are you trying to set up? I'm assuming this is in Members - Staff - Administrators where you config this and not editing the Group itself.

Version 8 submitted! 4.7 etc. etc. There was no version 7, I just skipped a number by accident. Derp.

Version 12.0.0 submitted! 4.7 (and of course, 4.7.2) compatible Some CSS and language string changes @MInced meat the dither is gone now. Available when approved.

It's end-of-life - will not be upgraded. I made a new BETTER version that handles more than forums - it is the upgrade for newer versions:

FYI I didn't think final was coming out today - so... 4.7.2 has breaking changes with the whole PHP8 checker thing. This app is the only one of mine mostly caught up in this. It's patched but I have to submit again, etc. So if you do upgrade, do not be surprised if it gets disabled.

Easy. I'll make a note for the next release.

You'll have to manually open it with a database edit. For plugins just the 'disabled' and 'requires manual intervention' fields in the entry need adjusting (to zero); ditto for applications. You probably need to dump your datastore after making the manual edits. Also, you are right @aXenDev, this current beta 5 still locks on upgrading. If they are making just an IN_DEV check, then yeah, it would still lock as we upgrade outside of dev mode. If IPS is actually checking for the -TESTINSTALL flag on the key, then it's just broken. I suppose I'm lucky. Just one thing locked for me... that has been running on PHP 8 for a year. I'm more weirded out by all the log messages saying it can't parse the plugin directories as they think they are not there. EDIT: The latter is caused by missing widget and tasks directories. They can change the log message for that to better indicate that is the problem rather than just say the plugin directory itself is the problem.

@OptimusBain all good with the new version?

I'll show myself out...

All written up. Even handles them when a new post is made and the post is ajax'd in. Do I resubmit now? Pretty sure Daniel et.al. are sick of seeing this already. Either way, this will be fixed forever and ever... in the next release.

FYI anyone reading this. It's an unsolvable problem: when something else is in the first position of that post menu. Alas, the :has CSS selector is still in its infancy and not quite ready for mass adoption yet so... grumble... , I'll eat this and add some derpy Javascript code to deal with this once and for all.

Eh, I'm just puttering on various things on the back deck right now (upper 70s, low humidity, nice breeze - yes...) so shoot me a PM with your site (and ACP access which I imagine I've already done with you before) - and I can look closer. At least maybe see what bookmarks is doing there to muck it up.

PM me an ACP account for me to take a look, based on what you said I'd have to pop in and check directly. Are you on CIC or self-hosted?

It's going to be Bookmark. Specifically, because it stuck itself at the front of the list. I was doing an even/odd thing in the CSS to hide this and appending this button to the front breaks that. This whole area is a hot mess when it comes to multiple third-party hooks and such. Although... I haven't changed this code in ages - maybe there is better targeting available now? Checking. EDIT: So now I remember why. The targeting with competing plugins back in the day was hell so I just gave up and did the even odd thing. I can still do this with CSS using nth-of-types now (maybe before too - the mind blurs when you are down some CSS rabbit holes) I'll submit a new version - gives me a chance to get the version language strings right internally.

I've just toggled on and off (and saved) the settings you have posted up in the off-chance something was spilling over, or I mis-wrapped an if-check in the CSS. I'm not getting this. Is this happening on the default theme? Also... toggle off the Bookmark and Tutorial apps when testing. It would not surprise me if we were stepping on each other's toes here. While you are doing that I'll look at the hook more closely and see if that is the hitch here.

I just woke up, didn't even know it was approved yet 😀. Un momento por favor...

Version 3.0.0 submitted, available ??? 4.7.0 Compatibility Sweep NEW! Added to Font Awesome 6 to the Font Awesome chooser. Font Awesome 5 remains as an option. A few CSS patches here and there. If you are using the Font Awesome chooser in KS, you are using FA5. This KS now supports FA6 and at a glance, it is more sizing-compatible with FA4 than FA5 was - that is, some FA5 fonts that swapped in for FA4, the sizes were a little off; that's no longer the case (mostly, have not looked at every FA instance). I'd switch the FA6 but I left the FA5 option in place as some of you might have "stuff" going on. Couple CSS changes I'd probably only notice. Uhhh... made sure everything was working? Tested on 4.7.1 107021, PHP 8.0.13. Oh, and I forgot to change the version number on the internal language file so the ACP settings area will say 2.2.whatever. Already patched for the next release.

Now that 4.7.1 is out I should get along and update this.

This on 4.7.x?

@HDiddy and all. Approved. Have at it.