Runar

Give me a few days and I’ll make a free plugin for you.

I’m having the same issue, and I’ve traced it to this function on line 4353 in system/Content/Controller.php:
protected function sendModerationAlert( array $values, \IPS\Content\Item|\IPS\Content\Comment $content ) : \IPS\core\Alerts\Alert { } More specifically, the second argument, the union types, causes issues for the editForm function in system/Plugin/Hook.php. On line 370, the editForm function loops through parameters and tries to get their types and names:
$parameters[] = ( $parameter->getType() ? ( ( ( $parameter->allowsNull() ) ? '?' : '' ). '\\' . $parameter->getType()->getName() . ' ' ) : '' ) . ( $parameter->isPassedByReference() ? '&' : '' ) . '$' . $parameter->name . ( $parameter->isOptional() ? ( '=' . var_export( $parameter->getDefaultValue(), TRUE ) ) : '' ); This works with single types, but not with union types.
A single type returns a ReflectionNamedType, while union types return ReflectionUnionType, and trying to call getName() on a ReflectionUnionType will not work. I assume a simple check for ReflectionUnionType inside the try block would solve the issue.
As far as I can tell, this issue affects all hooks to \IPS\Content\Controller and every class extending that class.
For the record, I’m using PHP 8.1.16.

So, it's official: it is my ISP.  I downloaded a VPN to test out, and it let me back in.  Something in my ISP got the site blocked.  Thanks to all, especially @Runar, for the help!

If you're so good, you should have known and offered to help. 🤪

This is the support topic for the plugin Login Page Message.

Thank you for the error details, I’m working on this.

I’m not dead! I’ve read all replies made the last few days, and I’ll post a longer update later this week.
But to summarize: An update to make the app compatible with the latest Invision version will be submitted for approval this weekend. Bugfixes and new features will follow later.
I’m also considering open sourcing this application and my other plugins (most are already open source), allowing anyone to make their own changes, but there’s some license stuff that must be taken into consideration. For instance, it will not be possible for anyone using my code to commercialize it, meaning any changes will have to be released for free. Also, at this time I’m not considering passing the application on to any other developer.

Thank you for the error details, I’m working on this.

Thank you for the error details, I’m working on this.

Thank you for the error details, I’m working on this.

Thank you for the error details, I’m working on this.

I’m not dead! I’ve read all replies made the last few days, and I’ll post a longer update later this week.
But to summarize: An update to make the app compatible with the latest Invision version will be submitted for approval this weekend. Bugfixes and new features will follow later.
I’m also considering open sourcing this application and my other plugins (most are already open source), allowing anyone to make their own changes, but there’s some license stuff that must be taken into consideration. For instance, it will not be possible for anyone using my code to commercialize it, meaning any changes will have to be released for free. Also, at this time I’m not considering passing the application on to any other developer.

I’m not dead! I’ve read all replies made the last few days, and I’ll post a longer update later this week.
But to summarize: An update to make the app compatible with the latest Invision version will be submitted for approval this weekend. Bugfixes and new features will follow later.
I’m also considering open sourcing this application and my other plugins (most are already open source), allowing anyone to make their own changes, but there’s some license stuff that must be taken into consideration. For instance, it will not be possible for anyone using my code to commercialize it, meaning any changes will have to be released for free. Also, at this time I’m not considering passing the application on to any other developer.

I’m not dead! I’ve read all replies made the last few days, and I’ll post a longer update later this week.
But to summarize: An update to make the app compatible with the latest Invision version will be submitted for approval this weekend. Bugfixes and new features will follow later.
I’m also considering open sourcing this application and my other plugins (most are already open source), allowing anyone to make their own changes, but there’s some license stuff that must be taken into consideration. For instance, it will not be possible for anyone using my code to commercialize it, meaning any changes will have to be released for free. Also, at this time I’m not considering passing the application on to any other developer.

It seems that the date of the last change made to the file description, is being called three different things (the three red circles):

Edited, Released, and Updated all show the same date. Is this intended? Nevertheless, it’s confusing. I can understand the Edited date below the description, but something should be done about the others.
In my opinion, the Published (orange circle in the sidebar) and Released (above the changelog) dates should show the same date. The current version of the application in the screenshot was published on December 31, so that date should be shown in the changelog as well as in the sidebar.
Finally, a date is missing where the purple circle is located. Here, the Published date should be displayed. Currently, no date is shown here until the next version is published, and then the date is wrong (see first post).

It seems that the date of the last change made to the file description, is being called three different things (the three red circles):

Edited, Released, and Updated all show the same date. Is this intended? Nevertheless, it’s confusing. I can understand the Edited date below the description, but something should be done about the others.
In my opinion, the Published (orange circle in the sidebar) and Released (above the changelog) dates should show the same date. The current version of the application in the screenshot was published on December 31, so that date should be shown in the changelog as well as in the sidebar.
Finally, a date is missing where the purple circle is located. Here, the Published date should be displayed. Currently, no date is shown here until the next version is published, and then the date is wrong (see first post).

I was sure I had reported this earlier, but I can’t find any similar topics.
In the Marketplace, the release dates of the different file versions are wrong. It seems the release date is set to the date of the next version uploaded: If version 1.0.0 is uploaded on January 1, the “See changelog” dropdown displays no release date. When version 1.0.1 is released February 1, version 1.0.0 is suddenly showing a release of February 1.
See this picture for an example:

The list of versions show version 2.0.0 as released December 27. This is wrong, as this version was released in March. December 27 is the date I submitted the new version (2.0.1).
Also, the December 31 date displayed below “What’s New in Version 2.0.1” is the date the new file was approved.
 

Thank you for asking! These are the ones I've found the last weeks:
https://invisioncommunity.com/developers/docs/general/autoloading-classes-r6/

General issue: Something is wrong with the text styling on this page.
  https://invisioncommunity.com/developers/docs/general/caching-r8/

General issue: The section "The caching layer" references several old and no longer supported caching methods, such as ACP and Xcache.
  https://invisioncommunity.com/developers/docs/development/plugins/complete-example-of-a-plugin-in-ips-community-suite-r50/

The section "Step 5: Making Database Changes" makes several references to altering the core_members table. There is a warning at the top of the section, but the examples and text further down need to be updated.
  https://invisioncommunity.com/developers/docs/development/applications/versions-and-upgrading-your-application-r51/

References adding a column to the core_groups table.
  https://invisioncommunity.com/developers/docs/development/extensions/coregroupform-r140/

References adding a column to the core_groups table.

As I wrote in the other topic, I’ve identified the issue and will submit a new version shortly. In the meantime, please disable the plugin. You might have to manually edit some posts, so hopefully not too many posts were made.

I’m replying to your post but my reply is meant to everyone here. I’m available and I’m reading all of your posts, and the next version is in progress, but I needed to prioritize real life during the last weeks. The next version will most likely be released around Easter, I won’t promise it’ll be ready any earlier.
But I haven’t forgotten about you all, so all I ask is your patience and understanding.

@Runar thank you for your app, it works as exactly as advertised.. love it! 🙂
 

Hi Invision,
In IPS.Commerce 4.6.10, there is an issue with account credits and invoice payments with Stripe.
Stripe indeed refuses card payments under $0.50:
https://stripe.com/docs/currencies#minimum-and-maximum-charge-amounts
However, it turns out that members can end up with an invoice to pay less than this amount of $0.50, when they have an account credit.
There are 2 issues in IPS.Commerce concerning this limitation:
 
1st situation: with generateRenewalInvoices
Let's take an example of a member who has an account credit of $9.60, and a $10 / month subscription.
During the generateRenewalInvoices task:
IPS.Commerce will first make a successful transaction of $9.60 with the account credit.
  IPS.Commerce will then try to make a Stripe transaction of $0.40.
  Stripe will refuse this transaction, as it's below $0.50.
  Then IPS.Commerce gets stuck: the invoice remains unpaid, and there is nothing we can do.  
The solution would be to use the account credit only up to this $0.50 limit, so that the transaction amount does not go below it.
 
2nd situation: with manual payment

Another scenario is the following:
A member has an account credit of € 7.00
  An admin generates a renewal invoice in the ACP for € 7.20
  When the member tries to manually pay this invoice, he can choose to pay with his account credit:
 
The transaction with the account credit is then successful:  

 
By returning to the checkout page, there is a 4X196/3 error:  

 
This issue comes from /nexus/modules/front/checkout.php at line 1337: there is no available payment method, as the Stripe gateway checkValidity() method returned false.
Again, we are stuck as this invoice cannot be paid.
Thank you!

No, you’ll be given the choice to make everyone accept the new policy or not, so you can easily just fix the spelling mistake. This also applies to the guidelines.