Interferon

A lot of times someone will send me a private message. I open it, and it turns into something much more detailed than I want to deal with right now. I can't answer right away, but if I leave the window I am likely to forget about the message completely. In situations like this it would be helpful to be able to mark the message as "unread" or some equivalent state, so I still have a little red notification reminding me to deal with it later.

@Interferon we do have a great plugin for that. Thanks to Adriano for it. 
 

Member group color is a surprisingly effective way to stratify your membership levels. If I see a gold-colored user name I easily perceive that member to be more valuable than the default white color free users have (we use a dark theme). It very quickly conveys importance in a subtle way and makes the paid members stand out.
However, member group colors are not displayed consistently across IPB. The recent users online block does not show colors. The forum index page does not show the user name for each topic in colors. On mobile, in the topic view, when the member group is hidden, the user name is shown using the member group color.
I suggest applying the following rules:
When the member group is shown, display it in color and use the default color (black, or in our case white) for the user name. When the member group is not shown, display the user name with the member group color.

I like the fluid forum view for staying on top of the forum contents, but the categories list takes up a lot of valuable real estate on a page we are trying to make the most of. I suggest making the categories box collapsed by default, and then allow the user to expand it when desired. Maybe this can be done in a drop-down box like the compact view does it.
We have a side bar filled with other stuff, and its a little awkward that the fluid and traditional views result in a side bar with a much different height.

I like the fluid forum view for staying on top of the forum contents, but the categories list takes up a lot of valuable real estate on a page we are trying to make the most of. I suggest making the categories box collapsed by default, and then allow the user to expand it when desired. Maybe this can be done in a drop-down box like the compact view does it.
We have a side bar filled with other stuff, and its a little awkward that the fluid and traditional views result in a side bar with a much different height.

Could we please have the possibility to add a 'NoAI' tag to our forums content?
I frigging hate these algorithms. 
😅
 
Thanks!
--
Rick

"Grammarly"
 

@onlyME If chatbox+ supported the REST API we could build out own Discord.  Not sure how hard that would be to add.

One thing that can drive me crazy is when layouts are not symmetrical. When viewing the first page of the blogs everything looks fine, two posts at the top and then 3 posts per row. 23 posts in total per page. However, when going to page 2,3,4 etc. 23 posts per page becomes an uneven number and ends up with a blank space at the bottom.
I would suggest to change the number of blog posts from page 2 and forward to be either 21 or 24.
I know it's a small and probably not important change but I hope it can be fixed at some point if not at least for the aesthetic aspects of the theme.

I have found webp to be only marginally better, or in some cases worse then JPEG.
There's no way this format would have caught on unless it was being forced by Google. I know an image format that is (really, not Google's BS numbers) 30% smaller than JPEG and it isn't supported by any browser.
In my view, the only reason to use webp is if Google is giving ranking preference to sites that use the format (based on the format, not the file size). I think their approach has been to introduce constant change to web standards in order to make sites that can't afford to keep up obsolete. It's just a way to coursely rank content and tell which sites are being actively maintained and have the resources to keep up with constant changes. Microsoft use to do the same thing to desktop application development.
However, I can't find anything conclusive on whether they actually use the format itself as a ranking factor.

I disabled all add-on applications and plugins and switch to the default theme. Same behavior:

If I go to the notification settings using Edge browser, I am able to enable them:

But with Brave browser it hangs:

Chrome seems to work as well.

Renewals always happen unless a user cancels or it expires. Automatic payment would only happen if the user has a payment method on file that is capable of automatic payment. 

There is still BTCPAY Gateway App, it works on 4.7 without issues.

I have created a ticket on this, so we can take a closer look and see what is happening there for you

You can control who can view but if you’re allowing everyone to view and they filled it before you install the plugin and set which groups can use it, obviously they will show for those who can view.  Your only option is to delete their content.

Hello @OctoDev
I just purchased the Coinbase plugin. I configured everything as explained but I wanted to ask you probably a silly question.... But I need to understand how it works before I test this out.
I follow the payment steps until I am prompted to:
Pay with Coinbase (login required) Send payment using QRCODE My question is about renewals. My products also have renewals. What happens with renewals then? If someone manually pays with the QRCODE, what will happen after a month when he has to pay automatically an invoice? Is it done automatically? If no crypto available in the same wallet, then the membership will be stopped because the invoice hasn't been paid?
Thanks a lot

I uploaded the files, then navigate to /admin/upgrade, log into my account, pass the requirements check, and it asks for my license key. When I enter my license key it says:
There is no mismatch between the URL listed in the client area for this key and the install location. They both match.
How to continue?
---------
Ah, I was missing "www." in the URL. It is working now...

Thanks, This seems to be an oversight.
I have logged an internal suggestion for this.

Happy Hump Day.
Identifying what members are frequently searching for is an important job for community managers. Built directly into the statistics panel of your ACP is a section that includes the most-searched-for keywords. Understanding what people search for helps you:
Improve upon those items Create more content around the term(s) Provide further clarity for people who search for the word or phrase in the future Because of the importance of search, we made some major improvements!
You may have noticed Invision Community introduced an update to our Search Bar user interface. @AlexJ certainly did 😜.
 

 
Previously, the search bar was smaller in size and included different options that could be confusing at first glance.
We've simplified the search experience. Should the user want to drill in further, they have that option on the search results page:
 

 
Go ahead and give our new search UI a test drive. Feel free to share your findings / thoughts in the comments. 😃 🔍 
---
As always, here's a list of updates and fixes made to the platform in the last seven days.
4.7.1 Beta 2 is out now. Release notes here.

See you in the comments. 
 

This code does it, but does not properly parse the CSS attribute, so if any other style elements are added it will fail:
 
<?php function getBlogHeaderImage($url) { $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $page = curl_exec($ch); curl_close($ch); // Remove some HTML elements $dom = new DOMDocument(); $dom->loadHTML($page); $classname="cBlogEntry_withPhoto"; $finder = new DomXPath($dom); $items = $finder->query("//*[contains(@class, '$classname')]"); if ($items->length == 0) return ""; $style = $items[0]->getAttribute("style"); $style = str_replace('background-image: url("', '', $style); $style = str_replace('")', '', $style); return $style; } $url = 'https://linustechtips.com/blogs/entry/2114-you-dont-want-to-use-a-linux-converted-chromebook/'; echo(getBlogHeaderImage($url)); ?>  

@Interferon I reached out to the plugin developer and he has extended the support of the plugin to cover blogs, etc and has submitted it to the marketplace for approval, so keep an eye out for the update🙂
 

My users make these mistakes every day:
https://www.ultraengine.com/community/blogs/entry/2778-finalizing-terrain/?tab=comments#comment-14301

One nice features of Github's markdown implementation is that it automatically removes double-line returns between paragraphs, and lines before and after the text content. This makes it so you never have those annoying errors that mess up the paragraph spacing.
 
You know what I mean?
People make these kind of errors all the time. I don't want to go in and edit their content to remove such a minor and common mistake, but it makes things look ugly.
 
 
 

I am not asking for help writing paragraphs. I am suggesting a way to clean up a very very common user error.