David..

Changing the future publish date on an already posted topic does not work. It basically just messes up the topic. Worse part is you cannot change it back apparently either without going through a database backup. I don’t see why setting a future publish date when editing an already posted topic is enabled.

I'm also noticing that once a future publish date is set, you cannot really cancel it but you can choose to publish. However, it still seems to keep the future date? If it breaks a topic like this, why even have the future publish option on past already posted topics?

I accidentally set a future published date on an old topic, and it completely moved the first post (the topic) to the most recent reply. How can this be solved?

I'd be interested in sending a donation your way if it helps speeding up the process, and adding my request of course 😋

I'm trying to make use of the Data Layer, but it's quite confusing this whole new GA4 & GTM as I'm still using the old universal analytics. From what I can tell, GTM is the best option? If yes, how exactly can it be set up to use GA4 & Data Layer together?

I am also experiencing this and emails being sent out to authors with non-solved sections.

Would be a nice option to have.

Offline indicators aren't that useful, but I think it would work if used as profile image background.

@All Astronauts could we add some more features and options? 🙂 https://i.imgur.com/Njaffrw.png I think some animations might also work!

Also it seems to be possible to enable both Questions with enable solved. Is that recommended?

Ah, I see. So is it better to have Discussions forum and enable solved? Does the Questions forum offer the email notifications?

IC announced the new support changes here: https://invisioncommunity.com/news/invision-community/finding-solutions-made-easier-r1261/ However, I do not see them on my board, everything is the same as it was. I created a new support/questions forum and then I can see the new IC changes, but not on the old questions forum. Even with all customizations disabled. I can provide an example to a moderator via PM.

Bring all options back? Perhaps add some more you may think are cool? 🙂

Is it due to IPS, or Apple/Google Pay?

When someone uses Stripe's Google/Apple Pay for purchasing, is automatic renewing an option? I do not see automatic renewals enabled on the ACP's customer view. That only appears when the user uses card details. As does the automatic renewal option during checkout.

SELECT p_id FROM `ipb__nexus_member_subscription_packages` AS `nexus_member_subscription_packages` IPS\Db\Exception: Unknown column 'p_id' in 'field list' (1054) #0 /public_html/system/Db/Select.php(388): IPS\_Db->preparedQuery() #1 /public_html/system/Db/Select.php(446): IPS\Db\_Select->runQuery() #2 [internal function]: IPS\Db\_Select->rewind() #3 /public_html/applications/nexus/sources/Fraud/Rule.php(1224): iterator_to_array() #4 /public_html/applications/nexus/sources/Fraud/Rule.php(102): IPS\nexus\Fraud\_Rule->isSubsetOf() #5 /public_html/system/Patterns/ActiveRecord.php(335): IPS\nexus\Fraud\_Rule->get__description() #6 /public_html/system/Node/Controller.php(223): IPS\Patterns\_ActiveRecord->__get() #7 /public_html/system/Node/Controller.php(113): IPS\Node\_Controller->_getRow() #8 /public_html/system/Helpers/Tree/Tree.php(130): IPS\Node\_Controller->_getRoots() #9 /public_html/system/Node/Controller.php(99): IPS\Helpers\Tree\_Tree->__toString() #10 /public_html/applications/nexus/modules/admin/payments/fraud.php(66): IPS\Node\_Controller->manage() #11 /public_html/system/Dispatcher/Controller.php(118): IPS\nexus\modules\admin\payments\_fraud->manage() #12 /public_html/system/Node/Controller.php(69): IPS\Dispatcher\_Controller->execute() #13 /public_html/applications/nexus/modules/admin/payments/fraud.php(54): IPS\Node\_Controller->execute() #14 /public_html/applications/nexus/modules/admin/payments/paymentsettings.php(81): IPS\nexus\modules\admin\payments\_fraud->execute() #15 /public_html/system/Dispatcher/Controller.php(118): IPS\nexus\modules\admin\payments\_paymentsettings->__call() #16 /public_html/system/Dispatcher/Dispatcher.php(153): IPS\Dispatcher\_Controller->execute() #17 /public_html/Prevail/index.php(13): IPS\_Dispatcher->run() #18 {main} Does anyone else have the same issue?

Sounds good! I would like to see the option to apply limitations to new topics and new posts to the same group. Thank you for the awesome work.

Adding different limits for new topics and different limits for new posts. For example when creating a new support topic, we want to add a 15 minimum word count so people hopefully add additional information so that we could better assist.

@Nathan Explosion Is it possible to add different limitations per posts & per first posts (topics) content?

How do I stop the login failed emails? Community is sending out too many of them and it's scaring people Or, how do I better protect the login page as people seem to be trying to hack logins

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue. Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use. 4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option. It was a very convenient way of playing around with (a copy of) your theme.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to. CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support. Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

Since you mentioned the above, I am unsure why those options are not selected. I have not changed any settings there, and they should be made mandatory if it causes issues. Regardless: Selecting "Ask the user to provide a display name" still skips the display name requirement when signing up/in via OAuth. Selecting "Google account name" automatically uses the Google account's name when registering via OAuth so that at least solves the incomplete account problem. The same issue seems to happen with Twitter sign in too. If we make the user enter a display name when creating a new account in the OAuth login, then the display name is never asked for and just gets redirected back to the OAuth site/app.

That I cannot do. You can restore the original during testing, but after that I am forced to modify them again. If you're unable to do that, then I will have to work with a 3rd party on resolving this issue.

I also attempted restoring the modified files, even though the modifications are minimal, the issue was still present. I recorded a video with the issue as I have to restore the modifications after testing. The modified contents are as follows. They should not interfere with the sign up flow: /oauth/authorize/index.php - Comment out 93-98 & 100 if ( $redirectUri ) { //if ( !\in_array( $redirectUri, $allowedRedirectUris ) ) //{ // throw new \IPS\Login\Handler\OAuth2\InitException('oauth_err_invalid_redirect_uri'); //} //else //{ $obj->redirectUri = \IPS\Http\Url::external( $redirectUri ); //} } /oauth/token/index.php 312 - 316 /* Check we are not IP banned */ //$ipBanned = \IPS\Request::i()->ipAddressIsBanned(); //if ( $ipBanned ) //{ // throw new \IPS\Login\Handler\OAuth2\Exception( 'invalid_client', "IP Address banned" ); //} /system/Dispatcher/Api.php comment out line 74 /* Check our IP address isn't banned */ //$this->_checkIpAddressIsAllowed();