Jump to content

All Astronauts

Clients
  • Posts

    1,231
  • Joined

  • Last visited

  • Days Won

    8

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by All Astronauts

  1. In the next IPS release: Sound Board is dead.
  2. Ditto. Also a Kitchen Sink option to change to just a pencil icon or remove altogether. I really don't know anyone that uses it. The create new topic button on the forums home page is in the same boat. It never felt intuitive.
  3. 20.3.0 Available! Removed un-needed csrf in url in ACP Journal Dashboard widget Added ability to reset highest CPU load in Server Overview widget settings FIX! Permission check on Admin Logs dashboard widget for admins not in the Administrators group Mostly just a few tweaks - no biggie. The reset button for the highest load point I added mainly because one site of mine had a failing VPS that registered a crushing load of 900%+ before it killed. No sense staring at that historic outlier in the widget all the time and once things are back to normal you'll want to see what the "new high" is anyways. FYI the post above, we worked that problem minutes after the post. A particularly rare occurrence where, and I'll admit I'm guessing here as it's fixed, is that for a low level PHP call - disk_total_space (and probably disk_free_space as well), the account he was running Invision Community under would not allow you to hit '/' (aka the root directory). You can throw any directory at those commands and it will give you what you need (it is looking at the drive, not the space in whatever directory you point it at). Just changing the root slash to the directory where IC is installed resolved this. The stupid weird thing is he has another site running on the exact same server. No problems there. And - what has it been - nearly a decade of this stuff already, and this is the first time this has ever popped up. Wild. The fix for the above is NOT in this release. Not really worth it to bug staff to kill the current submission (now approved) when approvals are averaging a week-ish these days so this fix that effects pretty much one site will be a bit. I'm putting a few more safeties in places and gonna check my dev notes to see if there was anything small I wanted to throw in before pushing another release.
  4. Permission check in a dashboard widget needed to be specified to the "core" app. For regular every-day Administrators it doesn't matter - they get everything all the time. When you have *any* other kind of admin, now the permission checks actually matter, and get checked. For the Admin Logs dashboard widget, I got a check there so scrub admins don't see something there that might leak out - dunno what but thought it best to slap the permission on there. \IPS\Dispatcher::i()->checkAcpPermission( 'restrictions_adminlogs'); Fine if the containing app is Core, not so much if its not \IPS\Dispatcher::i()->checkAcpPermission( 'restrictions_adminlogs', 'core', 'staff' ); There we go. Ahh! But I see you thinking - what if that scrub admin has that permission toggled off? Yep, same problem. So two things: 1) ACP permission checks using the dispatcher method above to allow/not allow dashboard widget display are a no-go; will disallow the entire dashboard. 2) Instead, use this: \IPS\Member::loggedIn()->hasAcpRestriction( 'core', 'staff', 'restrictions_adminlogs' ) 100% chance I just copy-pasta'd the dispatcher check from the admin logs page itself while creating that dashboard widget and never thought twice about it - til now... If you need this fixed fast lemme know so I can - well - hmm - I'd want to say I'd submit a ticket but that's going away now - that was the way when we needed to request a quick marketplace approval for a bug fix that had to get out. Lemme know, I'll submit the new version in a moment, and if you need it ASAP I'll yell at someone or something.
  5. @Sonya* - file approved and available. Yell if there are problems (which would just be escalated to IPS as adding this to PCI was literally just adding 'allowStockPhotos' => true to the form helper)
  6. Version 4.0.0 awaiting approval Enables Pixabay Stock Photos for image uploads if you have set all that up in the ACP
  7. V6 inbound pending approval: TWEAK! Debug footer CSS to ensure full width across page bottom. NEW! Toggle to turn marks on/off on content pages. Will also toggle the debug feature if enabled. NEW! English stopwords filtered out of marking (full term exceptioned out of course). These are the Lucene defaults: "a", "an", "and", "are", "as", "at", "be", "but", "by", "for", "if", "in", "into", "is", "it", "no", "not", "of", "on", "or", "such", "that", "the", "their", "then", "there", "these", "they", "this", "to", "was", "will", "with" RESTORED! Stream truncation for perkier stream page loads. Click the wand, all the marks go away; click it again, all of them are back. As usual, if you refresh the page, all the searchlight stuff goes away - no changes there at all. The stopwords was needed for some time now to prevent the marking of, well, the usual junk. If you search for /this stupid thing/ OR a singular phrase /"this stupid thing"/, Searchlight will mark out: "this stupid thing" "stupid" "thing" and skip over individually flagging "this". Looking over the stop words above will give you and idea how much cleaning the marking will be now. Also noticed IPS removed results truncation (by seeing the JS truncation on stream pages making massive page warps as all that content gets removed). This was a silent pull that happened I guess with 4.6 - 🤷‍♂️ - anyways, SSSR was still truncating on search results anyways to get better matching snippets (see previous update notes) - that remains of course - but I just folded back in basic truncating when the results are meant for streams. Works nifty as usual. Available whenever (also IPS is blowing things up here tomorrow so I wouldn't expect approval anytime soon) Toodles.
  8. File was approved yesterday; upgrade away.
  9. NEW! Content Trends dashboard widget FIXED! CSS for customization - login page - login page preview invert logo not applying FIXED! Spacious IPS patches task was breaking on a global variable not being fully rebuilt quickly enough in 4.6.x., also, button was not showing unless you had the admin or mod log buttons turned on in settings. FIXED! Highest historic server load wasn't being set in the monitoring task, only while viewing System Overview widget on the dashboard. UPGRADE PROCESS! Removes legacy task. This is for the pending approval 20.2 version. Content Trends is on a 24 hour period based on when the task runs. To truly do a completely date/time accurate content stat thing would require some brutal iteration on every app and what is considered "content". IPS already records this in a round-about way by incrementing every member's total content count. So this just runs on that. Obviously this means content generated by guests is not included (does anyone allow guests to do anything anymore? Did they ever?). Also stating the obvious that you probably shouldn't bother to put this widget up for at least a week. Graphs tend to look ridiculous with only a data point or two of data. Let the task cook for a week or so then throw the widget up. I think I'm borrowing one of the graph settings from the member Trends widget. I've got note down to let you set that separately eventually. The IPS patches button I got for Spacious was slightly bugged. Many of you never encountered them ever but this should resolve those. One was me derping out the button's appearance completely - you previous needed either the administrators or moderators log button enabled for the patch button to ever show. That's fixed. The other *should* be resolved. Best I (and another...) can figure is its some weird ghost thing going on with caching "somewhere" $ipsApps is a pretty pure, always there global variable that's runs on init.php - you don't get much more bulletproof than that. So why it was erroring on that ever-present variable when one called \IPS\Application::load('core') twice in the space of three lines? Ehhh... (obligatory shrug emote) - I just do a single load now and read off that var and that probably??? has solved the problem. Oh, and I sideways caught that highest load not updating correctly in the System Overview widget. Just a miss on my part. Think that's it. Available when available. Oh, and I still haven't updated the MP description aside from the screenshots in like two years now. On it. Screens with patches button working and the new CT widget: Keen eyes will spot that highest recorded load in the background. That's what you get when your dedicated VPS is failing 🙂 Like I said, you'll need to let this cook for awhile. Looks derpy with just a few datapoints. Graph I think is limited to 30 days. As mentioned earlier, I'll get the settings to make that configurable in a future update.
  10. I got an update in-bound soon. Just a few fixes (including one for the patches thing above - more of routing around an IPS quirk than anything else) plus a new widget (probably just the one)
  11. And fixed again... Ya know, when IPS let us add fields to IPS application tables, this mod was a dorky simple set-it-and-forget-it thing. Now, ugh. Put simply, I spaced that interacting with records would actually end up re-saving the category as well, and on the front-end, with the background image merged into the Category object that means when those edits/saves occur, it tries to save the Category with refreshed information and hits that background image and tries to save it in the Category table and the field ain't there, etc... I fixed this, ate lunch to give some space, then gave it another run through. I believe I've done all the front-end testing possible. I've hit all the mod actions in record view and category view, plus new records saves, edits, and deletes. Commenting and Reviews on records cleared as well. If this still errors out after this (I don't believe it will but...) I'll need to rip off the band aid and make you guys edit your templates. Instead of $category->pcimage to get at the thing it would be something different. Probably a template plugin like {pci=$category}. Sorry for the hassle. Available when its available (3.0.6)
  12. @Koper74 Are you on CIC? Regardless, hit the support tool post-install and clear caches just as a first-line check. After that if there are still hitches, I'll need to pop in to your ACP and look (PM me credentials)
  13. Fixed. I've asked for an accelerated review to get the patch out there. The hitch was in how these are now added to Categories. It gets merged into the object and that's all well and good front-side, but troublesome with saves on the admin side. I got no idea how I missed this 🤷‍♂️ as it's rather apparent when hit. Effectively a one-line addition to fix. Anyhoo, now that this is set for 4.5/4.6 I'll make a point to look at supporting thumbnail versions of the images and adding an additional field for an array of images which you can then throw at a carousel or something.
  14. Looking @Jimi Wikman What version did you install? Just to be sure, you are using the application right? There is no code in the newest release that interacts with cms_database_categories other than to copy images to a new table and remove the PCI column from that table. The error you are showing can only appear if you are using some old stuff somehow. Shoot me an account with ACP access (via PM) and I can take a quick look
  15. You can't. As stated, IPS removed notification sounds in 4.6. Someone here (you'll need to search) asked the same and they responded it was problematic on some browsers and so on and so forth. Remember: all Sound Board did was just swap out the standard sound for custom ones; it had no interaction with the actual sound-producing code. So once that was yanked out, SB has nothing to swap anymore. And, again as stated above, I'm not that interested in re-writing that code to re-enable that functionality (and IPS would likely reject it anyways as they do not allow stuff they pulled out to be stuck back in via 3rd-party mods - at least for the Marketplace) With the move to the HTML5 browser notifications in 4.6 - the ones that pop up in the corner of your screen - sounds are definitely back in play - BUT the hitch is even though all that is spec'd out and ready to be used, none of the browsers are actually supporting it yet. It's there, waiting, but until browsers actually support it 🤷‍♂️ Now, can I attach some javascript to these notifications anyways and force sound through? Probably; but the hitch then is the thing with browsers forcing a user to "interact" with a page before allowing a sound to play and that's gonna be a problem with these HTML5 notifications - hence why they have a sound specification themselves, but, again, as stated, currently not supported by browsers. Messy all around. Sound Board is still good to go with 4.6 (though I don't think I formally updated it in the MP to flag it as 4.6 compatible?), but what you are left with is just a profile page sound block - that and all audio attachments everywhere having an audio player (god send that). Like I said above, I'm thinking about what I want to do here. It was a custom notification sound thing then I added the sound player on all attachments, and now notifications sounds are out so I'm not sure what this even is right now (toying with music manager - i.e. tracks, albums, playlists, etc. but I have so much other junk going on already...
  16. Bump now that Zapier is back on the self-hosted menu plus that @Daniel F comment routed through @Jordan Invision
  17. Ya know, just go to the task page and run it manually. If you don't have Spacious set up to put the tasks button on the Dashboard page, go to advanced settings bit in the settings area in the ACP - the first tab there, where you choose to run tasks with user traffic or cron or an outside service - just beneath that is a text link to the tasks page.
  18. Well that's a little on the odd side. Obligatory running fine locally and on all my sites. I even ran it manually; t'was fine. The only interaction with IPS\Application is in getting the Core versions: \IPS\Application::load('core')->long_version , and then same but just version Doing so will probably (maybe?) hit that $ipsApps var in those methods so that's where that's coming from - though looking it seems to be a side-ways hit at best (maybe when constructing the app obj. via load) As to why on your site? What version of Invision Community are you on? EDIT: Also are you self hosted or CIC? And to be further confusing, the var is actually set as a public static var in init.php so that's pretty much the definition of always available.
  19. 🤷‍♂️ maybe they're busy? EDIT: Will be awhile longer; you can use the same Giphy I already used. ANOTHER EDIT: Daniel managed to find this one tiny thing out of the expansive pile of apps and plugins I have (There are a lot on my dev machine that never see the light of public day) that had this one thing leftover in a post-install routine. They probably aren't paying him enough.
  20. PCI Version 3.0.2 submitted. 4.5.x and 4.6.x compatible. This moves all your images off the actual Pages Categories database table into a separate table. You do NOT need to change any of your template code; this remains 100% compatible with whatever you are doing before. Code examples for a reminder: <img src='{file="$category->pcimage"}'> The above where you have the $category variable available. <img src='{file="$record->container()->pcimage"}'> And that above for when you are in a record view template and have the $record variable available. You should be able to see the basic chain there record - then it call the container (which is the category the record is in) - and then our category image. I do have caching of the new PCI database table. 99.99% it will never be a problem, when the category is being built out it actually double checks for the cache and if not there does a load from the DB directly. If something happens though, you can refresh the cache directly in the ACP on the Pages Databases menu option and any database Categories menu option with the obvious, can't miss button up top. EDIT: Will edit/post when it is approved.
  21. PCI 3 Finally got this patched for 4.5/4.6 - will require no changes on your end at all. Might even be slightly faster (everything is datastore cached). I'll be uploading 3.x tonight and it will be approved when it is approved as all things MP are these days. I'll also post here again after I submit with the low-down.
  22. Yeah, I know that. Do you really want those to be links though? There is no indication when you click those. And now you are "doing things"
  23. I'll just go ahead and assume some JS quirk or conflict somewhere on the page. That arrow is randomly grabbing and linking out various ACP urls. In the above screenshot its clearcaches. I've seen it link out dashboard widget management, CMS page editing, and so on. Naturally you'll need more than one Admin in the ACP and that widget up on the dash to see this. I think you should keep this as a "feature" but lock it to logging the user out so other admins can mess with other admins for the lulz.
×
×
  • Create New...