Hisashi

Maybe it's just my opinion 😅, but why don't make this IPS4 default menu?
It has a beautiful design, visually more organized and visible.
 

 

Hello,
I just reinstalled a test suite and the following date error is occurring.
Version: 4.7.1
Did the same happen in the previous version? (4.7.0.): No
Apps: Only Pages app
This is a test suite, NOTHING has been modified.
 
Date of first article created (default)

Creating a new article
1

2

3

 

Hello,
I just reinstalled a test suite and the following date error is occurring.
Version: 4.7.1
Did the same happen in the previous version? (4.7.0.): No
Apps: Only Pages app
This is a test suite, NOTHING has been modified.
 
Date of first article created (default)

Creating a new article
1

2

3

 

Comes from Commerce:
'reply' => "Reply",  

Thanks, I have filled a bug report for this ( We need to move the "show_all" lang string to the core app because it's used in core and blogs too )

show_all is a language bit added by Forums app:
'show_all' => "Anytime",  

Pages such as those below should be included in robots.txt, google unnecessarily wastes time on them.
https://invisioncommunity.com/pastleaders/ https://invisioncommunity.com/languages/ https://invisioncommunity.com/applications/ (if we set the guest to be unable to download attachments) https://invisioncommunity.com/tags/* (since the tags have noindex, they should be removed for guests or at least a link) /notifications/ 

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. 
 

If it was a snake it would have bitten me 😅
I still changed this but I didn't enable the option.

ACP -> Customization -> Themes -> edit Theme -> enable "Enable fluid width?" -> change "Fluid width size (in %)" to your liking.

Hello,
The idea may seem simple and silly, but i thought it might be interesting to have something like that as information.

 

(NE) Language - user counts 1.0.0.xml

Exactly.

Are we going to loose below current existing nice drop with new one which looks ugly + limited in functionality? 

I made some severe changes to the Our Picks Carousel on the front page, you're welcome to use and adapt the following CSS changes that allows some significant manipulation of the Our Picks.
This is before the changes:

This is after the changes:

 
/* Adjust our picks front page */ [data-role="carouselItems"] .ipsType_medium:not( .ipsType_richText ) { line-height: 1.53; display: none; } .cPromotedWidget_horizontal .cPromotedWidgetItem_content > .cPromotedWidgetItem_contentInner { flex-grow: 1; display: none; } [data-role="carouselItems"] .ipsPhotoPanel.ipsPhotoPanel_tiny.ipsType_blendLinks.ipsType_light { display: none; } [data-blocktitle="Our picks"] .ipsCarousel .ipsCarousel_inner { height: 330px !important; } .cPromotedWidgetItem .cPromotedHeader { min-height: 279px; } .cPromotedWidget_horizontal .cPromotedWidgetItem { width: 187px !important; display: flex; flex-direction: column; } .cPromotedTitle { font-size: 14px; font-weight: 600; } .ipsPad_half.ipsWidget_inner.ipsWidget_bottomBar { display: none; } .ipsBox--child { box-shadow: none; border-style: none !important; border-width: 0px !important; border-color: #26323e !important; } .cPromotedWidget_horizontal .cPromotedWidgetItem_content { padding-bottom: 15px; text-align: center; background: rgb(73 8 46); } Hope that helps 🙂
 

Generally, it breaks javascript. We have found this to be the case on numerous occasions. If its working for you, great. However if you have problems, its very likely that is going to be the cause.
When using cloudflare, the one thing you have to bear in mind is if you have issues we will ask you to disable it entirely for testing. So you should ensure you can do this relatively easily. It is worth noting that quite a high percentage of issues we come across are caused by the use of cloudflare. This is not to say there aren't people using it without issues, as you can see above. Just something to bear in mind.

A new 1.0.1 version is currently pending approval from IPS. Here's a preview of the changelog:
 
@Hisashi I looked into your request and I found out that CMS already provides a way for an admin to change the number of comments per page. The problem is that it is tied to the Database setting in "Field Options > Records per page". As the name implies this setting control the number of records shown while viewing a category, but I found out it also controls the number of comments per page at the same time. The problem is that you can't have 25 records show per page and only 5 comments; it's either 25 records/comments or 5 records/comments.
Now, this to me looks like a bug actually. Depending on how IPS decides to handle the situation there's no need for me to add it to my plugin. For now I'm going to make a bug report for IPS to look into it.
 
EDIT
The bug report is here:
 

Here I left it at 90 too, my website is a manga reader so I try to preserve the image quality as much as possible.
As only my team uploads to the server, so consumption is based on what is offered.

I found the problem. It will be fixed in next version.

This is due to 'JPG and WebP Quality' (ACP > System > Overview > Files > Image Settings)
I also think this is a problem as I understand when it reduces the quality if so set, but not when it increases beyond the file size.
It's like the system makes it 110% size.

Yes, I like the idea of notifying someone when a topic is viewed a lot.

In addition, it also helps users who don't have an overview of things to understand what is making success in community.

Hello,
I have AdSense and 'Google Search Console' and every month they email me growth statistics. Informing me about my performance in the service, if it increases or decreases, these things...
What if the IPS4 had something similar? In this case, a notification to the user informing that their content had "x number of views/downloads/comments/review".
Ex:




 
The admin would define "x amount" a notification would be sent. 

Whenever reach a goal:
Ex:
+1k = 1k, 2k, 3k... +5k = 5k, 10k, 15k... +10k = 10k, 20k, 30k...  

I see you use cloudflare, you tried clearing the cache?

Hi guys,
As usual, we face limitations when translating certain strings since in English there is no male/male words like in Portuguese, Spanish etc.
In addition, some words in English don't change regardless of singular/plural.
Right now, the following strings that are giving us trouble.
notification__unapproved_content_bulk_title
notification__unapproved_content_title
These two strings default to: ⚠️ New %s awaiting approval
There are two problems here:
1. We don't know deforehand whether "%s" will be a male or a female word. "New", in English, doesn't have gender, but in Portuguese/Spanish/etc the adjective changes depending on the noun: Nova (female) / Novo (male). And we have a mix here! Some examples:
Male: post, tópico (topic)
Female: avaliação (review), respostas (reply)
2. We don't know beforehand wether "%s" will be a singular or plural word. In English, "New" doesn't change with singular/plural, but in Portuguese/Spanish/etc it does. So, if we translate "New" as "Novo", when %s is plural, the grammar is incorrect (ex: "Novo posts" instead of "Novos posts").
I tried to use the {!#[1:novo][?:novos]} trick, but it didn't work here. But this would fail the male/female problem anyway.
I got a little creative here and solved this by translating this string as:
⚠️ Há %s aguardando aprovação
Instead of using the adjective "New", I changed it to the verb "Há" (There is/There are). So we have "There is/there are %s awaiting approval". The meaning is slightly different from the original string, but it does the trick.
Even though I have found a solution, I thought it would be interesting to tell you this, so you understand the challenges we face when running non-English communities.
However, the major issue now is with the following string:
notification__unapproved_content_grouped
Which defaults to:
There are {count} new %s requiring approval %s
Here, since we have the {count}, we can correctly apply the singular/plural trick, so I translated it to:
Há {count} {!#[1:novo][?:novos]} %s aguardando aprovação %s
The problem now is, we don't know whether the first "%s" will be a male or a female word. So we have a gender mismatch whenever it is a female noun.
Now, another issue we have is when it is a review in Pages that is pending approval. It is pulling the string "avaliação" (review), in the singular form, even when more than one is present. See the screenshot below. This may be a bug, maybe the system is pulling __defart_content_record_reviews_title instead of __defart_content_record_reviews_title_plural, and I kindly ask you to take a look into this. In other words, which string is being used in the first %s when the this notification is about reviews in Pages.
I hope I was clear enough for you to undertand what I mean, and let me know if you need any additional information.
Best regards,
Gabriel Torres