TDBF

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

The obligatory developer testing code..... because Xdebug isn't good enough! 🤣

Cheers 👍

I have a license that I paid full price for a while back. I stopped renewing it because I never used it. I thought I was going to use it for something but it turns out I didn’t end up using the software for anything. I paid renewals for about a year or two but the software just say there not ever one time being used. It didn’t make sense for me to keep renewing it. 
 
However, I like to think that if I ever figure out a use for this software, then I have already paid for it more than a few times over. It should be there for me to use and start paying renewals again.
 
I hate to think that I would have to pay full price for it all over again. 😣
 

 
 

"We have lots of statistics, no one uses it, it has been discontinued..".  🙂

Never mind, I had not enabled HTML for selected users.
Sorted now.

You don't need to use FileZila for this.
You should have phpMyAdmin in your CPanel.
Look for the core_members table, and on your admin account which is locked, scroll along for 'failed_logins' and delete the contents in that field and then set 'failed_login_count' to 0.
You can then use the forgot password tool to get a new password and be able to sign in.

It is, yes
twitter.com has a different oembed endpoint to x.com, hence the fix in 4.7.13 to account for it.

With the Marketplace EOL and providers switching to or relying on their IPS sites, it's really not the time to also be losing the built-in Support Ticket system. Providers will need it more now than before and all the third-party offerings are not free after trials end, require additional sharing of client data and require integration. The integrated system with Commerce is so convenient and with the planned Commerce improvements even more so.
Please can you consider a stay of execution or perhaps even simplify it to make it less timely for IPS to maintain?
Thank you.

Looking at those logs you have several crashed tables that need to be repaired.
In addition I also see that you're using MySQL 8.0 and I've seen a few people having issues with it. It would be best to use MySQL 5.7 or an equivalent MariaDB version instead.

I assume we would handle this just like we did for v3, v4.0, v4.1, etc. that have reached end of life. We generally give people a LOT of warning and then finally pick a date way in the future that they have to upgrade. We're talking years though. I am afraid I do not have a clear answer to give you on such specifics that are many years away 🙂 
As end of life approaches, you will get a lot more information on how to handle the upgrade. And, of course, by 2025 or 2026, v5 itself will be more mature. We might even be on v6 by then, who knows!

Unless this is a distributed application, not running in CiC, just make an executable file that you run with crontab at 5:00. 

Not by default imo. That will require custom coding.

Here's what I would do based on the currently available functionality.
Set the task to run every minute In your execute(), check if the time is 5pm If it is then proceed with the rest of the code If not, then do nothing.  

Users would need to use the Forgot Password function to set a password and would need to know the email address they used with the linked login method. So you could or should explain that somewhere and inform your users before making the switch. 

Been doing that for quite a while across all my communities. 

Hello,
If I remember well, you should be able to edit questions and answers but not delete them, as people already played.
Isn't the EDIT link showing up?
 
----------------------
EDIT: Just tested and it doesn't show. I'll update the file with a fix.

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Invision: 4.7.10
PHP 8.0
While in development mode and with Whoops enabled, any error from a widget will result in a loop while writing the error to the database, and cause the server to time out and crash.
For example: (This is an example just to trigger an error and not a real world example)
/** * Render a widget * * @return string */ public function render() { $lastFixture = NULL; $$nextFixture = NULL; return $this->output( $lastFixture, $nextFixture ); }
From the error log:
🙂

Full in-depth developer documentation with proper real-life full working examples on how to implement framework features.

Full in-depth developer documentation with proper real-life full working examples on how to implement framework features.

Full in-depth developer documentation with proper real-life full working examples on how to implement framework features.

Full in-depth developer documentation with proper real-life full working examples on how to implement framework features.

Full in-depth developer documentation with proper real-life full working examples on how to implement framework features.

You have to do this yourself, and it is quite easy to do once you use the right tools.
If you don't want to use SHH and MySQL commands, then I would suggest a tool like HeidiSQL. You can easily convert your database tables from MyISAM to InnoDB using the 'Bulk Table Editor' within the Table Tools.
If you do not want to download more software, you can use phpMyAdmin (You will most likely find this in your CPANEL account or something similar) and run an alter command like this:  'ALTER TABLE table_name ENGINE=InnoDB;'
 
Hope this helps?! 🙂