CaliPilot

Glad you got it solved 🙂
 
Regarding the API issues; I received news last night that MapQuest have (rather silently) decided to close all their "open" APIs, which sadly included the API used by Community Map. While there might have been possible to use other API endpoints provided by MapQuest, I will not do so because of how they've handled this and their lack of communication. I assume none of you got any news about this, even though they should be able to see that you are actively using an API that's about to be shut down.
As of the next update Community Map will not use MapQuest. I am currently exploring the possibilities to host this on my own, as there is a pre-compiled database available that doesn't have the same requirements as previously mentioned. I'm gonna check this out some more over the weekend, and I will hopefully have a solution within reasonable time.

I have settled on a new API provider to replace MapQuest - Geoapify. 
Geoapify have a free tier with far more requests per day than MapQuest had. I have been in contact with them today, and there are no limitations to how we use the API, as long as you stay under their daily limit. That limit is 3000 requests per day, which should be more than enough for most of you. This is not a hard limit, but should you constantly go over the quota they will send you an email asking you to upgrade your account. 
See more about that here: https://www.geoapify.com/pricing
 
I have converted all API calls over to Geoapify today. Just needs some more testing before I can give you an update.
Too bad the marketplace doesn't offer a way to do beta versions, or even have private testers... Can't really do a public beta version either, as the approval time for new versions can be up to a week.

The new version is submitted and is currently pending approval.
I'd mention it again; All of you will need to sign up for a new API at Geoapify. Your current API key from Mapquest will not work.

Hi,
I strongly recommend to do a test drive in a test environment. We had issues when we upgraded and switched from ATP to RT and it took @Makoto a while to solve the issue (which is maybe now fixed for you too).
Chris
 

We have the 1st competition running and we are a bit amazed how well our guys are participating. Some guys came up with questions and ideas which brought me back in here again 😉
It would be great if we could split a competition in 2 phases, the 1st phase is upload only, the 2nd phase is for votes only. So lets say you have a overall competition time from 10/1/22 to 10/31/22, from 10/1/22 until 10/15/22 you can upload your entry and from 10/16/22 to 10/31/22 is voting time for everyone.
That would raise the overall fairness level since in the first days of the competition the early birds have a pretty clear advantage.
It would be great if you think about that feature request, i think every board which is using this App could have a benefit out of it
Thanks ❤️
Chris
 

We have released 4.7.2.1 with an update to the PHP8 compatibility scanner to make it less sensitive to issues that PHP8 is not concerned at this time, such as the following:
Parameter variable names being different in the extended class, eg:
Base: function foo( $node )
Extended: function foo( $forum )
Protected methods becoming public methods in the extended class, eg:

Base: protected function foo()
Extended: public function foo()

Extended methods returning a type when the base class does not have any type, eg:

Base: function foo():
Extended: function foo(): \IPS\Member

This will reduce the number of third party code flagged and thus fewer plugins and applications being disabled.
Posted edited to reflect that 4.7.2.1 has been released.

I'm not the brightest candle on the cake but i learned it the hard way.. many times.. Backup.. every time.. minor or bigger updates.. doesn't matter if there is a warning or not. But i admit, a few words about the impending consequences from IPS would have saved some guys from frustration (even IPS devs).
Chris

The errors thrown by IPS are likely false positives. The application does not have any compatibility issues with PHP 8.0 in previous releases, but I do not believe there is any way to override IPS forcefully disabling the applicaiton.
I've submitted an update to the marketplace to address this, but it will likely take a bit for someone to review and approve it.

Please hold while we work on a plan.
We are hearing you all loud and clear and are working on a solution. I'll update you when we release a patch.

I don't know what else we can do. We've given our marketplace authors about a year to prepare. We started releasing betas in May, and we posted the above in August; yet a lot of our marketplace authors seem unaware.

However, we do not want to cause our clients a headache, so we're working on a way forward that doesn't leave you without apps and plugins you need.

Another suggestion, @Matt.
 Make this message visible to everyone:

 
Transparency never hurts and will certainly avoid posts and messages asking to update.
Currently it shows only to file submitter (and staff).

All these complaints but a simple server snapshot would have allowed an instant rollback. You’re warned to back up first. 

Just as a heads up, if you upgrade to IPS 4.7.2 Radical Tags get disabled and blocked due to outdated code issues.
 
Chris
 
 

i forgot to add more details:

Why? F'me if i'm wrong but there is a clear warning in front of the upgrade which you have to acknowledge with a slider!
But well I can feel the pain of @Davyc and others but if you're running a big site then why the heck don't you have a test environment? It takes a few minutes to migrate to a playground and test the upgrade and plugins there!
I made the upgrade in test a few minutes ago and i know that we can#t upgrade yet! 2 Themes and 3 Plugins get blocked, now i can wait for the devs in piece and silence 😉
 
Chris
 

Just as a heads up, if you upgrade to IPS 4.7.2 Radical Tags get disabled and blocked due to outdated code issues.
 
Chris
 
 

Why? F'me if i'm wrong but there is a clear warning in front of the upgrade which you have to acknowledge with a slider!
But well I can feel the pain of @Davyc and others but if you're running a big site then why the heck don't you have a test environment? It takes a few minutes to migrate to a playground and test the upgrade and plugins there!
I made the upgrade in test a few minutes ago and i know that we can#t upgrade yet! 2 Themes and 3 Plugins get blocked, now i can wait for the devs in piece and silence 😉
 
Chris
 

Already tested, works. Awesome job! 
Regards and thank you very much!
 
Chris

The new version has been approved now 🙂

Just a very quick update before I sign off for the evening.  @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now.  So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app.
I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled.  The locked status is no longer present.
Hope that helps 🙂
 

The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
 

One more thing. A quick shout out to @Adriano Faria who first thing this morning, and I mean first thing, was hammering out update notices on all of his apps. He's the only one that I've seen all day. I hope they all get approved quickly, but kudos for the immediate intervention. I hope that the other devs are also pushing updates, especially on the big apps that so many of us use!

Good point. Best point in the entire thread, actually. I take back my criticism. If we're serious about our setups, we create testing environments. Truth be told, it's not as easy as 1-2-3, but if your setup is monetized and mission critical, you hire someone who knows what they're doing. This does not mean that IPS could not, IMHO, have been more diligent in the warnings and process, but it splits the burden of responsibility in two. Thanks Chris.

New version submitted to fix the incompatibility with IPS 4.7.2.