Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


 Content Type 



IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog



Everything posted by Flitterkill

  1. If you want to throw money at me to take a look I'll be glad to but since this works on the default theme you otherwise need to talk to your theme author and see what they are doing I can increase the numbers, that's no problem, also will tackle adding a widget for this.
  2. Of course, as long as you are current on renewals it will be avail. Only time I see a re-buy in the future is with ips 5 and that's years away.
  3. That options menu Cog Wheel stuff is a nightmare to deal with (I'd have to write a paragraph or two to explain it...) involving permissions checks that have to be added and 3rd-party application hooks into this area being over-written by KS and no easy way around it. I've made a few specific app fixes but honestly it's more trouble than it's worth (and none of them move things into the options/cogwheel bit - they make sure they are stuck in there at the bottom.) I'm strongly considering pulling some things out of the KS plugin and sticking them in an application to tackle some of these problems. In this case it would literally be just a single hook for this forum post menu bit, and you would have to drag the application to right after the Forums app in the app list. That way, it would let you move the edit and quote buttons into the options menu, and change it into cog wheel if you like, but would cause zero conflicts with any other 3rd party stuff. No 3rd party stuff would appear in the options menu though, there is no real way to handle that at all, at least on my end.
  4. My setting for this in KS is universal; I do have adding forum/category filtering on this but again that's universal still. What you ask is certainly doable but it would need to be in a separate plugin as you want is more involved than just simple setting checks. EDIT: Doh, signed in under a different account, this is AA.
  5. Confirmed (with Chrome and Edge at least). You just need to collapse the browser width to less than 1300px to get it to break. Do that, or even less wide, and now look at how the images set up and try to scroll down the page. There is a hell of a js controller attached to the image tables in Gallery and what you are seeing is that controller not working correctly (image thumbnails spread out past row width into body elements, unable to scroll down the page without it immediately popping back to the top, throbbing elements, etc.). I submitted a bug report regarding it during the beta (and eons past too) but to fix it is some kind of work. I'm assuming something was done to it but appears still messy. I imagine Rikki is rocking back and forth and muttering to himself at the prospect of looking at this controller again. The problem is in how the controller wants to collapse the image table as you shrink the browser. It wants to stick as many images as will fit at the correct aspect ratio per row. Once there isn't enough room it will either resize the images in the row to get them to fit, or once it hits a certain limit, will remove/add an image to the row. When the browser is wide, past that 1320px max-width (or whatever that number is) the controller is all set and happy. But as you collapse the browser width, it's losing the certainty it has to have and freaks out. I have some thoughts on fixes but its a messy messy job.
  6. Just a bump to let everyone know this is all prepped for 4.2. I'll stick it in the marketplace when the release candidates hit (or final if they skip those). Don't bother running this in 4.2 right now. The version avail in the marketplace is fine for the widgets component but the theme is way broke with the changes IPS made to the ACP, FYI in the near-ish future IPS will be removing the ability for the ACP to have customizable themes. No worries - I'm in the process of moving all the Spacious ACP theme stuff into the Spacious Widgets app. At which point since this will just be a single thing again I'll rename it to just Spacious or Spacious ACP. Won't happen by the 4.2 release but soon after.
  7. I'll need to see how the Post Notes author is adding his menu bit. Can you pm to me your site address and some acp credentials? I can take a look at this now.
  8. Is Kitchen Sink the first plugin in your list of plugins? If not drag it to the top and try using Post Notes again.
  9. Just a bump to those still following this. One of the recent 4.2 alphas has done this. You can now pass through a plugin/app setting for the color component instead of just a theme setting. Opacity still must be a hard-coded value. It really is a nothing burger to allow theme/app/plugin settings to be parsed on opacity as well. I *strongly* encourage you to consider including this before 4.2 goes final. As is, I've already written a derpy plugin to account for these guys on opacity and will be releasing to the Marketplace said plugin with the release of 4.2 and will be including it with my apps/plugins by default. I'd rather have a single hook tackling this than everyone else writing the same and traffic-jamming hextorgb with the same calls over and over again. Unless, of course, you include this stuff in hextorgb by default...
  10. Agree, but it won't be in Spacious Widgets though. It's in my to-do pile* though * Warning! It's a big pile...
  11. 2) Maybe 3) I believe IPS incorporated this into 4.2 1) See attached, coming in 4.2 KS. (there is something attached but IPS forums are broken right now and not displaying anything - smells like something Cloudfront is cooking)
  12. /* FOLLOW */ div.ipsFollow.ipsButton.ipsButton_light.ipsButton_verySmall { height:26px; } div.ipsFollow.ipsButton.ipsButton_light.ipsButton_verySmall a { line-height:22px; min-width: 75px; } html[dir="ltr"] .ipsFollow > a:not( .ipsCommentCount ){ left: 0px; padding-left: 0px; } .ipsFollow .ipsCommentCount, .ipsFollow > a > span.ipsCommentCount { margin-top: 0px; } That should get you close. Add to your custom. I tried but the file wouldn't save. a.cEvents_event, .cEvents_event a, .cEvents_event.cEvents_empty span { border-radius: 2px !important; } Either add that to custom or find that bit in the ks.css file and add !important to it. Something in your theme or customizations is over-writing the kitchen sink stuff. It just needs the !important tag to take precedence.
  13. FINAL 4.1.x UPDATE! No version change, just wraps up that last bug thing mentioned above. 4.2 version is just about done. The only things left are the follow button stuff and I'm not sure what to do with the "Add the last post datetime to the section title on topic view?" as that section title line is now gone. A div appears once pagination kicks in but otherwise... Outside of those things KS is 4.2 ready. Price increase with 4.2. $12 to $15 to get in depending on how drunk I am when I release the 4.2 version. Renews the same $5.
  14. 4.2 default widgets style vs Spacious ACP. I shrink up the header. Also, these two widgets are modified. The improved admins online (which really should be renamed Admins logged into the ACP) and the IPS news widget with much better spacing.
  15. Plugins (or apps) that have theme hooks. Hook to change color on element or whatever. That's what i'm using it for. Suppose I have a plugin that changes the background color on an div element that is above the page body which has a nice background image. If I want to just change the color of the element I can use the standard color form element, save it in the plugin settings, and toss out some css like so: background: {setting="my_plugin_bg_color_setting"}; But, if I want this element to carry some transparency on it so some of that nice body background comes through, I need to add transparency. Note I cannot just do an straight up opacity css call on this element as that will make the div and all of the contents within that opacity. So this background color needs to go rgba. In the early 4x days if we wanted to do this and allow users to change stuff up we added a text field and told them to enter the rgba themselves (text form element) and then we would jack that in the css with essentially the same css as above. Problems being users entering it incorrectly, no color picker, etc. When you secretly added the hextorgb plugin we got halfway there to solving this. This output plugin still won't allow me to let users choose an opacity along with a color directly - that would make this thing perfect - but right now I can do the following: Color picker to plugin/app setting Select box with a couple opacity options (solid, 80%, 50% matching to 1, .8, and .5 respectively) Then in the plugin/app css I do the following {{if settings.boxtrans == 0}} .thing { background: {setting="boxtrans_bgcolor"} !important; } {{endif}} {{if settings.boxtrans == 1}} .thing { background: {hextorgb="boxtrans_bgcolor" opacity=".8"} !important; } {{endif}} {{if settings.boxtrans == 2}} .thing { background: {hextorgb="boxtrans_bgcolor" opacity=".5"} !important; } {{endif}} This allows the user to use the color picker, and still gives them some easy opacity options. Having them paste in the rgba directly is still better from a customization standpoint but we lose the color picker. Of course, there is no reason not to include the same theme/plugin/app settings check on the opacity option on hextorgb. Right now we can't as there are no checks for theme or app/plugin settings on that variable in the method. If you do add those checks I can use two settings then - one for color, the other for opacity amount (number form helper instead of the hard-coded opacity options like I give above) and then pass those settings respectively through hextorgb. Please strongly consider this - it would make life a ton easier for a lot of people. I could hook in the same checks on opacity myself and "complete" this hextorgb plugin but I really don't want to come to rely on it in the long term. I would have to include it as a separate plugin from whatever app/plugin I'm working on to cut down on just my own instances of this hook and that doesn't take into account anyone else who starts copying this technique. I'm sure having 10 to 20 hooks on convertToRGB all doing the same thing would work fine. Hilarious, but would work. Maybe not the best practice though... Thanks for giving this a look - a couple of lines and a ton more functionality (until the day you refactor the colorpicker to include opacity - yes, I know the history of why you have what you have right now - I can still dream though ). EDIT: If I really wanted to get around this I suppose I could skip using hextorgb in css and instead plaster it on as a style call on elements directly in phtml templates. In that case I could grab the settings and stick them in as {$var} elements and that would probably parse fine. {{$color = IPS\Settings::i()->bgcolor;}} {{$opacityamount = IPS\Settings::i()->opacity_number;}} <div class="whatever" style='background:{hextorgb="{$color}" opacity="{$opacityamount}"};'> Wheee </div> But I'm not sure those nested vars would parse. Maybe?.
  16. remoteVerify (Boolean; optional; default true) When the dialog contains a form built using the IPS4 PHP framework form helper, this option instructs the dialog to automatically validate the form values and present any errors to the user. remoteSubmit (Boolean; optional; default false) When the dialog contains a form built using the IPS4 PHP framework form helper, this option instructs the dialog to submit the form values via AJAX. If remoteVerify is also true, two separate AJAX requests are fired; first, the form is validated, and if successful the form is submitted with a second request. If remoteSubmit is true, after a successful submit the dialog is closed automatically. If the flashMessage option is provided, it will be shown at this point. By default, remoteSubmit is false, which means forms submit via a traditional page reload.
  17. Thanks. To anyone who needs this in the near-term, the hook is literally just what I posted. Code hook on IPS\System\Output\Plugin\Hextorgb. The plugin itself seems to have changed recently-ish (4.2? Sooner) so the actual hook is on a function within now. static public function convertToRGB( $data, $opacity ) { // Patch to allow app and plugin settings to parse through if ( isset( \IPS\Settings::i()->$data ) ) { $data = \IPS\Settings::i()->$data; } return call_user_func_array( 'parent::convertToRGB', func_get_args() ); } You're just front running on $data, getting the app/plugin setting before throwing it back into the function.
  18. Went ahead and added background images to the login page. All the usual Spacious settings are in play including color changes (backgrounds, buttons, and text), adding text, etc. You can also toggle the login box background transparency: solid,80%, and 50%. This all for the upcoming 4.2 release.
  19. It's a two-second hook to work around... but it's still a hook that really doesn't need to be made.
  20. You check for theme settings but not for regular app/plugin settings. Just splash this in after the theme setting check. if ( isset( \IPS\Settings::i()->$data ) ) { $data = \IPS\Settings::i()->$data; } Works great. You'd be a lot cooler if you did...
  21. Spacious ACP good to go for 4.2. All the usual color changes plus you can change the hardcoded ACP orange buttons to whatever you like. Additional dashboard buttons are back in business as well. Naturally, the current release in the Marketplace is still only for 4.1.x but we'll be set for 4.2 on release.
  22. Kitchen Sink 12 Released! Fixes Classifieds Application incompatibility Patches the above editable topic titles bug Adds forum descriptions to forum titles in forum index views Can now remove both multi-quote and quote buttons from post view. Yell at me if the edit first posts thing is still broken. Forum descriptions are created in the ACP with the full editor, not a plain text field. This KS feature is just pulling over whats there so expect the hottest of messes if you routinely use images and formatted text for your forum descriptions. This is only a convenience feature I've included for those of you who just use text exclusively for your forum descriptions and is not supported for rich-formatted text/image forum descriptions. As note in the updated KS Marketplace description, KS is still supported and under development but it's more or less in a holding pattern until we get the 4.2 alpha. As you can imagine there will be a lot of work to remove/change KS stuff when 4.2 hits so I'm investing my dev time as wisely as I can until then.
  23. @Rikki and whoever else: these are *much* better than 4.1 - well done!
  • Create New...