Looking at things it seems to me that another CA cp* would be the best way forward for the reasons above.

Okay thanks, Sorry if I bumped this task and replying late.

Gotcha. Thanks.

In T8017#161744, @Reception123 wrote:

We'll change the WikiForum message (cc @Universal_Omega ) shortly.

We'll change the WikiForum message (cc @Universal_Omega ) shortly.

We've recently updated our Captcha system from ReCaptcha v2 to ReCaptcha v3. This new Captcha system no longer requires you to fill something in and works in a different way (you can Google "ReCaptcha v3" for more info). If you look carefully at the bottom right you'll see a small Captcha box that pops up which confirms that Captcha is being checked in the background. (For the record so far it's been doing a great job)

@jimbomorrison There's nothing left for you to do, it still needs an approval from @John (the other EM) and then it can be added.

Awesome. thanks. Does this mean that it can now be added? Does anyone need anything further from me at this point?

Fixed by rebuilding the text index.

We can't advise how to fix it until we know the cause

Oh, but I just want to know how to fix this for myself.

We're volunteers. It's going to take more than 14 hours to review.

Umm, why isn't anyone responding to me about this problem?

The code is:

Do you think that mw.loader.load('https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js', 'text/javascript'); causes the problem? I added this statement to the common.js because of the <math>-bug https://meta.miraheze.org/wiki/Community_noticeboard#Limit_on_%3Cmath%3E_tags_or_just_a_bug?

Privacy concerns have been addressed over the years, particularly with more strict legislation limiting what information can be used for - this occurred 6 years ago. For the security side, resolution and investigation seems quick and thorough, no concerns were raised over the matter.

No concerns regarding the lack of mentioning GDPR in the PP, information is only retained for 7 days before being deleted and such collected information relies on consent as the mechanism, not a legitimate interest.

The assessment seems thorough and accruate.

A brief review of the relevant Japanese legislation suggests it is similar in terms of principal rights as GDPR, therefore this can be approved.

IP addresses can't be linked in a way to create an individual user profile, email address would be out of scope of Miraheze's purview. Therefore, this can be approved.

Here's the proof{F1494467}

Oh, but when I typed 'edman' there were no results as there's no page title or text matches for this page. I think it was broken or something.

I can't seem to reproduce this issue. I found a random page 'Edman Silimedia' and searched for it and it came up as it should.

Every page. When I tried to enter any keywords that has title or text matches for an exact page I already have created. There is no results found.

Which page was this?

Just noting that this is still continuing (confirmed via Graylog)

In T8013#161648, @69unfortunately wrote:

@RhinosF1 do whatever you need to do. We just want it so that only approved users can make edits, while nonusers etc. can only view.

Reception123 has reset permissions. You only need to remove 'edit' from the '*' group. Nothing else.

Permissions reset to default.

If this is not fixed, please reopen the task.

Doing https://github.com/miraheze/mw-config/commit/4bcb6424d0694f08ee9aa5f53e8e57d2aa0ed3a3 I think will fix the issue.

@RhinosF1 do whatever you need to do. We just want it so that only approved users can make edits, while nonusers etc. can only view.

In T8013#161645, @RhinosF1 wrote:

The permissions are seriously messed up

@69unfortunately: it's probably going to be easier to just reset ManageWiki permissions to default, can we do that?

The permissions are seriously messed up

The issue is with PortableInfobox. Paladox did an upstream PR to hopefully fix this: https://github.com/lkucharczyk/mediawiki-PortableInfobox/pull/46 not much more we can do on our side.