Runar

Already reported: Tips: Try the search function. It actually works! 😉

This sounds interesting. Would you be able/willing to post a screenshot of how posts look with your modifications?

Any specific reason why you recommend Cloudfront over Cloudflare?

This is the support topic for the plugin Customize New Member Badge.

The plugin is available!

As mentioned earlier in the topic, there is a bug when sending private messages to members after X hours. If you set the message to send immediately after signup, nothing bad happens. If you set any delay, it will send the message to everyone. This is a bug, not a missing option. I just hope @Michael.J responds soon, as this can be quite serious.

I have created a simple (and free) plugin to change the icon, change how long a member is considered new, or disable the badge completely. Hopefully the plugin will be approved and available shortly.

What’s new in version 2.0.0: The plugin is now an application! This means a new location in the ACP (under the "Community" section), but apart from that everything should work as before. When updating, the application will automatically move all of your markers and marked topics to the new database so you won't loose anything. After the update is complete, the old plugin will be uninstalled and removed. Another change is the price. The new price — which only affects new purchases — is $15 plus a small renewal fee of $7.50/6 months. This will ensure the application is kept up to date with new versions of Invision Community, and give me room to add new features when suggested by you, my customers. The total price for one year will be around $0.08 per day, which I think is acceptable. Now, let's take a closer look at the changelog: New features Users can now choose between multiple markers when marking a topic, if multiple markers are available. Notifications will be sent to topic authors when their topics are marked and/or unmarked by anyone else. Improvements Added options to customize marker badge background color and text color. Added option to customize marker badge position (before or after topic title). Added option to show marker text in topic page titles. Added live preview of marker badge style when creating and editing markers in the ACP. Added option to prevent members from unmarking topics. Fixes Fixed marker badges displaying incorrectly (in some cases not displaying at all) in "Question" forums. Fixed a few small annoyances in the markers sections of the ACP. Improved the handling of marked topics in the database.

Thank you! Any comment on the SSL issue?

I've been using MariaDB for years, and I've never had any issues, and I don't think I had to make any adjustments when installing Invision Community. Just to be safe, I advice you to take a closer look at the official MariaDB vs. MySQL page from MariaDB, which includes an incompatibilities list.

Any comment, @Matt or @Lindy? Surely this can't be an issue limited to only a few unlucky visitors. SSL Labs marked the certificate as invalid from four different servers, and other SSL testing tools did the same. I understand that you might not be able to reproduce the security warnings, but there are clearly some issues with the certificate or your load balancing setup.

If I accept the security risk (in Firefox) and continue, I no longer see the warning. Maybe everyone at IPS has already accepted the certificate? Anyways, the certificate on community.invisionpower.com is not valid. See the test results from SSL Labs: Edit: The actual test results:

I don't know if this is the right place to report bugs with this community, but here goes. Links in the descriptions for the following forums point to an old domain (community.invisionpower.com), resulting in security warnings and in one case a 404 error: https://invisioncommunity.com/forums/forum/320-client-lounge/ https://invisioncommunity.com/forums/forum/442-contributor-chat/ The links in questions are: http://community.invisionpower.com/forum/307-ips-customer-services/ http://community.invisionpower.com/forum/451-community-resources/ (dead) http://community.invisionpower.com/contributors/

Creating a test forum and copying the production database is not that simple when you've got tens of millions of rows in several of the database tables. Not to mention the test environment should be as close to the production environment as possible, which might require additional expensive hardware. All this requires someone to do the work, and in many cases it ends up being a question about who pays for what (and what is pushed to the back of the queue due to money going to testing). In an optimal scenario testing would be the norm and money wouldn't be an issue, but unfortunately this is not always the case. I don't know where to draw the line myself. I understand your points of view and I agree with most of them, so I might be playing the devil's advocate here. PHP and other server software can be patched without updating to newer full releases. In some cases there are patches released for Invision Community as well, and the most serious security issues would be disclosed so one could – though not recommended – manually fix the security issues without updating. With that being said, the best and simplest thing is to update. I honestly don't think most members of online communities care. If you know what Invision Community is, you'll quickly recognize communities running on older versions, at least on versions 4.4 and earlier. The differences in functionality and design are quite significant, even on communities using custom themes. All members care about is performance and functionality, and that nothing breaks when something is updated. I also don't think someone is trying to hide the fact that they're not using the most recent version. I would just like to add that I personally try to update (all software) as soon as possible after a new release. What I'm trying to say here is that I understand why some don't update immediately, and that I get the most common reasons for not doing so. I don't disagree with you that the banner is not the main issue. What I meant with my original comment was that Rhett's wording could have been better, as the causes of many not updating immediately is known, but not necessarily quickly resolved.

Well, the option is to edit the theme. But yes, maybe it should be an option somewhere, as not everyone is comfortable manually editing the theme.

The relevant code is on lines 45–47 in the theme file forums > front > topics > postContainer: {{elseif $comment->author()->joinedRecently()}} <span class="cAuthorPane_badge cAuthorPane_badge--new" data-ipsTooltip title="{lang="member_is_new_badge" sprintf="$comment->author()->name"}"></span> {{endif}} I've kept the badge, but changed it to something a bit more positive: /* Change the icon for new members */ .cAuthorPane_badge--new::before { content: "\f25b"; } Which results in this:

You're correct, and personally I'd like to see the community I referred to updated more frequently. However, updating during the beta period is not really an option, as things change quite often and things can and will break. Another point is that some updates require you to make changes on the server side. For instance, 4.5 recommends PHP version 7.4 and future versions of Invision Community will drop support for older versions of PHP. Yes, I know PHP 7.2 is three years old and that you should keep your servers up to date as well, but realistically that's not always possible. Finally — and this is something I don't think anyone can argue against — some people simply don't want to update. Apple doesn't force their users to update their iPhones and iPads to the latest version of iOS. Sure, they recommend it and more and more apps will stop working on older versions of iOS, but you don't get a banner taking up half the screen everywhere if you're on an older version.

Did you ever get this done, or are you still looking for a solution?

I sent you a PM now! 🙂

As others have already mentioned, it's not always that simple. I help manage one of the larger communities, with over 25 million posts running on multiple servers, and upgrading to a new version involves long periods of testing. When we actually do upgrade, it's a complicated process to prevent messing something up for our thousands of members. I completely understand that you want everyone to be using the most recent version, but there are several valid reasons for not upgrading immediately after a new release.

I'd just like to add that I'm currently working on a huge update for 4.5, hopefully to be released later this weekend or early next week.

Thank you for the explanation! I assume you're not in the EU, as sending a copy of the database to a third-party would be a rather big deal for me. With that being said, I understand your decision.

I'm interested in hearing more about this. Is this something you can and want to talk about?

For everyone else, I'm currently working on a huge update with support for 4.5. The new version will be an application instead of a plugin, as this makes it far easier to provide new functionality. In addition to official support for 4.5, I'm working on the following new features: Choose between multiple markers when marking a topic. Set custom background color and text color on the marker badges. Choose marker badge position (before or after topic title). Send notifications to topic starters when their topics are marked and/or unmarked. Support for "Questions" forums. I hope to release the new version later this week or early next week. Suggestions for more features are always welcome!