Jennifer M

Welcome to life at IPS.

That's only because google can't handle us.

I'd even be so inclined to say that a Private Club or "PMs" which are just private conversations can reach that goal with no issues. The PMs being available depending on how the site staff have it setup but you can include specific members in a PM exclusively. I'd probably say a private club would be more user friendly though.

At this time this behavior is working as intended. You can make a suggestion in feedback and suggestions.

No, as I said in my previous post manually registering an account bypasses the IPS Spam service entirely. It won't even check the email if you register them. Unfortunately, as for the why it was flagged as a spammer, I cannot provide further details. The spam service takes a lot into account when it provides a level to an email so it could be any number of things. It's rare but it could be a false positive, thus the fail safe to manually approve or register the user.

A level 4 response means that in our system the account is a known spam account. To change how your system deals with those you can go to Members > Content Moderation > Spam Prevention > Click on the "Spam Defense" tab and adjust these levels appropriately. Currently your system is likely set to "Disallow Registration" for a level 4, thus the specific error you're getting. If you would prefer to keep this setting in tact go to Members > Members > Click the Create New Member in the top right and manually register the member. This will bypass the IPS Spam service. @kherezae

Hey @kherezae this looks to be an issue with the spam service and your settings. Most likely you have a Spam level 3 or 4 account within the IPS spam service set to deny registrations (instead of register and ban or register and require admin approval). In this case you can either manually register the member or change the spam registration settings so that you can manually register the account. This will have nothing to do with gmail accounts in general, just this specific users email address.

@kmk each field has a "View", "Add", and "Edit" permission for each group. View is whether they can see it on the record, Add means that they have permission to see that field when they are creating a new record and Edit means whether or not they can edit it after the record has been created.

It's technically easier not to do it by just checking to see if the person is an admin (since technically you can add administrators without them being in the admin group) by using this: {{if \IPS\Member::loggedIn()->isAdmin()}} What you want admins to see. {{endif}} Additionally, in pages you can set fields so only specific groups can view them using the permissions for the custom fields. Hope that helps @Brian

Try using this. It won't use the integration but will allow users to join the chat: https://deploys.io/docs/disweb/

.cForumRow .ipsItemStatus.ipsItemStatus_large.ipsItemStatus_read { background: #000; opacity: 1; }

The item status badge only changes for unread. The greyed out background would require a change to custom.css

Yes. Add these items to the custom.css if you need them to be more forum specific you can do that too. This is just generalized replacement.

Hey @AlFed @steve00 is correct, there is some manual style bits in your global template. I don't know how you uploaded the theme but it's still there. Particularly this bit: <style> #ipsLayout_header header { background-color: #3d5e78; background-image: url(http://www.spain4you.es/forum/uploads/monthly_2016_12/699329.jpg.716a4acadcfee74382d1192a0d378f0e.jpg); background-repeat: no-repeat; background-position: center; background-size: cover; } </style> Now, note that the image doesn't actually load for me at all but that's why your header color isn't changing. To me it looks like someone copied the CSS and pasted it into a style code in your globalTemplate. Your globalTemplate is the first thing that opens when you open the theme editor so look in that one.

Hey @Vianney Gantelmi You can achieve this through CSS. If you want to use two different Font Awesome icons (this includes changing the background color too): .cForumRow .ipsItemStatus.ipsItemStatus_large .fa.fa-comments::before { content: "\f0a2"; } .cForumRow .ipsItemStatus.ipsItemStatus_large { background: #FF0000; } .cForumRow .ipsItemStatus.ipsItemStatus_large.ipsItemStatus_read .fa.fa-comments::before { content: "\f0a2"; } .cForumRow .ipsItemStatus.ipsItemStatus_large.ipsItemStatus_read { background: #000; opacity: 1; } For two different images you would do this: .cForumRow .ipsItemStatus.ipsItemStatus_large .fa.fa-comments::before { content: url(PATHTOIMAGE); } .cForumRow .ipsItemStatus.ipsItemStatus_large { background: transparent; } .cForumRow .ipsItemStatus.ipsItemStatus_large.ipsItemStatus_read .fa.fa-comments::before { content: url(PATHTOIMAGE); } .cForumRow .ipsItemStatus.ipsItemStatus_large.ipsItemStatus_read { background: transparent; opacity: 1; } You can do similar things for the topic list etc.