Jump to content

Community

rllmukforum

+Clients
  • Content Count

    117
  • Joined

  • Last visited

About rllmukforum

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Our forum has been running Invision since 2003, and users are very much stuck in the classical folder paradigm. Attempts to switch or supplement this with a metadata approach (ie, tags) gained little traction. It's not alike an illness, it's being used to a certain way of doing things. And on a personal level, I'm quite happy for forums in general to eschew the need to mimic social media and operate as they did. To each his own, right? Thanks for the marketplace suggestion, I'll look in to that, @day_
  2. Apologies if already suggested, I searched and could not find it specifically. Request: Change all topic title links such that they include the getNewComment parameter. This is the default behavior while browsing from the main site index, but not while in a forum/sub forum. Justification: When the Forum app had separate desktop and mobile themes, the mobile theme had this very functionality. Rather than requiring users to click the little dot/star alongside a thread, you could click the thread title to see the first unread reply. I no longer run analytics, but even as of a few years ago, half of my users are on mobile devices. We manually edit themes to include getNewComment, but I would prefer to perform as little customization as possible. If, for some reason, a user wants to return to the first page, the forum already includes a link to page 1 under the topic title. I believe this would, technically, allow you to remove the dot/star, which cleans up the UI slightly. It feels like a good quality of life improvement for mobile use, much like the recent new features added in 4.3.
  3. I actually appreciate it when Twitter sends me an email advising a specific report led to action taken. We have developed a similar expectation from our users, but it's also born of moderation being a black box in general. Only moderators see if a post led to a warn, only mods see if a post is reported (leading to duplicate reports, and so on. Maybe it's a question of trust in the system. Applying the 80/20 rule, I can see how this is likely an outlier case for many communities, but moderators on our forum have requested it. I think, at the very least, the post in question indicating that action was taken is useful, even if it's not my original request here. It sets a clear precedent for what isn't acceptable, per the forum's rules.
  4. When moderators take action on a report, they are able to leave a note to moderators and the person on the receiving end of the action. The person who made the report does not receive anything, requiring moderators to start a PM conversation. It would allow for a more efficient process, and better user experience, if the reporter could be informed at the time a report is closed out (i.e., no action), or if specific action was taken (perhaps a third text box on the warn screen).
  5. Given the volume of reports we handle, we would also benefit greatly from this feature. Sometimes it's very difficult to discern the intent of the report. I would very much rather deal with "lkjherhkjewhkjhkjsfdg" as the reason, than no reason at all. The former could be handled as potential time wasting. We attempted to edit our theme to enforce this as a required field, but have not been successful thus far.
  6. I'm glad this topic has resurfaced, I asked a few weeks back to no response. I'd be surprised if Invision has nothing to do here, given Given we all have a vested interest in adhering to laws and protecting our users' rights, I'd really like to participate with others here in trying to establish the remit of forum owners/admin, so we can provide clear expectations of their rights, but also to feed suggestions to Invision to enable us to enforce them.
  7. Thank you, I appreciate the technical analysis. I will trust that the above means some plugins require a specific version for IPS 4.2. I think the issue is language; something "compatible" with 4.2 literally doesn't preclude compatibility with prior versions. Also, as I have stated, other plugins we have used, for older versions of IPS, have not require separate versions. If the plugin had stated "4.2 required", I would have initially downloaded the previous version, 1.1.6. Thanks for taking the time to explain why the change was necessary, it's not always clear why Invision mess with templates in this manner.
  8. No sir, I do not. I am literally offering only my experience of having installed other IPS plugins. By pure chance, these other plugins have needed tweaks to adapt to changes Invision made to their code. In these specific instances, the plugins then worked with the current and prior versions of IPS. I have no knowledge of this plugin nor any of the underlying programming knowledge in IPS framework. I'm simply a paying customer who is 1) having difficulty and 2) seeking help by asking questions. I am disappointed in the outcome of our interaction. Thank you for your time.
  9. I've seen numerous plugins that need to be tweaked for new versions of IPS, due to changes Invision have made, but retain compatibility with older versions Not trying to be difficult, this is just my experience of plugins and so I did not understand the requirement for this one.
  10. Yeah, running the support tool fixed the post issue. I'll try reinstalling the plugin later to see if it reoccurs. To me, "compatibility" means "also works with", not "is required". Even just a minor heads up in the notes to use the previous version while not on the 4.2 beta would probably save a post from people like me.
  11. Well, this is interesting. Approximately 25 minutes after installing 1.1.6, some members of our forum, myself included, cannot post. I have no way of asking who can and cannot. I've since removed the plugin, but when I try to reply the CKeditor fails to load (I click in the reply window by the placeholder text remains). Also, and curiously, the theme selector dropdown no longer works. Again, anything obvious I might try? I've restarted nginx and php-fpm on the off chance it was that, but honestly, the forum has been running absolutely smoothly for months. edit - running the support tool in the ACP resolved it, although I have yet to reinstall the plugin. Very odd.
  12. That did it. I installed version 1.1.6 and it worked immediately. Could I suggest a change, please? This is the first mod I've seen (admittedly, we haven't used many) where it's not backwards compatible with earlier versions of IPS. Given 4.1.19.4 is the current stable production version, and 4.2 not yet released, I would update the product page for this plugin to make it explicit that the latest version (1.2) only works on 4.2, not that it's "compatible" with 4.2. FYI, our only other plugin is Tapatalk. Thanks again for your help.
  13. Purchased and installed on 4.1.19.4, however the "change author" link does not appear at the bottom of a post. I have enabled the plugin, enabled various groups (including the one I am in) and even toggled the "increment post count", not that I thought it would have any bearing on it. Any sense of where I should begin troubleshooting, please?
  14. https://en.wikipedia.org/wiki/General_Data_Protection_Regulation I glanced through the EU cookie law thread to ascertain Invision's general approach to local regulations, but I'm wondering if the product management folks have one eye to this new data protection law, which goes into automatic effect in 2018. I haven't delved properly into the implications for our community, but a cursory reading suggests additional functionality may be required, such as data portability. I know some US sites went to the trouble of accommodating the cookie law, presumably to have a single code base to support, but this obviously seems a little bit more in-depth and so would appreciate Invision's thoughts.
  15. Excellent, thanks. I needed to enable the "can view edit log" permission for the Moderators group.
×
×
  • Create New...