sound

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
 

reported here 3 weeks ago
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

no forum images
happens on up to date chrome browser
just resize the window to tablet size to see it 

Also $priceDetails['initialTerm'] call in the 'package' template seemed to cause a similar effect/error - needed to get rid of  that as well
  <div><span data-role="initialTerm">{lang="package_initial_term_title" sprintf="$priceDetails['initialTerm']"}</span></div>

I had the same error using a 'new' generated theme
I temporary resolved it by removing
    <span>{lang="package_initial_term" sprintf="$details['initialTerm']"}</span><br>
in the  packageBlockPrice template - there are just two instances of this call in whole theme
I'd say a possible commerce bug that needs fixing/investigating ?

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Another tutorial 
https://medium.com/oke-software/create-apps-for-ips-2-customizations-9510d32a5a53

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

Anyone at invision explain the thinking behind these two sets of statements...
 
Commerce Deprecation
Commerce Help Feature - Now, there are many email support desk solutions that are a significant improvement on what Commerce offers...
...we made the decision to deprecate the support desk feature
Commerce Sales Feature -  ...physical product sales have now been deprecated and are much better handled by specialist services such as Shopify.
versus
New Courses and Lessons Feature
The Courses app is not going to try to be a full LMS. Not trying to run a university here 🙂
 
As I see it invision are...
Getting rid of 2 features (that I use heavily) with the reason being you can get better commercial versions elsewhere
Whilst adding one new feature (that I have no use for) even though you can get better commercial versions elsewhere
All a bit conflicting to me
Plus while here, may as well ask, will the cost of commerce go down now as it will be a lesser product for self hosted packages?
 
 
 

We expect this limitation to be removed in our April release.
We have merged two different concepts into one. We previously had "Publish Date" in pages, but "Future Publish Date" everywhere else.
Merging them did cause some issues which we've been resolving. The final one was when you have Pages records (any publish date) synchronised with a forum (only future publish date).