The Dark Wizard

4 hours ago, Jim M said:

Have all background tasks completed? There are rebuilds which would process these items.

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:

3 minutes ago, Jim M said:

I've tagged a developer to confirm if that should work here or not. Someone will be with you shortly.

Thank you.

11 minutes ago, Jim M said:

What version of Invision Community are you running?

Invision Community v4.7.0

1 minute ago, Jim M said:

Search index is responsible for those. You'll want to ensure all that gets rebuilt as there's a lot of rebuilding there.

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.

1 minute ago, Marc Stridgen said:

There isnt really any 'best practice' for this, as its unique to the individual site. 

Your suggestion on how to set it sounds fine, however only if there is a situation where 'supporter' doesnt have any member permissions. If it's the case that every supporter gets the permissions of the member group, then you might as well set permissions on the supporter group

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.

17 minutes ago, opentype said:

It should work, but you will still have to deal with two permission sets which can potentially be conflicting. “Don’t change any supporter permission” doesn’t mean that the primary group permissions don’t affect anything. There is no way to turn the permissions off. 
It’s probably easier to just have two primary groups. Create the second by copying the first. And if you ever want to make changes, apply them to both. 

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?

4 hours ago, Jim M said:

Did you create your Invision Community admin account with the same details as your account from your converted forum? If so, that is intended. The system will do it's best to merge accounts that exist already. However, will keep existing items in place like join date, profile photo, etc.. but add in new data like posts, messages, etc...

I did use the same details yes.

4 minutes ago, Randy Calvert said:

It will eventually hop over to something else for a bit.  I've given up trying to figure it out to be honest.  

(By the way, the other thing I've seen is that even when the dashboard says "100%", it is not quite there.  It' rounded up and has a couple left until it actually disappears.  Once the item actually disappears, you know it's really finished.  🙂 

4 minutes ago, teraßyte said:

It does tasks depending on the priority (from 1 to 5). If attachments has a higher priority than anything else it will do only that first.

As for the 100% on PMs, given how many you have I doubt it has already rebuilt them only. Most likely a bug in how the complete % is calculated.

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.

1 minute ago, Randy Calvert said:

It actually does not do every task in order.  It rotates through small amounts of each based on my past experience.  

For example, it might do 200 posts, then some topics, etc.  If you run the tasks manually you'll see what I mean how it will do some of each.  🙂 

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.

1 minute ago, Randy Calvert said:

Well, you'll be able to find out how things went by looking at your PMs.  😄

There just may not be much to do with it and the job could blow through it quickly.  

PMs seem to be fine.

However, it's also doing tasks in order, so I was just concerned is all.

1 minute ago, Randy Calvert said:

If your users have not sent a lot of PMs, it won't take long at all for it to rebuild.  There's a TON of things rebuilding...  some complete super fast and others will drag on for infinity.  🙂

I pulled up another tab and ran the task queue manually while I worked in other windows to help make me feel better about everything finishing faster.  lol

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).

Just now, Marc Stridgen said:

Yup. Note if they are to be responding, ensure they are set up as an alternative contact on your account too. If you are unsure how to do this, please take a look at the guide here

 

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

Just now, Marc Stridgen said:

Yes they are indeed replying to the ticket

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

Thanks again!

5 hours ago, Marc Stridgen said:

I have now created a ticket for you on this

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

9 minutes ago, Marc Stridgen said:

You cannot via the back end, no. It has to be via content

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.

47 minutes ago, Marc Stridgen said:

Are you referring to on the same item of content? I have actually given you the same badge on 2 occasions here, just to illustrate

I saw that.

21 hours ago, Nathan Explosion said:

Front-end, multiples can be awarded:

Via the ACP - click 'Manage'

Then click 'Add badge':

And you can then give them any of the badges you have set as 'Manually awardable'

 

The above method via the ACP would meet your initial request if your feature suggestion got implemented (no need to dig around and find a post made by the user then)

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

4 hours ago, Marc Stridgen said:

Im a little confused as to what you mean here. That is already the case, via "reward "as mentioned above

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.