Jump to content
Announcing Achievements! ×

Community

rgf100

+Clients
  • Posts

    612
  • Joined

  • Last visited

 Content Type 

Profiles

Downloads

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Store

Everything posted by rgf100

  1. That's a good idea. I have plenty of legacy blocks hanging around which I'm *fairly* sure aren't used anywhere, but don't want to delete just in case...
  2. I see what you're saying, and it might not always be ideal - but if they're just queued up for approval rather than published, there's scope for editing. And it's also about what people expect - if you specifically market it as 'here's our best posts, don't forget to check out the full discussion', for example, people know what they're getting. At least with my site, I think if I could get the most popular posts in front of people's noses, it'd be valuable. The occasional false positive when everyone upvotes a two word inside joke won't do much harm, and can be removed later or caught during an approval process. There's scope for bad actors to, eg, spam reputation to get their posts onto the social media feeds, but again, it's not necessarily the end of the world. No need to let the perfect be the enemy of the "really useful, and we could have had it years ago."
  3. While people are paying attention, can I point you towards this seminal 2017 post suggesting the use of reputation information to automate / semi-automate social media promotion. Take either the X top posts, or all posts with X+ reputation, and push those to social media, or load them up for promotion to await an admin edit / approval / rejection. In one fell swoop, you've automated getting the best of your site out into the wild.
  4. Excellent. I'm just going to keep going and we'll see how fast you can keep up. Next point: "Under first post" is not the ideal position, for the topic summary or ads, or anything. Regular member traffic is much more likely to be heading for a #comment-xxxx anchor tag and will skip right past the first post. If I remember correctly anything after the # in a url isn't available to the server, but if you could work round that and have that content appear *where the user is actually looking* it's a lot more likely to be seen.
  5. I like the new topic summary boxes, but have a few thoughts... "TOP POSTERS IN THIS TOPIC" - it's more likely people will want to read the posts, than the posters' profiles. If there's any way to bring together the posts someone has made (perhaps by minimising other posts?) that would be good, otherwise I'd have that link to the person's first / highest rated post in that topic. The "POPULAR POSTS" bit - I'm not sure how intuitive clicking on the date is. I'd make the post text snippet clickable (and perhaps that whole div, with the userphoto / name also going to the post, although I realise this would be inconsistent with behaviour elsewhere. POSTED IMAGES - I like this, but there's no way to get from the images to the associated post. I think there should be.
  6. The 'popular posts' bit in the new topic summaries are a step in the right direction. But there's so much more that could be done.
  7. I'm flogging a dead horse here, but... I still can't filter a post block by number of reactions.
  8. I'm keen to see Zapier available, but I'd imagine it's a pricing thing, as it isn't free at anything but the most basic level. This also makes me wary of using it - if IPB and Zapier can't agree on pricing at some point in the future, what happens to your automation?
  9. I actually came looking for it on a per-forum basis - I'd like to keep controversial or contentious topics in a separate forum, where users can only make one or two posts per day. In case you don't know, there is a per-usergroup daily post limit - not quite a flood control, as you could use up your quota all in a few minutes. But it'd help a bit, I'd imagine.
  10. Just to say, I'd *love* to see this based not on days, but on posts.
  11. As far as the software goes, this is one of my main concerns currently. Regardless of how genuinely important it is, the fact is that we're mostly getting traffic from Google, Google judges sites by speed, and when I go into Google's Webmaster Tools, I see thousands of pages it regards as too slow.
  12. I like this, but having it appear under the first post when not in the sidebar seems a mistake. Fine for a new topic, but once you're past the first page, it's going to get overlooked pretty quickly. I'd say bottom of page, or under the 'target' post - ie, the post that a 'read new' link takes you to. Put it where people will see it.
  13. I'd like to have this (and other stats) compiled into weekly emailed reports.
  14. The reactions info is woefully underused in general. I've been banging on about this for some time.
  15. Looks like rebuilding the search index fixed it, for anyone having a similar issue.
  16. I am, and I'll try that now... Ok, that's reset it to the correct value. Will see if it stays that way as indexing progresses...
  17. I'm trying to get an approval queue count on the userbar. Part of this involves the following code: $approvalQueueCount = \IPS\Content\Search\Query::init()->setHiddenFilter( \IPS\Content\Search\Query::HIDDEN_UNAPPROVED )->count(); As I understand it, this should return the number of as-yet unapproved content items and comments. For some reason which I cannot make sense of, this consistently returns a number 2 higher than what's actually in the queue. I went hunting for phantom unapproved content. It's not status updates or replies. It's not blogs, or Pages databases, or gallery, or club, or anything else I can think of. And anyway, if it was any of those things, it should be appearing in the queue. Where's the extra 2 coming from? What code (I'm very much at the edge of my capabilities here) do I need to see what the above code is 'finding'.
  18. When upgrading, there's a generic "We're sorry, this web site is unavailable while an update is in progress." message, which is fine. But if, during the update process, we could choose something: "Quick update, should be back by 10pm EST." "Big update in progress, could take a couple of hours." "Updating the site, don't forget to check out our other site othersite.com" That'd be cool.
  19. I would... create a custom block with the settings you want. Content tab > Use as base for custom widget > Then you need to look at <div class='ipsType_break ipsContained'><a href="{$comment->url()}" title='{lang="view_this_topic" sprintf="$comment->item()->title"}' class='ipsType_medium ipsTruncate ipsTruncate_line'>{$comment->item()->title}</a></div> and make some changes. Refer to the bit just below on the post text for one way... <div class='ipsType_medium ipsType_textBlock ipsType_richText ipsType_break ipsContained ipsSpacer_top ipsSpacer_half' data-ipsTruncate data-ipsTruncate-type='remove' data-ipsTruncate-size='{{if $orientation == 'vertical'}}6 lines{{else}}2 lines{{endif}}' data-ipsTruncate-watch='false'>
  20. I'm not sure we'll get anything different (except perhaps clearer language) without a significant reworking of how notifications work.
  21. Sounds like it's not so much 'unintended behaviour' as 'the only way to do things right now', but they're taking another look.
  22. It could be an oddity in my database, although... if both methods are the same... Let me know if there's anything I can do to help.
  23. Caution! The 'stop emails' options for members who aren't logged-in actually removes ALL notifications, including on-site. This caught me by surprise and I now have hundreds of topics I want on-site notifications for, which have been set to 'no notifications'. I've got a ticket in to see if this is intended behaviour.
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy