IPS Staff
  • Content count

  • Joined

  • Last visited

About Rikki

  • Rank
    IPS Brit
  • Birthday 08/17/1983

Contact Methods

IPS Marketplace

  • Resources Contributor
    Total file submissions: 3

Profile Information

  • Gender
  • Location
    Lynchburg, VA :o
  1. Theme Tip: Color coding tags

    We were recently asked if it's possible to color code tags - the customer in question used tags as statuses on topics, and so wanted 'resolved' to be green, and so on. Despite being a great idea, this isn't something that is currently possible 'out of the box' - although we'll add it to our internal feature idea list to follow up on later! But just because it isn't built in, that doesn't mean it isn't possible! In fact, with a little CSS, this is quite easy to achieve now. Writing a CSS selector We can do this by writing a CSS selector that matches the tag URL for the tag we want to style - a handy way to use CSS that can be applied to lots of other ideas within the suite! Lets say we have a tag called 'resolved', and we want to make it green. Add the following CSS to your custom.css file: .ipsTags a[href*="/tags/resolved/"] { background: SeaGreen; } html[dir="ltr"] .ipsTags a[href*="/tags/resolved/"]:before { border-color: transparent SeaGreen transparent transparent; } The first style is the main part of the tag element; the second matches the :before pseudo-selector which we use to make the 'point' of the tag. Another tag we'll style is called 'needs help'. In this case, there's spaces in the name, which are represented by the + symbol in the URL (since it's URL-encoded). We'll make it purple this time: .ipsTags a[href*="/tags/needs+help/"] { background: Purple; } html[dir="ltr"] .ipsTags a[href*="/tags/needs+help/"]:before { border-color: transparent Purple transparent transparent; } Supporting prefixes This little CSS snippet won't change prefixes, however - they'll still be shown in the default color (specified by your theme settings). If you want to change prefixes too, you need to adjust the CSS as follows - replace the previous CSS with this version: .ipsTags a[href*="/tags/needs+help/"], a.ipsTag_prefix[href*="?tags=needs+help"] { background: Purple; } html[dir="ltr"] .ipsTags a[href*="/tags/needs+help/"]:before, html[dir="ltr"] a.ipsTag_prefix[href*="?tags=needs+help"]:before { border-color: transparent Purple transparent transparent; } (Note: Notice the slightly different string we're matching in the href attribute; once you upgrade to 4.1.14, this won't be necessary - both selectors can use the same href format, e.g. /tags/needs+help/. Prior to 4.1.14, tags and prefixes used slightly different URL formats.) That's it - now everything looks correct! Topic View Forum View
  2. It's difficult because as far as I know, AMP pages don't support forms - and almost every page of our suite has a form.
  3. We like upgrades. We have the best upgrades.
  4. Also, it's orange.
  5. Hi Yes, as long as your license is active, you'll be able to download IPS4. You can run it in test environment to start with to develop your theme and so on, and then install in a live environment later. We have a responsive theme, meaning the same theme works great on mobile and desktop, so you can use all the same functionality - including uploading attachments
  6. You can use your own domain name with a Cloud plan - just submit a ticket to our Cloud team and they can help you with that You don't need to purchase a self-hosted license to do that, just make a small change to some settings with your domain registrar
  7. Yes you are correct - my apologies. That's even easier to do - it's a Pages block that we built, and we set the permissions so that it's only available to guests
  8. Sorry for the delay approving this Yes, you can certainly set a Pages page as your homepage - that's easy to do. In terms of developers, take a look at our providers page
  9. The vast majority of plugins (certainly the ones available from our Marketplace) don't require any files to be uploaded via FTP - they'll just provide an XML file that you upload into the AdminCP to install the plugin When designing IPS4 we intentionally made this a requirement, because not all environments allow disk writing, so FTP generally isn't required except in unusual circumstances. Yes, we have a built-in menu manager that lets you completely customize the menu navigation
  10. The loading spinners are used throughout the suite as an indication to users; it can't be removed I'm afraid. That said, with some custom CSS you could change how it looks, if you wish
  11. Please try logging out and back in again - that should sync your account. If you still have trouble, please submit a ticket via the client area so we can take a look at your account and make sure everything is up to date Thanks!
  12. That's a custom block we made using our Pages app, and using some HTML logic we display it only in the pre-sales forum
  13. Hello Our licenses aren't per-version, so when you have an active license you can download any version we make available. Right now, you can download 3.4.9 which is the latest (and last) release of the 3.x platform. However, I should caution that 3.x is now 'end of life' (EOL), meaning no support or updates are available for it, other than critical security updates. So, you are welcome to download and use it, but you would unfortunately be on your own if something didn't work right. Hope that helps
  14. We have a Similar Topics block that is based on tags rather than the topic title It looks like there's a few third-party plugins in our Marketplace too that might be closer to what you want: search results
  15. An enterprise customer recently asked us how to have a different feed block for each of their forums. Their goal was to have each forum show a 'popular topics' block containing topics only from that particular forum. Unfortunately this isn't possible using the standard block manager right now, since each view is treated as one configuration. That means that any blocks added to forum view will show for all forums. However, as usual in IPS4, some of the more advanced power under the hood does allow you to achieve the same goal - in this case, by using HTML Logic. This technique uses a similar idea to the one I outlined in the Dynamic-ish Forum Feeds blog in May. Creating conditional blocks The way we would implement this functionality is by creating a custom block that is simply a wrapper for other blocks. This wrapper block will contain HTML Logic that determines which feed block to show, based on some information about the current page. The first step would be to create standard feed blocks for each of the forums to which this should apply. In our example we're creating 'popular topics' blocks, but it could be anything you wish - the principle will remain the same. Another idea would be to create a 'Topics from other forums' block for each of your forums, whereby in the block configuration, you set it to include topics from all forums except the one in which it will be displayed - a good way of cross-promoting your topics. In order to include the blocks later, set the template key of each to be forum_x, where x is the ID of the forum in which you will display the block. Once we've created a block for each forum, the next step is to create our wrapper block, which should be a custom block set to use Manual HTML, with the following code: {{if request.app == 'forums' && request.module == 'forums'}} {{$id = \IPS\Request::i()->id;}} {block="forum_{$id}"} {{endif}} What's happening here is we're checking the app and module from the page URL are both 'forums', which indicates we're in forum view. We then use the {block} tag to insert the appropriate block based on the ID parameter from the URL. To use this block, simply save it, then using the Block Manager on the front-end, drag it into the desired location in your forum view. I hope this quick suggestion gives you some ideas for other ways to create blocks that show contextually depending on what the user is viewing. If you have ideas for interesting ways to use this technique, share them in the comments!