The Dark Wizard

It is just reindexing the post index now for the search engine, there are no more background tasks related to rebuilding messages or content. All PM quotes have formatted with "\ said:" for example, and all mentions in messages have the issue posted previously. Topics do not have this issue.

It seems that all quoted names in PMs mess up. This does not seem to be the case for topics. It also seems mentions break in PMs but correctly reformat in topics as well In PMs, all things that are supposed to be mentions turned into uSER for some reason. All mentions work correctly in posts:

Thank you.

Invision Community v4.7.0

Good to know, thank you. Wanted to make sure there wasn't an issue from the start, as we prepare in the foreseeable future to wipe the conversion and start again.

Hey All, We are looking at possibly replacing ElasticSearch with OpenSearch and according to some topics and posts around the community, this seems to be possible. This post in particular seems to suggest that 2.0 is usable: However, we get a notice in the Admin Panel: The same error message appeared with 2.0.1 and 2.1 However, 1.3.4 seems to work fine.

Out of curiosity, which background task fixes the Last Poster Box Thread IRL You'll notice in my next image, that while I have the thread in the above picture selected, that the URL/ID via the last poster box is zero. So, when I click on a thread via the last poster box, it shows no permissions as expected. But if I actually enter the forum topic list: I'll get the proper URL: From the topic list, I can enter the topic properly, read its contents etc. I assume one of the background tasks currently running will fix the last poster box? Remaining Tasks:

There is a typo on the gamify page: Link: https://invisioncommunity.com/innovate/gamify/ The word "they" I've highlighted should be removed.

Ah. Yeah, on our site, supporters don’t get anything extra, we don’t paywall any feature. In our previous software the explicit purpose of the supporter group is just to apply styling. I’ll see about supporter just being a clone of Members then.

By don’t change I meant as in leave it as default and unedited except for styling. So don’t apply any forum or group permissions to the supporter role. That way a supporter gets their permissions from the members secondary group (which is primary for non supporters and a majority of people) if members can see forum xyz, then it sounds like I don’t need to duplicate that for supporter.

Hey All, As I watch a new test conversion take place and stare at the progress counter, I started to think, what are the best practices for member groups? From my understanding from the guides and reading around: Members will not acquire styling from secondary groups, only primary. With the above point, that means Admins and Mods should have those respective groups as primary so that they acquire staff styling. It seems that the group system will favor positive permissions (yes) over negative permissions (no or not having it) or lower in terms of wait timers (because lower is positive) On our previous software, we have for example a Supporter group that turns usernames gold, but it actually provides zero permissions (and we only wanted it for styling purposes) because the user is still primary "members" It seems that on IPS, the user should have the primary group Supporter but secondary members in this situation to accomplish the following: Primary Group Supporter (to style usernames) Don't change any supporter permissions User gets the Members group as secondary (where all the forum permissions actually are) Is this correct?

Has anyone heard from the author of this app, and it's plans for 4.7?

I did use the same details yes.

We will definitely see when it tries to run that task! Something else I noticed is that my account didn't get my avatar, or my original join date, but it gave me my PMs and posts, I'll see if anything improves when these catch up.

Currently, in attachment hell: I haven't seen it do any other ones yet. All the other dozen+ tasks are at zero since it's focusing ona ttachments.

PMs seem to be fine. However, it's also doing tasks in order, so I was just concerned is all.

19 million pm replies. That shouldn't have finished faster then anything else.

We have completed our first migration test, I'm sure we will do several more before we even attempt the live site. I've noticed the long list of background tasks that have appeared, but something stood out to me: "Rebuilding Personal Conversations" was at an instant 100 percent, should I be concerned about that?

Hi IPS, Today, I'd like to suggest that the company eventually adds the LanguageTool API into IPS Products as an optional integration in Admin > System > Integrations Here are some relevant links: Main Site: https://languagetool.org/ API Landing Page: https://languagetool.org/proofreading-api Actual API: https://languagetool.org/http-api/#/default LanguageTool is an extremely popular alternative to Grammarly and is open source, has had funding from the EU and so forth. Since the suite is often billed as a platform for businesses to provide support or long form discussion, I think there is merit in having such a thing built into the editor (with a toggle for the user to turn it off or on via their end).

Yup, they've been an alternate contact since like 2014 I think.

Awesome, I didn't know if that would pipe correctly. Neat. Thanks again!

Just to confirm, the fact that I CC'd @Ghan works fine and shows up in the ticket right?

That's why I made a feature request. I do really appreciate how much everyone has been helping us as we ask questions and get closer to our live conversion.

I saw that. Like this, try to give me the same badge twice via the back end. You cannot.

You cannot manually give a badge to someone more then once. If someone is pledged to our site on Patreon, we give them the same supporter badge once per month. I made a feature request about it like @Jim M suggested I do.