sound

reported this a couple of years ago
last time checked was still an issue
 

Would it not help the discussion if the discussion was split into admin use of the editor and the normal member use?
i certainly have different needs/requirements of the new editor as an admin, espically on the cms article editor side than say a member posting normal forum topics
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

have you tried using the delete/move content post options that shows when you click on a forum in the acp
For content that matches all of the following conditions...
admin/?app=forums&module=forums&controller=forums&do=massManageContent&id=1
without knowing your setup not sure if it helps
but if your 'guest' posts are filterable - you could then move then to a temp forum then delete all when checked ?

Source Mode uses:
Custom embed of videos that are custom sizes, like Vimeo 21:9 or whatever ratio we wish to use - doesn't work properly without source mode. HTML code clean-up in Pages (as already mentioned). Embedding Sketchfab 3D models or other 3rd party materials (e.g. Custom Google Map embedding), the use of  source mode for adding specific code for custom settings. So many uses for source mode.
Not having it I consider a serious omission. More important than having a sticky toolbar.

Source mode was typically used in my case for iframe embeds from our podcast host to have the latest episodes show up within a post.

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

as admin use it for the below
to embed cms blocks via the 'external embed' method
to embed 3rd party website embeds/iframes
not just for forum posts but for nearly all content items such as articles, events etc
 

This would be correct. They arent an item which is stated by any of the 2 purge options

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Users do not always understand the difference. They mark emails as spam because it is easier and faster in comparison to unsubscribe. 
Amazon SES allows you to have 10% of bounces before your account is at risk. But it allows only 0.5% of spam complaints before you've got issues with them. The account reputation is not so much about invalid mails, but about valid emails that have marked you as spam.
You can clean your database from invalid emails. But there is no service to clean users who have marked your emails as spam. Unsubscribing with one click could at least lower the complaint rate. 😉 

just checking in to see if any news about the future of this most useful app as the marketplace is now closed and version 5 is due out soonish?
 
 

just checking in to see if any news about the future of this most useful app as the marketplace is now closed and version 5 is due out soonish?
 
 

nope
can't do full path as the acp link depends on the database name/id
so just use the link titled 'databases name' Fields
then click on a field and you will see a field with the text underneath
This setting controls whether the field will be included in the automatically generated topic, and how to format it. Use {title} for field title, and {value} for field value. Leave empty to not include in the automatically generated topic.
more  info and   a screenshot  here may help
 
 

...

I confess to myself - I have forgotten this topic... But there is one accidental, or not quite solution that I have found.
And here I am sharing it with you.
Open the Include CSS template
Find it
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='stylesheet' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' media='all'> {{endforeach}} {{if \IPS\Dispatcher::i()->controllerLocation == 'front'}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='stylesheet' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' media='all'> {{endforeach}} {{endif}}
And replace code with
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload stylesheet' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' as="style" media='all'> {{endforeach}} {{if \IPS\Dispatcher::i()->controllerLocation == 'front'}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='preload stylesheet' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' as="style" media='all'> {{endforeach}} {{endif}}
You will eliminate render blоcking CSS without much effort...
Of course, there are other little (hard to do) tricks for even better performance, but the above will also make you smile…

reported here 3 weeks ago