Martin A.

Yeah, those times can be a bit confusing. You need to look at the Published date, the Updated date was most likely Martin updating the file's description. The two things are separate.

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.

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.

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.

As a fellow MP dev...hats off to @Martin A. on the above work to get this back to working order.
 

Done. Thank you.

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.

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.

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.

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.

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.

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.

I'm going to hazard a guess that you are asking if the approval was done - yes, it was...2 weeks ago.
If you are relying on me posting in here to say it has been approved then please don't as I won't - I'll post once to say a release has been submitted.
If you require a notification when a release is actually available (has been approved) then go to the resource and click the "Send me version updates" link located on there and you'll get a notification.

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.

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.

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.

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.

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.

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.

Yeah, a few sites I know that were using that application all converted to using Radical Tags instead.
 
As for Minimized Quote, it's now a built-in feature since version 4.5 so you can just uninstall the plugin.

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.

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.