Makoto

This has been addressed in the next update which is now just pending marketplace approval!

I'll have an update to address this released soon!

I definitely consider this not working as intended too and it's something I frequently deal with.
It frustrates my customers and me personally. I can't see why anyone would want it to work this way.
You have subscription options available monthly and annually, and once someone has opted for a monthly subscription, they can never let that subscription expire and opt for an annual one instead?
That makes absolutely zero sense whatsoever. I can't think of a single platform anywhere on the internet that operates this way.
IPS, I've said this many times before, I like you guys and all, but sometimes you are way too hardheaded when it comes to addressing things none of your customers actually want.

I'll have this updated by tomorrow! It may take a few additional days for IPS to review and approve the update on the marketplace however.

Well done @Makoto for updating the plugin, Many thanks buddy.

Has a tags widget if you're interested. The widget isn't sold separately however.

I definitely consider this not working as intended too and it's something I frequently deal with.
It frustrates my customers and me personally. I can't see why anyone would want it to work this way.
You have subscription options available monthly and annually, and once someone has opted for a monthly subscription, they can never let that subscription expire and opt for an annual one instead?
That makes absolutely zero sense whatsoever. I can't think of a single platform anywhere on the internet that operates this way.
IPS, I've said this many times before, I like you guys and all, but sometimes you are way too hardheaded when it comes to addressing things none of your customers actually want.

I definitely consider this not working as intended too and it's something I frequently deal with.
It frustrates my customers and me personally. I can't see why anyone would want it to work this way.
You have subscription options available monthly and annually, and once someone has opted for a monthly subscription, they can never let that subscription expire and opt for an annual one instead?
That makes absolutely zero sense whatsoever. I can't think of a single platform anywhere on the internet that operates this way.
IPS, I've said this many times before, I like you guys and all, but sometimes you are way too hardheaded when it comes to addressing things none of your customers actually want.

This issue has now bene resolved in the latest release, which has gone out this morning.

I've pushed an update addressing this and a few more CSRF issues now!
It should be up live as soon as IPS is able to review and approve it.
Thanks as well for your patience!

Cloudflare, for example, makes this very easy to do.
Just go Security, then WAF, and from there you can set up a rule to block an entire country code from accessing your server.

 
Just be sure you've carefully considered the implications, and you are certain you really want to do this.
(You can also block TOR exit relays via the country code firewall rule)

Just confirming update has been received and fixed this problem. Thank you.

I definitely consider this not working as intended too and it's something I frequently deal with.
It frustrates my customers and me personally. I can't see why anyone would want it to work this way.
You have subscription options available monthly and annually, and once someone has opted for a monthly subscription, they can never let that subscription expire and opt for an annual one instead?
That makes absolutely zero sense whatsoever. I can't think of a single platform anywhere on the internet that operates this way.
IPS, I've said this many times before, I like you guys and all, but sometimes you are way too hardheaded when it comes to addressing things none of your customers actually want.

I definitely consider this not working as intended too and it's something I frequently deal with.
It frustrates my customers and me personally. I can't see why anyone would want it to work this way.
You have subscription options available monthly and annually, and once someone has opted for a monthly subscription, they can never let that subscription expire and opt for an annual one instead?
That makes absolutely zero sense whatsoever. I can't think of a single platform anywhere on the internet that operates this way.
IPS, I've said this many times before, I like you guys and all, but sometimes you are way too hardheaded when it comes to addressing things none of your customers actually want.

I definitely consider this not working as intended too and it's something I frequently deal with.
It frustrates my customers and me personally. I can't see why anyone would want it to work this way.
You have subscription options available monthly and annually, and once someone has opted for a monthly subscription, they can never let that subscription expire and opt for an annual one instead?
That makes absolutely zero sense whatsoever. I can't think of a single platform anywhere on the internet that operates this way.
IPS, I've said this many times before, I like you guys and all, but sometimes you are way too hardheaded when it comes to addressing things none of your customers actually want.

That’s why it never gets fixed. IPS just pretends there is no issue with excuses. The expiration isn’t the point. It’s the fact that an existing expired invoice on file blocks future purchases, which is very clearly wrong and not how ANY other subscription service on the planet is working. If I subscribe to a newspaper and cancel it, I will always be able to start FRESH in the future. Of course I am. It’s what I want, it’s what the newspaper wants. Why would the software prevent it for now reason against my will and the provider’s will? The Washington Post or Netflix aren’t saying “oh, your subscription expired 5 years ago, so you will never ever be able to start a new subscription”. That would be insane. But it is how IPS has coded it. And that it even fine in the sense, that things like that happen. It was probably an honest mistake to set it up like that originally. But it is not fine to not own up to it and correct it after admin after admin runs into this problem for years, loosing money because people willing to continue a subscription can’t and just give up.
Not letting invoices expire is a work-around at best, it’s the not the proper solution. If someone would let the subscription expire and they did not use it for years, the SHOULD be starting fresh with with any product and the current conditions, maybe even higher prices, because their subscription has expired years ago. Why should I set it so that they will forever be able to pick up the old subscription just so users don’t run into this problem of not being able to continue a subscription at all. This is objectively flawed. An expired invoice is meaningless. It should not block people from buying the product like a new subscriber. Anyone with expired subscriptions should get exactly the same offers as someone who never had a subscription to begin with. 

The issue: when someone let’s a subscription (product subscription or regular subscription) expire, they will later not be able to buy it again, because the invoice on file prevents a new subscription. But the existing subscription also cannot be renewed because the invoice has expired. This can only be solved by intervention from an admin (manually finding and deleting these invoices), but there might be hundreds of those and it would require a constant monitoring of expired invoices. 
The solution: The check that prevents a new subscription with an invoice on file should be removed or adjusted. Someone who doesn’t have a subscription anymore, because subscription and invoice have expired, must be treated like anyone who never had a subscription. Both groups should see exactly the same offers because their status in relation to these subscriptions is the same. 
Why it matters: People run into this problem all the time and it’s not just an inconvenience, it it costing them money, because people who would want to pay cannot pay and probably just give up. Here are just a few examples from the recent days (and I have observed this and commented on it for years): 
Subscription buttons don't show up. (yesterday)
Subscriptions Bug (yesterday)
invoice has expired but member cannot renew (7 days ago)
The development time to fix this is probably much cheaper than having IPS support deal with this issue for years, constantly identifying the issue and guiding people through the process of the possible work-arounds. So it would be a win-win situation to finally fix this. 😉 

Thank you for bringing this issue to our attention.
While the 1-hour expiration is intended now, I can confirm the issue with the link should be further reviewed and I've logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

A maintenance release will be available shortly to address the "null" tags issue.
I've also added a tool to clear these broken tag entries out of the database without needing to run manual sql queries.

In the latest release of IPS, password reset e-mails seem to expire after 1-hour.
If a user submits a password reset request and does not respond to the request within that hour, the first problem is the error they receive when clicking on the reset password link,

It would be much better for this error to tell them that their password reset link has expired, and provide a link to submit a new password reset request.
However, that brings us to the real problem.
When users submit another password reset request, nothing actually happens. It sends the same password reset request link to the user. It does not regenerate the password reset request in the database.
The user gets sent an expired password reset link every time they try and generate a new one.
This means that if the user does not reset their password correctly on the first attempt, it becomes impossible for them to do it until an administrator goes in and manually clears the entry out from the core_validating table.

In the latest release of IPS, password reset e-mails seem to expire after 1-hour.
If a user submits a password reset request and does not respond to the request within that hour, the first problem is the error they receive when clicking on the reset password link,

It would be much better for this error to tell them that their password reset link has expired, and provide a link to submit a new password reset request.
However, that brings us to the real problem.
When users submit another password reset request, nothing actually happens. It sends the same password reset request link to the user. It does not regenerate the password reset request in the database.
The user gets sent an expired password reset link every time they try and generate a new one.
This means that if the user does not reset their password correctly on the first attempt, it becomes impossible for them to do it until an administrator goes in and manually clears the entry out from the core_validating table.

In the latest release of IPS, password reset e-mails seem to expire after 1-hour.
If a user submits a password reset request and does not respond to the request within that hour, the first problem is the error they receive when clicking on the reset password link,

It would be much better for this error to tell them that their password reset link has expired, and provide a link to submit a new password reset request.
However, that brings us to the real problem.
When users submit another password reset request, nothing actually happens. It sends the same password reset request link to the user. It does not regenerate the password reset request in the database.
The user gets sent an expired password reset link every time they try and generate a new one.
This means that if the user does not reset their password correctly on the first attempt, it becomes impossible for them to do it until an administrator goes in and manually clears the entry out from the core_validating table.

Hey there! I'll absolutely look into this for you. Looking at the error message, there's a possibility this might be an isolated issue, so I might need you to PM me here and see if you can set me up with a temporary AdminCP account, but I'll review this either way and see if I can reproduce it locally tonight.
I'll take a look and see if this is something I can reproduce. I believe this was an error with Advanced Tags and Prefixes if you just recently upgraded from that, but I'll make sure Radical Tags is not causing any issues with RSS feeds!

There’s a 3rd-party resource to deactivate accounts:
 

If you need help setting up IPS with Nginx and PHP-FPM, this guide is a bit dated but should help,