Yamamura

Hi,
Really like this plugin but could you maybe look at the suggestion below.

Maybe able to change the order like this aka switch this:

or even better make it "one line" aka smaller/in one column like this: (only for the "WIDE" widget)

And option to also display their names somehow would be great 😮
Kind Regards

Sorry, but it’s simply a failure to understand responsive web design. You can’t take one screenshot and move things around to “solve” something (e.g filling white-space), because that “solution” would likely break the display in other situations you haven’t considered. For example: Users can have ANY screen width, from a few hundreds pixels to a couple of thousand. The layout needs to work in any of them at the same time! And the content is dynamic too. There are 5 people online in this screenshot. But what if it’s 50? There is column that gets activated when there are invisible users, but just because it isn’t in the screenshot, you don’t consider it. But I do have considered all these parameters and that’s why it looks the way it does. 

Happy Hump Day, fam! 
I'm bringing this very special Hump Day post from our headquarters in Lynchburg, Virginia.
@Ryan Ashbrook, @Matt Finger, @Marshall Slemp and myself flew in from all over the U.S. to join forces with @Charles, @Olivia Clark and @Rikki to A.) meet in person and B.) dream up some exciting new projects!
Spoiler alert: we have some pretty exciting things in the works! Olivia is helping us channel our creative energies into effective workflows. Seeee?
 

Speaking of projects, have you had a chance to check out our website refresh? I'd love to point you in the right direction 😏  namely our Innovate section. It's beautiful 🥲 . Curious, what are your thoughts? 
Content Discovery Visitor Engagement Community Management Integration Achievements Mobile Customize
Next up is 4.6.7 Beta 1... it's available now! It includes our new Activity Streams subscription feature, extended Closed Clubs functionality and Stock Replies!
 
 
And if that wasn't enough Invision Community magic, check out a list of updates/fixes we've knocked out since we last spoke:
- Fixed an issue where converted mentions may contain a static URL (breaking them if you change your domain).
- Fixed an error that could occur if the Converter tried to delete a content link.
- Fixed an issue with tag statistics immediately after a conversion.
- Fixed a niche issue where an error could occur if a PayPal Subscription notification arrives after the Subscription is cancelled.
- Fixed an issue where it wasn't possible to edit a subscription expiry date.
- Fixed an issue that could cause a slow query to run when sending email if a large number of emails have previously failed.
- Fixed an issue with the Frontend Theme Editor occurring with PHP8.  
- Added Stream Subscriptions.
- Fixed the broken "Buy" link inside file embeds.
- Fixed an issue with some topics not being hidden (but their posts were) after converting from vB5.
- Fixed a potential issue adding tags to content when using PHP 8.
- Added the ability to quickly navigate between Node permissions and Group permissions in the AdminCP
- Made Profile Completion steps non-copyable.
- Fixed members REST endpoint responsible to award a badge. 
 
Alright folks, that does it for now. If you have any comments, questions or concerns, drop us a line in the comments. We're here for you!! 

Hello if anyone could help that would be great.  I am wondering if for certain post or forums if I can remove the Posted date.  Some of my content is course material and although it's evergreen, the date makes it feel like it's out of date content even though it doesn't change.
I did some searching through the forums but didn't find any question like this.
Thanks in advance.

Finally someone gets it. 

Sorry, but "support" from the community on forums is inherent in free software. When a client pays money, he wants to have a private communication with the support (there can be many reasons for this).

We are working on native translation in a future update 🙂

I see that the debate about a new kind of support is due to differing understandings of this meaning. I agree that "asking questions" is best done on the forum, rather than contacting support in person. BUT I and many others here are talking about a different type of support requests. I contact support when problems arise on the forum (mainly after an update) or I see some bugs, I attach screenshots and screen recordings (which I post to my YouTube account), I provide developers with access to my forum so that they can go in, check and confirm problems. I don’t want to write about this on a public forum, I don’t need a "community support" for these problems (because these problems can ONLY be solved by developers), and maybe I don’t want to show a link to my forum or YouTube account. So yes, I want to be able to address such issues directly to support.

I see that the debate about a new kind of support is due to differing understandings of this meaning. I agree that "asking questions" is best done on the forum, rather than contacting support in person. BUT I and many others here are talking about a different type of support requests. I contact support when problems arise on the forum (mainly after an update) or I see some bugs, I attach screenshots and screen recordings (which I post to my YouTube account), I provide developers with access to my forum so that they can go in, check and confirm problems. I don’t want to write about this on a public forum, I don’t need a "community support" for these problems (because these problems can ONLY be solved by developers), and maybe I don’t want to show a link to my forum or YouTube account. So yes, I want to be able to address such issues directly to support.

I see that the debate about a new kind of support is due to differing understandings of this meaning. I agree that "asking questions" is best done on the forum, rather than contacting support in person. BUT I and many others here are talking about a different type of support requests. I contact support when problems arise on the forum (mainly after an update) or I see some bugs, I attach screenshots and screen recordings (which I post to my YouTube account), I provide developers with access to my forum so that they can go in, check and confirm problems. I don’t want to write about this on a public forum, I don’t need a "community support" for these problems (because these problems can ONLY be solved by developers), and maybe I don’t want to show a link to my forum or YouTube account. So yes, I want to be able to address such issues directly to support.

Matt, let me clarify as I can see how this was, and could be, misinterpreted.
I agree that a peer-to-peer forum would, could, and will be helpful. I disagree that paid license product support should include peer-to-peer assistance. Note, tone does not often convey in text. But understand I am not the least bit angry. Disappointed, but not angry. And I hope the following is received in the manner I intended. My own personal thoughts.
In your example with the barista, my responsibility to a barista (or any company) is to be cordial and pay for my order, product, goods or service. Their responsibility is to be cordial and deliver it as ordered. And if my order is not correct, they support it by correcting it. They don't expect me to to turn to another customer on a laptop and ask for assistance as that would be unreasonable. Certainly, the price I pay for their coffee doesn't come with the expectation of creating/contributing to a customer handbook.
I understand entirely what you are trying to do, but I feel it is personally really misguided. To illustrate, already it has been pointed out that this new plan effectively segregates, and places a support value, between one type of customer and another (self-hosted versus cloud -- which admittedly I appreciate and benefit from).
Further, customers incur higher fees that not only eliminates proper, direct IPB ticket support, but now comes with the added expectation of crowdsourcing a live knowledgebase just to get any level of support.
Respectfully, if we're being honest, I think this entire concept is quite arrogant.
Truth be told, I think a much better use of hiring all of those new tech support staff would be to provide better, more efficient ticket service for all paying customers, regardless of how trivial the request may be. And then IPB themselves should extrapolate and collate non-identifying information to create an official Self-Help Guide. And then this would be used as a live search in people's admin areas when they click support and type their request out. And still have the ability to file a ticket if still needed.
But my assumption, and fear, is that these "triage" personnel will be more like junior entry level techs who will do little more than add one extra step in the process before finally getting actual support.
So, to summarize the above misunderstanding, it it simply that I expect support from ONLY the company with whom I have I have a business relationship. Nothing more, nothing less.

That's putting words in my mouth and cherrypicking at its finest Matt, and is beneath you to do so.
I am your customer. I pay for your product. I have a business relationship with you, no one else. If you want to extrapolate non-identifying information and use it as part of your knowledgebase, then fine.
I have an expectation of support from IPB, and ONLY IPB, to support the product I am paying for, and to do so properly. No one else.
I think an expectation of proper ticket support is hardly outrageous.

I've already canceled the self-hosted license because of the open forum support policy. The ONLY reason I have not canceled my Cloud license is proper ticket support is continuing.
For me it's basic principle. I pay for a product. I expect proper, private support for that product from the company with whom I have a business relationship. No one else. It is not my responsibility to create a living knowledge base, nor contribute to it. I have no interest in being part of a "community". I am a customer. That's it. That's the end of the relationship I want, and need, with IPB.
It's crazy that I've posted more times in this thread than I have in 17 years.
Suffice it to say, should ticket support end with Cloud, so will my license for it.

Sorry, but I find that very hard to believe. Then again, most of what has been said by IPS staff in this thread is pretty unrealistic. Moral of the story is, this is a tactical push to evolve completely into a SaaS service. Might even save you some time and money just to refund all of the self license purchases and get rid of it entirely.
I'm pretty disappointed you haven't realized this was a huge mistake, and haven't taken steps to accommodate anyone you've blatantly hurt by these, I'll say it, malicious changes.
It's clear this was not a "communication" issue, rather a stunt to prevent anyone from renewing prior to the price hike. It's also clear the changes to self hosting prices had nothing to do with betterment of the software, rather an excuse to push people to cloud hosting. It's also clear the reason for yearly renewals was to prevent customers from selectively renewing only when they actually need to. Not because "it would confuse customers."
Yeah, confuse customers with the same model you've had for the past 10 years... We aren't that gullible. I'll stick around, but I'm not going to renew until there's drastic changes, and I'll avoid using the marketplace from now on and work directly with 3rd party developers to make sure they're being taken care of.
I can't express enough how disappointed I am.

I've slept on the email and on the first 14pages of this topic.  WOW!
12 month billing industry standard? Almost all of the services I use are per hour, per month, most offer an annual discount. Those that only have annual, TBH, they have something to fear to lock you in. Even microsoft do monthly 😉  who/what is a standard?  Be better by differentiating and offering your customers what they need.
Silver linings: I'm assuming search will be getting a really good overhaul, elastic 7? If we're to search for issues first. TBH I still just use `site:domain.tld` in google here and on my own sites. 
I can actually stand the price increases. But I'm not impressed at all, at how it's been done. Trust was a word used before, I'll reiterate that and add reputation. Now I don't want to renew on the principal of it, and to support those who had this foisted upon them. 
I understand the support changes too. As a developer of 25+years and engineering manager for many, I see my peers on support, their productivity is far lower. £ for £ I get more from my non-support folk. However, they tear through bugs, keep paying customers happy with super quick response times & prompt fixes. Sure we have the odd customer who is a 'burden' but we see it, if we can make it work for them, then 80% of the others won't bother us. Now if I could offload support to customers... win. #fail If multiple similar questions asked, add it to a knowledgebase, dev or customer led, #win.

Could also get rid of the annoying config/server queries by bumping the price up to a bearable, but mostly prohibitive figure? ...win. #fail Ultimately at $1250, that's an hour work a month I'd expect in return. Or one serious forum offline help me get it back. If I was raising that level of support queries, IPS isn't the best. I'd pay $100 per serious issue escalation or guaranteed resolution, not a sort it yourself as your not cloud hosted...

I didn't have premium support before, didn't feel I needed it, support was great; ok, mostly ok, a little difficult as self hosted, no sftp, 2fa etc for the dozen tickets or so over a decade. Had one bad upgrade, 4.5 to 4.6.6 yesterday ironically.
Community support no sla? That in essence, and at worst is, no support, a suggestion that breaks more than it fixes, an escalation to a ticket at some point/trigger?, or premium support! Well let's try it for a quarter, nowt to lose now.
I'd save a big chunk of my monthly going to your cloud offering, except I'd rather eat my own notebook. I choose to self host, I enjoy it and I can optimise it, tune it, debug it. Ican upgrade when it's not a buggy .0/.1 release.  I pay for an sla with service providers and pay for more with many companies whom I trust... who are open, transparent and fair. Who reward their evangelists and support the 3rd party community. 
not bad news... just wow.

Hello!
Sorry for my translation, I use a translator. 🤗 But I can't help but speak out about the price increase.
I tried to use licensed software and therefore acquired a license, and all these years I paid for support, receiving updates, often not seeing any sense in them both for the community and for myself. My community is not a commercial one, we are a fishing community.
The news with an increase in prices hit us, the amount of $ 250 is not acceptable for us, given the number of support requests for the entire period of using the IPS.
But in the current circumstances, we most likely will not extend support, but perhaps we will start looking for an alternative engine. Or we will work as much as possible on the version that will be the last paid subscription for us.
Thanks to the developers for many years of work, but unfortunately, I will not be able to pay tribute to my habits in the future.

Sorry, but "support" from the community on forums is inherent in free software. When a client pays money, he wants to have a private communication with the support (there can be many reasons for this).

My take so far reading through all of this...
Don't lose your marketplace developers.  They're a key to your success and help build your suite of products.  It's a win for customers in getting more robust features, it's a win for developers in earning revenue, it's a win for your company/product suite in both revenue and features that can be adopted.  It's a tough balance to be had, but I can certainly see a credit system whereas developers are credited back license costs once they contribute X (whatever X is deemed to be).  This incentivizes them, and should be coupled to a quality metric to ensure they aren't just throwing something out on marketplace to get the credit but that their offering provides verifiable value to the consumers. There is a huge gap in affordability between hobby sites and business sites.  To have the same pricing model apply to both only serves to make it unaffordable for hobby sites entirely.  If IPS has an interest in being the forefront of online forums/CMS and gain correlating exposure, this approach is leaving hobby sites out of the equation and that is a net loss for IPS in gaining visibility which translates to future sales/adoption by new hobby/business sites (penny wise, dollar foolish).  Not to mention the immediate loss and future visibility from hobby sites that migrate to another solution and popularize it will negatively impact future IPS sales/adoption.  IPS needs to find a way to balance the affordability based on the target customer, but not at a reduction of features (as that inhibits marketplace incentive and adoption if that feature set can be found elsewhere) Support.  You need to address the turnaround SLA for support and customers need an appropriate path to solving site critical issues within a reasonable SLA without it costing $1250 or waiting 3+ days for a resolution to take effect (note, not 3 days to respond, but 3 days to resolve it and have the site properly operational). Unquestionably, the PR around this specific case needs (and is getting) review.  Moving forward IPS needs to do a far better job in broadcasting the roadmap of these changes and provide their customers the opportunity to assess them, which avoids customers being cornered ala "big bang" like we've seen here. I can see MANY are quite upset by these changes for a variety of reasons, but I also see opportunities for IPS to revise their approach for their benefit and for their customers' benefit.  It's a complex situation, and there are fair arguments on both sides, however there is a big void in the balance in the current solution and it WILL unquestionably adversely affect BOTH IPS and its customers.
- "cannot see the forest for the trees"

As a long time user of approaching 20 years who has been a customer since the Ikonboard days and has a first recorded invoice here in 2005 for "Purchase: Invision Power Board Perpetual License".
For what it is worth, here is my feedback on the e-mail I received about the price hike and reduction in support levels.
Six years ago you contacted me as a "lifetime" member to tell me that the lifetime agreement I signed up for, which helped set the the financial foundation of these forums, was to be replaced with an annual fee. It was nice to get a little credit on account by way of apology, however, I bought a lifetime licence and it should have been for lifetime. Offering a lifetime licence is a marketing incentive, and not something that should be reneged on further down the line once a company has reaped the benefits of the marketing drive. Telling customers its one payment for lifetime access, then changing the goal posts to an annual fee is not the type of thing that reflects well.  
Onto the new e-mail....
Forums: was $50, now $80 (increase of $2.50/month) The marketing team really earned their wage this campaign as $2.50 doesn't sound like much, however this represents a 60% price hike from $50 to $80.
A 60% price hike needs to be backed up with some serious upsides.... however...
For most customers, support is simply “how do I do this?” and these questions tend to be quite similar. Rarely, support questions are “this went wrong” Not my experience. My support experience is basically the same every year - my forums go offline with errors every time I do an upgrade. It fills me with dread every year or so, and true enough I need to submit a ticket to try and get the forums back online. To think that that base line support for a quick turnaround on outages is either now reliant on an additional payment for a support plan, or posting in publicly accessible forums is not a sustainable proposition for me.
Creating a strong support community backed by our support technicians will result in a more detailed and richer set of answers For "how to I customise this" or "how does this feature work", the above statement is true. For critical board offline situations, the above sets alarm bells ringing loudly. Critical issues need a formal support ticketing system - which is included in the licence fee. Come to think of it, no other service I use has separate support and licence fees.
For those that wish to retain ticket support longer term, we will be unveiling a premium support option soon. No, just no.
 
I already discontinued my other IPB forums as the cost/benefit ratio slid off the scale.
A 60% price hike means I will now have to look at other options for my final licence, it would be easier if I felt any degree of trust or loyalty to Invision as I would just pony up and pay the money, however - and sadly for such a long time customer, this is far from the case. I cannot trust you as evidenced through the lifetime licence fiasco, and I feel absolutely no loyalty due to this 60% price while reducing access to critical support.
Very disappointed.
What I would like to see?
Cancel premium support plans and retain this as part and parcel of customers licences. Maintain current pricing plans for existing customers and roll out new price structure for new customers.  
 

I would be more concerned about the clients who are keeping quiet than the ones making a noise.  My mom was a fountain of wisdom right up until her demise at the grand old age of 89 years.  She used to drum this into me:
"It's OK to make mistakes, but always be sure to admit to them, take ownership and make sure that your mistakes never have a negative impact on others and if they do, then do something positive to make amends."
There's also a saying that everyone will be familiar with "Act in haste, repent at leisure"  Hindsight can be an awakening moment, but often it is too late when realisation hits home.
It's not too late to do something positive and resolve this horrible situation, but you need to act now to enforce damage control - I can see your competitors rubbing their hands in glee just waiting for the torrent of new clients heading their way. I cannot get my head around the rationalisation of this move - it really does beggar belief.

Same, I appreciate your point of view. As a businessman myself, the reality is that the smaller accounts usually cost the most in support, in both time and money. And, let's be honest, your job is to increase net margins. And these changes serve to streamline that. In most cases, changes are usually met with a public backlash, a lot of huffing and puffing and sky is falling talk, and that's the extent of it. And the truth is, IPB will not miss smaller accounts like mine. Such is life. I get that.
As a thought, you could have simply retained proper ticket support as part of a monthly subscription -- or even capped it at 3 or so included support tickets a month, then a fee per ticket afterwards -- as incentive to go post publicly in the forums. At the same time, IPB could easily aggregate information from private support tickets internally to then create an official knowledgebase of answers that could be the first line of support within people's admin areas. But still offer private ticket support directly.
FWIW, and I will preface by saying the following is via conscientious choice when making a purchase. There isn't a company I deal with that does not offer a direct line of private support communication as part of my subscription/lease/product cost -- it's a big reason why I pay for services instead of the "free versions". I expect products I pay for to be properly supported, privately. I admittedly never expected IPB to shift away from this model.
On that note, I'll bow out of this discussion.
Best regards.

I don't believe that to be the case, Matt.
I do not expect IPS to hold its prices, but this is not just a pricing issue. There are a number of issues:
It's a big price increase (46% for me), in one fell swoop, on an unsuspecting customer. That introduces a shock factor to the equation. That is entirely of IPS's making. Smaller incremental adjustments to pricing, inline with inflation, are easier to absorb and to plan for. This increase is not. It was not communicated. I cannot tell you how furious I was to find a new price on the website, with a changed renewal term, without so much as a word from IPS. I therefore have little time to absorb, reflect or plan for it, and being on the smaller hobbyist side of your userbase, I now have serious doubts about being able to continue to be a customer. That is a shame after a decade of being a loyal customer, but I guess that's part of the game. It benefits your cash flow and hurts ours. You get a chunk of cash in one go, whereas you would have previously accepted it in two. It's stated that this is in part for simplicity, yet I can see no justifable reason for this claim. How hard is it to set 6-monthly renewals? You've done it for years. Bringing it inline with industry standards isn't a compelling reason - IPS is now just as inflexible as other industry players. The communication, when it did arrive, was completely tone-deaf. "Don't worry, it's not bad news"... Yes, it is. It's not only an unexpectedly large price increase with little notice, but it's changing the frequency too. Neither of those things are good news for me. The costs were communicated in monthly terms when the renewal is now collected annually, which screams of smoke and mirrors.

It's not about the fact that prices are rising. In my country it's a constant process, they never stop. It's about:
1. That the gap between old and new prices is 50% which is a lot. I don't see many businesses do this to their loyal clients. We would understand something about 15-20%, not 50%.
2. That you guys try to sell it like "but look at monthly rate! Not a big deal!". You seem to forget that people who are able to spend hundreds of dollars on forum software are adults and wouldn't fall to cheap marketing tricks. I'm a marketer myself, and I know exactly what is happening here.
3. That you didn't inform us before this decision so any hobbyists could pay for their software. The greediness is not good.
4. That you try to sell it like IPS is the best thing ever, some premium software that is nowhere near it's competitors. But would the best software company treat it's customers like this? For real? 
5. That you tried to cover it under website redesign.
6. That you're telling us "pay more but if you have a problem - go ask community"
 
You know, it feels really bad. It's a really bad publicity. How many existing clients will recommend IPS after moves like this, how do you think?