VR6Pete

This is one of those cases where you need to be sure you are aware of what you are doing when you are self-hosting. I do not believe our software should be in the business of helping you run your server. You should have the technical know how to check your S3 bucket size and your own server's disk space before starting a file storage move.
Keeping track of server disk space or S3 bucket size is not really up to our software - that is the job of the system administrator.

Conversion to XenForo. Which, unfortunately, requires the files to be localhosted.

We've recently launched a subscriber program and a donation campaign, and it's doing kinda meh. 
Suddenly! a wild idea appeared! 
Why not have a "X people got this" or some other variant of that next to the subscription/campaign name (or below it if it's super long)?
That way all those free loading non-sub scum could see how many people there are in the community who are so much better and more generous than they are, and then feel guilty and give us their money. of course they could also see no one's buying your crappy overpriced crap and just back out of the page sinisterly laughing.
Seriously though, all the crowdfunding sites do that, and peer pressure is a genuinely good sales tool. 
Technically this should be a cakewalk because you have that info plainly displayed in the subscription page in the ACP. 

any update on this? 🙂

have done just that.

Submit a support ticket and I'll see what I can do

Any update on this? Would like to get a bulk email out today, but would be good if there was a beta version to test before I did this, if not I will just disable Bouncer whilst I perform my mail out. cheers
 
Pete

I've got 10,000 + markers, seems fine...

I haven't looked into full IPB 4.2 compatibility yet but will do as soon as I can.

second that please
but I can confirm that basic functionality appears to be working on my 4.2 install.

Will this work on ips 4.2

second that please
but I can confirm that basic functionality appears to be working on my 4.2 install.

second that please
but I can confirm that basic functionality appears to be working on my 4.2 install.

Hi  
Will the application work with the new ips 4.2.x? Thanks

That's a 4.2 issue. I'm already aware of it, and it's fixed on my dev install.

I noticed a bug when going into ACP > Groups > Members (or any group for that fact) and clicking edit;
 
ErrorException: Argument 1 passed to IPS\membermap\extensions\core\ContentRouter\_MemberMarkers::__construct() must be an instance of IPS\Member, instance of IPS\Member\Group given, called in /home/xxxx/public_html/forum/system/Application/Application.php on line 756 and defined (4096)
#0 /home/xxxx/public_html/forum/applications/membermap/extensions/core/ContentRouter/MemberMarkers.php(38): IPS\IPS::errorHandler(4096, 'Argument 1 pass...', '/home/xxxx/p...', 38, Array)
#1 /home/xxxx/public_html/forum/system/Application/Application.php(756): IPS\membermap\extensions\core\ContentRouter\_MemberMarkers->__construct(Object(IPS\Member\Group))
#2 /home/xxxx/public_html/forum/system/Application/Application.php(303): IPS\_Application->extensions('core', 'ContentRouter', true, Object(IPS\Member\Group))
#3 /home/xxxx/public_html/forum/applications/core/extensions/core/GroupForm/Content.php(36): IPS\_Application::allExtensions('core', 'ContentRouter', Object(IPS\Member\Group))
#4 /home/xxxx/public_html/forum/applications/core/modules/admin/members/groups.php(189): IPS\core\extensions\core\GroupForm\_Content->process(Object(IPS\Helpers\Form), Object(IPS\Member\Group))
#5 /home/xxxx/public_html/forum/system/Dispatcher/Controller.php(86): IPS\core\modules\admin\members\_groups->form()
#6 [internal function]: IPS\Dispatcher\_Controller->execute()
#7 /home/xxxx/public_html/forum/init.php(448) : eval()'d code(14): call_user_func_array('parent::execute', Array)
#8 /home/xxxx/public_html/forum/applications/core/modules/admin/members/groups.php(35): IPS\Dispatcher\hook781->execute()
#9 /home/xxxx/public_html/forum/system/Dispatcher/Dispatcher.php(143): IPS\core\modules\admin\members\_groups->execute()
#10 /home/xxxx/public_html/forum/admin/index.php(14): IPS\_Dispatcher->run()
#11 {main}
 

I scheduled my first weekly newsletter and received complaints that it sent every hour for up to 10 hours. Is there a log that shows this or has this happened to anyone else? I'm assuming it has something to do with the hourly task, but my settings show weekly distribution. I've disabled it and will run some checks sending to the admin group, but something went funky here. Members complained of spamming...
Maybe the issue is that the PublishNewsletters task is set to send hourly but the PruneDistributionHistory is set daily?  i also notice that after it sent the next distribution time did not change, which should have been one week from now. I manually ran the PruneDistributionHistory task but it did not change. 
EDIT:
I just noticed that my next distribution did not change to next week with the weekly interval setting. The daily and weekly intervals act the same for the next distribution time. I changed it to every two weeks in the interval setting and now the distribution time shows a week from now....funky.
So I took a look at some of the files and not sure if this is the reason or not. Looks like in  /applications/newsletters/sources/Newsletter/Newsletter.php you have the code below:
switch( $this->publish_interval ) { case static::PUBLISH_DAILY: case static::PUBLISH_WEEKLY: $day += $daysToAdd; break; case static::PUBLISH_WEEKS: $day += $daysToAdd; $day += 7; break; case static::PUBLISH_MONTHLY: $month++; break; case static::PUBLISH_ANNUALLY: $year++; break; } My choices are Daily, Weekly, Every Two Weeks, Monthly, Annually, and Manually when in settings. I seem to only be able to get a weekly +7 days by choosing Every two weeks which is your Publish_weeks in the code above?  every 2 weeks should be +14 and weekly I would imagine should be +7 like;
switch( $this->publish_interval ) { case static::PUBLISH_DAILY: case static::PUBLISH_WEEKLY: $day += $daysToAdd; $day += 7; break; case static::PUBLISH_WEEKS: $day += $daysToAdd; $day += 14; break; case static::PUBLISH_MONTHLY: $month++; break; case static::PUBLISH_ANNUALLY: $year++; break; } When I change this, it shows correctly in my "next distribution" when picking weekly. I would have the weekly with just a start date and from there +7 days send it weekly and then on the Daily, to actually pick the days of the week to send. But that's me..
If you have weekly, and pick two or more days it'll actually send in an interval that's less that a week. I think this is what happened to me. I accidentally had Friday and Saturday checked off under weekly because I was messing around with it the day before. Since the task sends every hour and the distribution time only updates once a day, it kept going even though I assumed it would only send once a week regardless.
I also think that update distribution time should be changed to hourly if the send is hourly.

Is there a way to see who unsubscribes and a total count of subscribed members as opposed to just looking at the subscribed member pages?

I can add this to my enhancement list.
I can change the default template if people think that it needs changing. What I've learned over the years though, is that no 2 people ever want the same template. So I can change it to something without bullets, but I can guarantee that someone else is not going to like what I change it to.  
Links. There is a generic template that is used for all content types. I guess I could/should do something else for gallery, though. No timeline.

I hadn't realized that for some reason. I can add it then. No timeline, though.

Thank you to @Stefan Johansson_72643 for your assistance with this issue.
A new version has been uploaded to the Marketplace. It contains a fix for this problem.

I can.  I can email and or PM an admin login
sent you a PM

@VR6Pete I use Mandrill, so it appears that this occurs with two SMTP-providers 

Yes

I will update the new version asap (1-2 days)