-
I've been working in the computer industry for over 20 years, doing everything from Technical Writing, Project & Product Management, Web Development, and Programming. Over the years I have worked extensively with a variety of database platforms and on multiple Operating Systems. Despite the "Project Manager" title, I've always been hands-on, often taking on some of the more complex projects. In early 2010, I made the jump to full-fledged Developer, working in Java and C#.NET. I got involved with IPB in 2007, when a friend of mine started his own site and was looking for a programmer. I taught myself PHP and IPB, and by early 2008 I started accepting requests for custom modifications. In May 2010, I quit my job and moved full-time into consulting, with the majority of my work being IPB-related. All of my clients are long-term projects, some of them corporate. My clients look to me not only for development, but because I also have product management experience, I can often help them take a basic, not yet fully-formed idea and expand it into an actual application or project. I have worked with every IPS component available, as well as developed many custom applications. Please note that: I do not do any design work. Please do not contact me for theme design, I am not the right resource for that. I am primarily interested in long-term, ongoing projects. I prefer to build a relationship with my clients, rather than delivering a single plugin and walking away. -
We do get notified, with (almost always) plenty of time to update. It's just that some of us have a large number of marketplace resources and so those resources may not be updated the very second that a release is available. Additionally, each update has to go through a review before it's available. In most cases, the monthly releases don't break the marketplace resources. You should only (potentially) have issues when upgrading to a bigger release (e.g. 4.6 -> 4.7), at which point you should reach out to the plugin developer to check compatibility.
-
A fix has been pushed to the Marketplace and is pending approval.
-
Cycle here is more of a batch size. You can probably leave this as the default. It's how many emails get sent at a time. This is because some mail servers will scream at you if you try to send out 1,000 emails in a short period of time. Breaking it down into batches with a delay helps. So instead of sending 1,000 emails in the space of 2 minutes, for example, it will send 100 emails, wait 10 minutes, then send another 100, wait 10 minutes, etc. Hope that clears things up.
-
A new version has been pushed to the Marketplace and is pending approval. Changes include: Allow Admins to view a list of users who have unsubscribed from the Newsletter (ACP -> Newsletters -> Subscribers -> Unsubscribed Members ) Allow Admins to export a list of users subscribed to a newsletter Multiple improvements to distribution tracking to prevent loops and users receiving multiple instances of the newsletter Moved population of the distribution list to a background task to prevent timeouts on large sites
-
In what way is it not working?
-
OK. Feel free to PM me directly if you still have issues. As you can see I don't always get the notifications for these threads.
-
What are you using for sending email?
-
I'm honestly not sure how to correct that. It's something you'd have to ask IPS. I mean... there is no update for me to push, so I don't know how I can handle it from my end.
-
Just pushed a new version to the Marketplace, it fixes this issue. Possibly, but not any time in the next couple of weeks. I'm swamped.
-
The file referenced in the screenshot does not exist. You may need to manually delete it from your server... but it's definitely not part of the distribution, not for quite some time.
-
A new version has been pushed to the marketplace and is pending approval. Changes include: Issue where plain-text newsletters were not distributed correctly. Fixed. Exception when sending a test newsletter. Fixed.
-
I've removed the offending file completely and submitted a new version to the marketplace. That said, the original point still stands. If a hook is extending a non-existent file, it still should not be flagged.
-
OR..... that it was done to be compatible with another one of my custom apps, which is Sparkpost integration. 😉 I'd argue that this should be allowed, since we very often have to integrate with other 3rd party apps.
-
Just double checked, latest version is definitely correct.
