wegorz23

Thanks, Nathan and Martin. Your replies helped. I am not using PHP, I'm using C#/.NET, and Postman for testing. I think it's a deficiency of the documentation that it assumes that the API will be called from PHP.

By reading about how PHP is resolving the arrays to POST fields, I found the problem. The actual POST format of the fields is NOT actually (for example):

Field Name            Value
secondaryGroups   [7,8]

it's:
Field Name                   Value
secondaryGroups[0]      7
secondaryGroups[1]      8

This works.

I'd add that it's an annoyance that this sets and replaces any existing secondary groups. This requires reading existing ones and taking them into account, for adding new groups. Since this is an update operation, a more common use case would be to add new groups (or delete old ones).   A suggestion, which would be backwards compatible, would be to add a new field, e.g. secondaryGroupsOp, with values 'replace', 'add', 'remove'.  'replace' would be current behavior, 'add' would add the group (doing nothing if the user were already in that group), 'remove' would remove the group.
Another approach occurs to me, also (I think) backwards compatible: if a '+' is prepended to the id, then add it to the existing groups;  '-', remove it. 

Your theme seems not to be compatible with the IPS version you’re using.

At present, it seems this is not actually a bug as such. Smaller width items are treated the same as sidebar items, which is why there is a border. This has however been brought up internally for discussion.

Looking at those logs you have several crashed tables that need to be repaired.
In addition I also see that you're using MySQL 8.0 and I've seen a few people having issues with it. It would be best to use MySQL 5.7 or an equivalent MariaDB version instead.

There is no such option build in the software a.f.a.i.k. This will require a custom application.

Are you actually using PHP 8.0 for the site itself?

You would need to take a look at your server configuration. Just a quick google on this
 
https://serverfault.com/questions/517190/nginx-1-fastcgi-sent-in-stderr-primary-script-unknown
 

Right, so this bodes well for well known and established devs as they have already created a foundational trust model with clients.  For new devs, that's a barrier they'd have to create over time.  Meanwhile, clients either have no way to validate new devs work like IPS previously did to guarantee the safety of the app/plugin.
I think this greatly elevates the risk for clients and subsequently harms the potential for developers to grow the product.  Hobbyist sites will suffer the most as they simply don't have the resources to invest in robust security evaluation.
Perhaps another opportunity for a dev to provide some level of AppSec and InfoSec scanning of applications to lower the risk.  

One potentially large gap is the validation and approval process done by IPS to guarantee the Marketplace developer's app/plugin aligned with IPS standards before it was approved for client download.  How will this be managed moving forward?

I have that option for years through a third-party solution. Get ready to be insulted. 😉 People who leave a community in anger (e.g. after moderator actions) will love the opportunity vent their anger one last time, blaming and insulting you. I can’t remember a single time a text-based option to give reasons to delete an account was actually useful. If anything, I would suggest a checkbox list with admin-defined options. 

A quick test
- Your message for guests to sign up is your LCP - and it creates a serious delay…
-Core Web Vitals Assessment: Failed
- You have a problem with contrast on different buttons
- Low image resolution
- Having an issue with touch target areas on mobile
etc.
I'm not sure which of my tips you've used/removed - but a tip doesn't do magic, it's just a stepping stone to a path of improvement...
You have, simply put, a lot of work to do, after which Core Web Vitals  will improve. And loading speed too. With one or two tips, there is ore no way this will happen.
I have an idea and how to improve loading JS - and for me in my site it works well... But I'm not sure how it will work for everyone else - because I analyze many varius of the resources and mine - and monitor their behavior in repeated tests... There are many dependencies that influence each other when changed - and this cannot be created as a general rule... It is individual according to what each site uses... In some sites, certain css rules displayed in critical css improve loading speed, but these rules are not chosen randomly, but after analysis...
To use ads - every block in which ads are displayed on your site should be of a fixed height - otherwise your metrics will drop sharply, because your CLS will increase significantly, and this will decrease loading speed... etc.
 

ok thank you for letting me know. I will go ahead and copy and replaced all the files.
Thank you for your help. 

If you have not updated in that long, you will most likely need to upgrade PHP and make sure your server meets the requirements.  Once on PHP8, run the following script:
Again, only do it after you switch to PHP8.  It will tell you if it is ready for the latest version of IPB.  
Temporarily disable any third party plugins/applications.  
Once everything is good, download a set of files from the client area and upload them to your site.  (Replacing everything already there.). Then run domain.com/admin/upgrade.  Let it walk you through upgrading.  Once done, login to ACP, make sure any resources are updated and turn them back on.  Test things to make sure they're good!  
You might need to update your theme or switch to a new default as well if your theme is super old.  
 

Anything uploaded by the users would be located in the /uploads/ folder typically in a subfolder like monthly_XX_XX like:
/uploads/monthly_2023_04

Thanks for the help, guys!
@Ryan Ashbrook Are the conv_password and misc columns safe to remove? We moved from vBulletin to IPS 10+ years ago... LOL
I also need some advice if it is safe to remove these:
cm_reg referred_by gallery_perms pp_setting_count_visitors Thanks!
Thanks, I was able to find their origin here in an old spreadsheet. They were from a plugin called "Sign in through Google", available in the 3.4 era, before this functionality was incorporated in the core software.

These are a part of the converters application.
conv_password misc  

Chunking seems to be the answer... Changing upload_max_filesize / post_max_size to 50M each seems to work.  I turned the proxy back on in Cloudflare and have been able to upload multiple large 250MB+ files without error.

Correction Cloudflare Free and Pro have a max upload size of 100mb.

Is that the time that an automated backup of your site's database takes place?

@Adriano Faria +1.
I suggest replacing ipsGrid with ipsFlex and add ipsResponsive_pull to cover background and buttons.

I think it's good SEO-improvements is done, but in this case I feel it's at the expense of guest user experience. Why can't this be solved with indicating nofollow or adding it to robots.txt? If the link is not gonna take you to what you expect as a guest, then why have it be a link for them in the first place.

Hello
I have some problem on ips lightbox or attachments images.
Its not showing at all on page on every field that is added as editor data.

 
The problem i just match and solve at first after update to 4.7.11 was to upload old files to javascript_global
 

The structure of DOM html is fine and looks like normal but script root_library is crashing. 

 
Is anyone have some problems like me ? 
I just upload old files to that folder and its solved the problem but on next update i need to fix that problem if script changed.
 
 
 
 
 

The easiest wait is to move that spammers to some member group and then on ACP panel remove them that profiles or just filter that in ur ACP panel and remove one by one.
We ban some spammers accounts every day and mark them as spammer. (it is because it hide all posts and block that account)
 
to solve problem we installed cleantalk plugin and it fixed ur problem like in 99% of the time. 
 

There isnt really any way around that unfortunately. You would need to mark them as spammers individually which would remove the content alongside them. I realise you are looking for a quick solution there, but there isnt one available I can recommend 

Do not delete them with a SQL query. Member data is all over the place in multiple tables, if you delete it only from the members and topics/posts tables you'll be in for a lot of weird issues all over the place.
 
The best solution I can give you is to create a new group in ACP (call it TO DELETE or whatever), and then update the member_group_id column for all those members you've identified to the ID of that new group. Once that's done filter your members in ACP based on the group, and then prune them from the member search results page.