• Content count

  • Joined

  • Last visited


About Meddysong

  • Rank
    Community Regular
  • Birthday 12/16/1978

Profile Information

  • Gender

Recent Profile Visitors

3,103 profile views
  1. What'd be super fun (/nerdy) is to have somebody filming the goings-on in the war-room at the time the trigger is pulled!
  2. That does look good, mate. Really, really good. I can't help but ask one particular question, though, because it's the sort of thing that's going to be on my mind all day. Why is it that your category list in your articles database is in alphabetical order, except for Police State and Government & Politics being transposed? Is it just an oversight, a bug, or an unfortunate fluke? Edit: Oh, there's a small bug. On your about page you're forcing the icon to display at 200px. But on a wide desktop (mine is 1920px) the container it's in is 203.67 and your icon has padding too, so it's being forced outside its container:
  3. There's a curious problem which occurs when using the white background on markers. See how the icon is further to the left here? It doesn't apply to the other backgrounds: But with white: Unusual, huh?
  4. Because if there were only three columns in the grid, each cell would be wider to eat up the space and look fairly ugly compared to the narrower ones when you use four columns.
  5. And I think the visual issues (that the opacity is different, the container is positioned higher, and the arrow located centrally rather than on the left) are something that needs fixing within the custom theme, since the screenshot shows that that's nothing to do with IPS's default.
  6. If it does that on the default theme, then that's a bug. You'd expect all of the menu items to behave the same on hover. It's worth making a support request for this so that IPS can fix it in a future release.
  7. It's a bit complicated to explain The current prices are the ones which are struck through. However, since 4.x has been introduced, we've been paying the 3.x prices. So we currently pay the old prices, if that makes sense. But from December 2nd, we'll be paying the proper 4.x prices (the struckthrough ones) rather than the 3.x ones.
  8. They're marked on the page:
  9. And this is a problem for regular fields, too. OK, I can add language strings within custom formatting so that it displays in my second language, but the filters still show in English.
  10. Not in the case of this one, though, because it's not only a field (which can be controlled with permissions) but also the content for the record. So this line in the record template <section class="ipsType_richText ipsType_normal" data-controller='core.front.core.lightboxedImages'>{$record->_content|raw}</section> calls it irrespective of permissions. And commenting it out will remove it
  11. Bah, great minds thinking alike. It turned out I'd already had the same idea as you, Ralf! What confused me is that the content still appears in the display template, so I was still seeing "test" after submission. I'll dip into the template in a bit and see what I need to remove from it.
  12. Hmm ... That sounds like a good work-around. So ... it'll be a mandatory field but with a default value, and nobody but me will be able to see it. It looks like I've had a similar thought to you at some point because I can see that when I upload just a title the word "test" appears in the body. So all I need to do is keep what I've done but change permissions, hey? Think I'll have another look at this later
  13. This has caught me out, too. One of my databases has a category which is for requesting a word to add to a pronunciation database. Just the title would be enough, rather than asking people to type the same thing into the title and the content. It doesn't help either that for the other categories in the database, the content will be uploaded sound files (the pronunciations). I can't make people attach a sound file in the "requests" category, and I can't expect them to add text content for no reason in the "pronunciation recordings" categories either. So it seems I'm going to have to split across two separate databases, even though these are related uses.