TSP

Hello, 
Sorry for the lack of updates. I have a lot to do at the moment, but I'll try to make something happen here this week. I'm sorry for the inconvenience. 

Hello, 
Sorry for the lack of updates. I have a lot to do at the moment, but I'll try to make something happen here this week. I'm sorry for the inconvenience. 

Jeg har oppdatert språkpakken for å løse problemet som ble nevnt og oversette noe mer tekst som har blitt lagt til.

Why is this not possible already? We can merge topics, close them, sticky them, delete them - but there is no way to choose topics from a result set when searching and move them to another category. There really should be a way to do this from a result set that contains topics.

It would really speed up the process of moving topics when new forums are created.

Why is this not possible already? We can merge topics, close them, sticky them, delete them - but there is no way to choose topics from a result set when searching and move them to another category. There really should be a way to do this from a result set that contains topics.

It would really speed up the process of moving topics when new forums are created.

You'll be presented with queries against tables that have x number of rows. You'll also be able to set another x value in your constants.php. 
I can't remember name of constant currently, but take alook in init.php and you'll find it. Either way I would say it's always advisable with test upgrades, especially with forums at your size.

Why is this not possible already? We can merge topics, close them, sticky them, delete them - but there is no way to choose topics from a result set when searching and move them to another category. There really should be a way to do this from a result set that contains topics.

It would really speed up the process of moving topics when new forums are created.

When you have Elasticsearch enabled we do not maintain the local MySQL search index to save on overhead.

If you have enough data to make Elasticsearch worthwhile, it stands to reason you can fix whatever the issue is with ES in the amount of time it's going to take to rebuild the search index locally. Either way, your users aren't going to have accurate activity streams immediately. I'd focus the effort on restoring service to your elasticsearch instance. 

Hello, 
There is no indication in the mobile menu on which account you're logged into. There is no profile image or member name. 
I suggest that you add the member name to the Sign Out-button, so it'll say for example: Sign Out TSP
Alternatively you could have a small line at the top of the mobile user menu with the avatar and user name next to it, above the sign out-button or the message/notification/report-icons.
Thanks for considering this small change that I feel will improve the mobile user experience.

Jeg har oppdatert språkpakken for å løse problemet som ble nevnt og oversette noe mer tekst som har blitt lagt til.

JsonLD data was restored in 4.2.4 beta 2, I'm also seeing it working in communities that have been upgraded to Beta 2.

I see it's still not back in 4.2.4 pre-release. 
Could someone from IPS give us an idea on when it's coming back? 

I see it's still not back in 4.2.4 pre-release. 
Could someone from IPS give us an idea on when it's coming back? 

Hello, 
There is no indication in the mobile menu on which account you're logged into. There is no profile image or member name. 
I suggest that you add the member name to the Sign Out-button, so it'll say for example: Sign Out TSP
Alternatively you could have a small line at the top of the mobile user menu with the avatar and user name next to it, above the sign out-button or the message/notification/report-icons.
Thanks for considering this small change that I feel will improve the mobile user experience.

Hello, 
There is no indication in the mobile menu on which account you're logged into. There is no profile image or member name. 
I suggest that you add the member name to the Sign Out-button, so it'll say for example: Sign Out TSP
Alternatively you could have a small line at the top of the mobile user menu with the avatar and user name next to it, above the sign out-button or the message/notification/report-icons.
Thanks for considering this small change that I feel will improve the mobile user experience.

Hello, 
There is no indication in the mobile menu on which account you're logged into. There is no profile image or member name. 
I suggest that you add the member name to the Sign Out-button, so it'll say for example: Sign Out TSP
Alternatively you could have a small line at the top of the mobile user menu with the avatar and user name next to it, above the sign out-button or the message/notification/report-icons.
Thanks for considering this small change that I feel will improve the mobile user experience.

Hello, 
There is no indication in the mobile menu on which account you're logged into. There is no profile image or member name. 
I suggest that you add the member name to the Sign Out-button, so it'll say for example: Sign Out TSP
Alternatively you could have a small line at the top of the mobile user menu with the avatar and user name next to it, above the sign out-button or the message/notification/report-icons.
Thanks for considering this small change that I feel will improve the mobile user experience.

Jeg har nå oppdatert språkpakken for 4.2. Se: https://invisioncommunity.com/files/file/7383-norwegian-norsk-bokmål-for-all-ips-apps-except-commerce/
 
 

We are exploring possibilities as Lindy said, including implementing more event-based triggers (which we do in some places already, such as MemberSync extensions) and looking into adjusting the hooking system to allow it to work with traits as well. As Lindy said, we will update everyone with more information in due course.
 

This is being discussed with development, I just wanted to let you know we're not ignoring it. One proposed solution moving forward is to incorporate our own event trigger system - for example, when a reaction is provided, send a "reactionGiven" event that you can then work with. This allows you extendability without us needing to get hacky. 
Once the core devs have given more insight, I'll update this so we're all on the same page. 

You allows to extend the moderator form (in my case, from FORUMS app) to add new permissions:

But you "hardcode" the moderator permissions on templates (for all apps, AFAIK). Example for FORUMS:
{{if $topic->canPin() or $topic->canUnpin() or $topic->canFeature() or $topic->canUnfeature() or $topic->canHide() or $topic->canUnhide() or $topic->canMove() or $topic->canLock() or $topic->canUnlock() or $topic->canDelete() or $topic->availableSavedActions() or $topic->canMerge() or $topic->canUnarchive() or \IPS\Member::loggedIn()->modPermission('can_view_moderation_log')}} <li> <a href='#elTopicActions_menu' id='elTopicActions' class='ipsButton ipsButton_link ipsButton_medium ipsButton_fullWidth' data-ipsMenu>{lang="moderator_actions"} <i class='fa fa-caret-down'></i></a> <ul id='elTopicActions_menu' class='ipsMenu ipsMenu_auto ipsHide'> So, unless the moderator has any of mod permissions above, it won't display the new permission in the Moderation Actions select:
 

Had the same problem myself a while ago. Since there was already a topic about it I didn't post another new one though.

HI Brandon. Fell again on this today in a plugin.
Any idea if and when will be implemented?

The problem is that "next year" also goes until december.