Gabriel Torres

Hello,

Evaluating our website with Google's Lighthouse, I came across this:

This was easily fixed by editing core > global > framework > fonts.css and adding:

font-display: swap;

To 

@font-face {

I recommend adjusting this in a upcoming release.

More info: https://web.dev/font-display/?utm_source=lighthouse&utm_medium=devtools

Thanks.

23 hours ago, Mopar1973Man said:

CLS is my biggest thing. Mostly cause by Google Adsense.

This should be easily fixed by adding a <div> with height parameter around your Google AdSense code:

<div style="height: 250px">

[your google adsense tags]

</div>

Thanks @Mopar1973Man and @ptprog for all the pointers. I will take a look into all that was said and get back to you. All I need now is some spare time... LOL

@bfarber

20 hours ago, bfarber said:

Ultimately your setup looks like it would ban users each time they get a point, so the other settings seem pretty pointless actually.

Thanks for the pointers. I actually realized that we shouldn't ban the users with 1-4 points, just restrict their content, and ban only with 5 points. See the new configuration in the screenshot below.

That said, isn't it redundant to have three options (moderate content/restrict from posting/ban) for each warning point? IMO, we should be able to choose only one of the three for each point. (That's where I got confused.) Maybe this is something that could be improved in a future release? Because it doesn't make sense to set more than one option for each warning point.

Thanks! 🙂

Hi there,

Currently we have the configuration below.

The issue our moderators are questioning is this.

If we give a user his second warning, he will be restricted from posting for 7 days.

If, however, within this period we give him another warning (his third, in this case), the system doesn't add the remaining number of days from the previous warning to the new number of days.

For instance, if the user gets his second warning today, and later today he gets his third point, he will be restricted from posting for 15 days instead of 22 days (7 days from the second point + 15 days from the third point).

Is this the intended behavior? Is there any workaround?

Thanks in advance.

@ptprog Many thanks for your pointers. I added woff2 files to the list and increase the cache to 1 year as suggested. Can you please tell me which tool to use to check these cache expiration durations? This way I can check if the changes I made worked.

As for the server response time, I don't even know where to start. One issue is that we have to load advertising banners, and these usually take a while, increasing the page load time.

Hi,

Our moderators are asking that whenever a post is marked/unmarked as solution, this action to be recorded in the topic log, so other moderators can see who marked that post as solution (e.g., was the topic's author or another moderador?)

Thanks.

@AlexJ Please open your own topic; your question has nothing to do with my topic here.

Hello,

One issue that I noticed today is that when someone clicks on the "Subscribe" button at our subscriptions page (/subscriptions/), a new invoice is ALWAYS generated. This way, we end up with TONS of unpaid invoices created by guests... See below:

Right now, we have 106 pages of this.

IMHO, the invoice should be created only AFTER the user commits to pay.

Cheers.

@Morgin Got it. As mentioned above, I disabled it. Thank you very much for coming back and detailing the issue! 🙂

30 minutes ago, Ryan Ashbrook said:

It can break the editor and cause it to not load in some cases. I'm not sure of the configuration options for Rocket Loader, so it may not be an issue for you. Every instance I've seen, disabling it resolved the issue.

Thanks @Ryan Ashbrook for detailing what @Morgin mentioned. I will disable it "just in case".

On 12/18/2020 at 7:11 PM, Fast Lane! said:

I'm fairly certain the sidebars on the site are delayed when loaded causing CLS issues, largely on the desktop view.  

Thanks, the majority of errors are coming from mobile.

On 12/18/2020 at 7:11 PM, Fast Lane! said:

For ads just put a DIV around them with the size of the ad. That will fix the CLS issue. 

Yep, done that. That was exactly what was shifting the layout. Now I just need to wait until Google validate these changes. Thanks! 🙂

6 hours ago, Morgin said:

Cloudflare Rocket Loader usually breaks IPS, as a heads up. 

Really? What do you mean by "breaks IPS" exactly? Could you be more specific? Because we are using Rocket Loader for quite some time now and haven't seen any issues with it.

@Adlago Many thanks! It is great that I can enjoy your experience!

@Adlago Many thanks for this tip, done that. I will investigate a little bit further every day, I made saveral small adjustments and fixes during this weekend. Let's wait and see how the metrics react to them.

I was just wondering why adding the font awesome preload at the end of the page and not at the start...

https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content

It seems these FCP/LCP issues are being caused by the advertisement banners we have on our website. I made a few changes, but will continue investigating this further in the coming days. Thanks.

1 hour ago, Adlago said:

For starters - eliminate all errors

https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.clubedohardware.com.br%2F

Fixed all that I could. There are still errors caused by:

(1) Cloudflare's Rocket Loader (A script element with a src attribute must not have a type attribute whose value is anything other than the empty string, a JavaScript MIME type, or module). I am not sure if there is anything we can do about those.

(2) Group Name Indicator plugin, which the developer has just fixed for us and we are waiting for approval at the marketplace.

I will take a closer look at the FCP/LCP metrics tomorrow. Pointers are welcome.

Thank you for your help! 🙂

@Adlago Thanks, will work on that and get back to you as soon as I finish this.

Meanwhile, I was wondering if the CLS errors in Google Core Web Vitals were being thrown because of the IPS Lazy Loader feature.

1 hour ago, Adlago said:

Please share a link to your community for tests.

Ops, forgot the most obvious... LOL https://www.clubedohardware.com.br

Many thanks! 🙂

Hi,

We've been badly hit by the Google December 2020 Core Update: our traffic comming from Google dropped 20% starting December 4th, 2020.

Investigating this further, I came across the Core Web Vitals, available at the Google Search Console, and our numbers are really bad there, especially for mobile. See screenshot below.

I am wondering if you guys are seeing the same (meaning this is something to be improved in the IPS software itself) or if this is caused by our custom modifications such as advertisement/banners.

Thanks in advance for any tips on this issue.

@bosss that is correct.

Another two bugs that I've just fixed.

Without this, the notifications layout breaks on mobile devices.

CSS

core > front > custom > fmdark.css

Remove the width.

Before:

.ipsMenu_innerContent {
    max-height: 350px;
    overflow: auto;
    width: 450px;
}

After:

.ipsMenu_innerContent {
    max-height: 350px;
    overflow: auto;
}

And without the !important applied to #elFlashMessage, flashmessages ("inline notifications") for reports are always with the default blue background instead of using the color the user selected in the color picker.

Templates

core > front > global > fmDarkCustomCSS

#elFlashMessage {
	background: {$colour} !important;
}

core > global > global > fmDarkJSBG

#elFlashMessage { background:' + colour + ' !important; } 

More fixes:

Templates:

core > front > global > fmDarkCustomCSS

Add:

.ipsTabs_activeItem {
    background: {$colour} !important;
}

core > global > global > fmDarkJSBG

Add to the logic:

.ipsTabs_activeItem { background:' + colour + ' !important; }

CSS:

core > front > custom > fmdark.css

REMOVE one intance of the code below because it is duplicated:

.ipsTabs_activeItem {
	color: #fff !important;
}

Hi there!

With the new 4.5 series, we have a new functionality, "set best answer/solved".

However, if moderators are configured to moderate only certain forums, they will only be able to set a post as best answer/solved if the topic is in the forums they are listed as moderators.

IMHO, it is missing a setting to allow moderators to set post as best answer/solved in all forums.

Therefore, I think that in the moderator settings, it is missing an option under the 'Content' tab to allow this.

For example, under the 'Content' tab we have the 'Can enable/disable moderation on all content?'. With this option enabled, the moderator can enable/disable moderation in all topics. With this setting disabled, a new option shows up in the 'Forums' tab, 'Can enable/disable moderation on topics?'.

Following the same idea, in the 'Content' tab I think we should have a new option:

'Can set best answer/solved on all content?'

With this option enabled, the moderator would be able to set posts as best answer/solved in all forums.

With this option disabled, only then the current option 'Can set best answer/solved for questions and topics?' would show up in the 'Forums' tab.

I honestly think this was an oversight from your team! 🙂

Thank you in advance.

Cheers!

20 hours ago, bosss said:

What made those changes? have you some screenshoot?

/* Logo */ = without this, only the upper half of your logo will be clickable

/* Breadcrumb */ = without this, the breadcrumb is hard to read

/* Mentions */ = without this, mentions are hard to read

core > custom > fmdark.css

change

.ipsTabs_activeItem {
	color: #fff;
}

to:

.ipsTabs_activeItem {
	color: #fff !important;
}

Add this to custom.css:

/* Logo */
#elLogo {
  z-index: 2001;
}

/* Breadcrumb */
.ipsBreadcrumb {
	color: inherit;
}

/* Mentions */
a[data-mentionid] {
  color: #000;
}
a[data-mentionid]:hover {
 color: rgb(var(--theme-text_color));
}

17 hours ago, Gabriel Torres said:

@TheJackal84 Another issue here, in the user's activity stream, when we have a topic that was hidden, the layout gets broken.

To fix this:

core > front > custom > fmdark.css

/* Activity stream overview */
#elProfileActivityOverview .ipsStreamItem, #elUserContent .ipsStreamItem, #elSingleStatusUpdate .ipsStreamItem {

Change:

margin: 0;

To:

margin: 0 13px 0 13px;

@TheJackal84 Another issue here, in the user's activity stream, when we have a topic that was hidden, the layout gets broken.