Daniel F

This seems to be an issue with your telegram notifications 3rd party file!
#0 /var/www/..../applications/core/extensions/core/Notifications/Content.php(457): IPS\_Content::loadAndCheckPerms(137048) #1 /var/www/.../applications/telegram/sources/TelegramNotification/TelegramNotification.php(241): IPS\core\extensions\core\Notifications\_Content->parse_new_comment(Object(IPS\telegram\TelegramNotification), true) I would suggest to disable it and then to try to run the queue task again and if it then continues, please contact the author and make him aware of the issue.

I have fixed this for you:) 
This was caused by a very old bug which was fixed in the meanwhile, but unfortunatly you were still affected by this because you were still running 4.4.x !

Hi,
you can set the visibility while editing the field in your ACP.

That's correct, we have changed this for security reasons, I'm just not sure why we have kept the condition and the 3 langstrings instead of returning only one generic error message in all cases:D 

Usually you’ll prepare and format the text before you send it to the community which then creates the item as it is.
I agree that it’s not optimal. We’ll discuss this internally, because I guess we could/should make this optional. 
 

This seems to be a system configuration issue, where your community isn't able to connect successful to your MySQL server.
I would suggest to contact your webhost for further assistance.

You'll have to truncate following database tables:
core_tags core_tags_cache core_tags_perms core_search_index_tags But please create a DB backup before you run this;)

It seems that there's an issue with one of the fields on the "Content" Tab. Switch the tab to see the highlighted field and it's error.

My guess is the forms app because following hook is being mentioned in the error stack form_hook_formRegisterController

I'm really sorry for the confusion here.
@Jim M just shared some further details with me and it looks like a legit issue, which I have logged to our bug tracker.

That’s the IP. Download app in combination with commerce.
You’ll also need commerce if you want to allow your members to sell the items.

I'm working on the nightowl ticket right now.
 
Edit: It's an issue with the "neviewpasswordonstandardlogin" plugin

It’s available while editing a forum.
 

This was patched today. Please visit your ACP-System section and follow the instructions to apply the patch.

We have moved this to the integrations section. ( ACP-System-Integrations )

IMO it's fine to show it while editing, I mean what if it was created anonymous by accident or if something shouldn't be anonymous anymore, but I would prefer if it would be an extra setting or a moderator permission to control who's able to toggle the anonymous flag while editing existing content.
 
That said, I have brought this up internally.

Thanks.
This should be fixed in our November release:) 

Apologies, this was the wrong code.
 
That's the correct one:
{{if \IPS\Dispatcher::i()->application->directory == 'blog'}} Your code to show only inside blogs {{endif}}  

This means the internal IPS Advertisement System ( https://invisioncommunity.com/4guides/monetization/internal-advertising-r57/ )
 

Set the type to "Other/Manual" and then use following code:
<?php $options = ['fa-angle-up' => '<i class="fa fa-angle-up"></i>', 'fa-chevron-up' => '<i class="fa fa-chevron-up"></i>', 'fa-window-close' => '<i class="fa fa-window-close"></i>']; return new \IPS\Helpers\Form\Radio("core_theme_setting_title_{$row['sc_id']}", $value, FALSE, array( 'options' => $options, 'parse' => "raw" ), NULL, NULL, NULL, 'theme_setting_' . $row['sc_key']); Result:


 
You could also use the IPS\Helpers\Form\Custom form field type which allows you to literally customize the whole output...
 
 

Zapier should show all available variables once you click into the editor

 

Check your menu manager in the ACP and make sure that the " My Activity Streams Menu" is placed in your menu! 

That's a per ad setting appearing on the form while creating/editing the advertisement under ACP => System => Advertisements.
 

Please make sure that all your dev files are up2date!
 
And if they are, make sure that none of your 3rd party apps/plugins is accessing the deprecated IPS\Application::$ipsApps variable, which was mentioned here: