Sonya*

Sure, that might be a consequence. Just throwing out ideas off the cuff, but consider having a developer indicate something like a service-level agreement at the outset at the time of purchase. "This is $10, but no guarantees it will continue to work in the future" vs. "with ongoing support and maintenance for the 4.x series"
And I would think that the trigger to have a resource opened up to the community would be after some inactivity or by the developer communicating their intentions to IPS. Maybe Adriano wins the lottery, moves to a private island, and lives this rest of his days sipping from coconuts. He decides that he'll sell 10 of his extensions to Kevin, 20 of them to Scott, 40 of them to Veronica, etc. He updates his extensions to indicate the new account supporting them. Or maybe Adriano can't be bothered by all that, and drops off the face of the earth, jetsetting around the globe with supermodels and the uber rich, and doesn't log into his account or make any updates or respond to any support requests for a year.
In that last case, the hypothetical clause kicks in and IPS says "Hey, this stuff appears to be unsupported. We've reached out to the developer via e-mail three times, called him once, and no response. In 30 days, we'll make it available at your own risk as open source."
I may just be suffering from too much cabin fever, but I think it's a novel idea.

You have the same key for four different strings. You cannot translate strings with duplicate keys. Check where the keys are derived (custom theme?) and contact the developer asking him/they to change the keys. 

You have the same key for four different strings. You cannot translate strings with duplicate keys. Check where the keys are derived (custom theme?) and contact the developer asking him/they to change the keys. 

Currently only the following values are outputted through the RSS feed:
"title"
"description"
"link"
"date"

I think "author" should be added to that information.
That way, for example if you're using RSS to output to Facebook or Discord or Twitter, and you're customizing the outgoing feed, you can include the author of the post.  It looks a little weird when you just see some random post and have no idea who it's from, just appears to be from the site itself. 

You can use these plugin to add code to the head 
 

Right now, when selecting "Delete content submitted already" in Spam Prevention > Flagging Spammers, content is immediately deleted. We are wanting instead to have that content moved to the "deleted content" queue that serves as a sort of recycle bin, in the event that someone needs to reverse the action.
Please add this as an option, so that our choices aren't only hide or delete instantly. We want to delete in the same fashion as deleting manually as a moderator.

In AdminCP go to System -> Support -> Support and choose Something isn't working correctly. 
 
 

Search for search_blurb_date_* strings to translate.

True
Personally, I never understood by IPS didn't allow custom fields everywhere, only in certain apps like Pages and Downloads.  

The tags above are stripped in the translated strings while displaying. They are saved, but not displayed on the GUI. Examples:
themesetting_js_position_body themesetting_js_position_head  

I have deleted the strings with SQL from MY installations. But this is definitely something that IPS has caused in the previous versions. I have checked some older installations (also those I have not setup or customized but have an admin access to), they all have these strings defined. 😏 

If I open applications/cms/data/lang.xml, there are no instances of "r__menu" anywhere. I am unsure how you have those in your database, perhaps this was an issue in a much older version and it has since been corrected, I can't be certain. I would recommend you simply clean them up in your own database if they're present and posing an issue.
I cannot find "read_more_about" or "task__publish" in Blog. Again, those may be older language string entries we've already cleaned up but didn't outright delete. I would recommend cleaning them up yourself in your own database if they're posing an issue.
(It is also possible there are changes in 4.5 that explain the difference, I am checking our working release and not 4.4.10).

I renewed my license, applied the latest version and the sitemap is now working like it should.
Thanks for the help everybody!

I'm struggling with a navigational issue involving the IPS help guides here that has irked me enough to make this request.
There is no way to navigate to the "next" content page when browsing the guides. Would you please consider adding "previous" and "next" links within the guides, and maybe for bonus points, jumps to the last and next sections of the guide as well.
For example:
While in the Pages section, I might be looking at Core Concepts and be reading along each entry. To go to the next one, I need to scroll all over the page to find the menu on the left, figure out where I am, and then figure out what the next page is instead of a nice "Go to Databases part I" link at the bottom of the Blocks page.
Please, for my own sanity. 🙃

I checked the settings for the sitemap and it is using the recommended settings and I haven't made any changes to the settings in the past. I know I should upgrade to the latest version but not sure if I should put more time and money in a site that appears to be going nowhere. 

They are not used, that's right, but they are there and prevent saving the translated string. This is a fresh install:

This is another example:

Probably you can run a SQL to get those double keys to eliminate them? 🙄

Sounds like Mod_Security is blocking your change, try disabling it or reviewing your logs for mod_security.

+1 for a native dark/night mode!
I'm not thinking about myself when asking for that, as I wouldn't even use it myself. But it's now far too common for any (web) app to offer light and dark modes that suit all needs and tastes. IPS Community Suite should definitely follow that.

I have a TESTINSTALL instance of IPS 4.x.x Forums upgraded from my previous IPB 3.4.6 forums and have made many changes to the ACP in terms of almost every setting, including building out new forums labels/structure/mods/perms, Menu Manager, etc.
I will be upgrading my production IPB3 instance soon and want to overwrite my ACP settings from TESTINSTALL if possible to avoid the repeat work. Using UPDATE on the core_sys_conf_settings table seems obvious and relatively risk-free ... any gotchas here?
What about other settings that likely require additional tables and meta-info like Menu Manager, Forum labels/structure, Member-Forum-Mod perms, Block config, etc? Perhaps it is safer to manually handle all of this, but wondering if anyone has devised a best practice(s) for this piece.
Thanks in advance.
 
------
Edit:
The following can possibly be updated using UPDATE ... SET from other instance
core_sys_conf_settings core_menu  
 

I thought it might have been abused in the past, as I seem to recall updating some after purchasing.
Still, it would be nice to move with updates and changes.
Hopefully, it will be accessed and changed. 🤞🏻

@newbie LAC, if you consider to make a plugin, could you please add some simple options? 🙄
Set default country (dropdown-field) Always use the default country (Yes/no) Try to determine the country by user IP, if not possible use the default country (Yes/No) I think this would cover every need 🙂

@newbie LAC, if you consider to make a plugin, could you please add some simple options? 🙄
Set default country (dropdown-field) Always use the default country (Yes/no) Try to determine the country by user IP, if not possible use the default country (Yes/No) I think this would cover every need 🙂

Thank you very much! Please consider making it into a small but very useful plugin and posting on marketplace!

Create a plugin or open system\Helpers\Form\Address.php
Find 
if ( isset( $_SERVER['HTTP_ACCEPT_LANGUAGE'] ) ) Add above 
try { $location = \IPS\GeoLocation::getByIp(\IPS\Request::i()->ipAddress()); if (\in_array($location->country, \IPS\GeoLocation::$countries)) { return $location->country; } } catch (\Exception $e) {}  

Thanks, I've logged a bug report to have this looked into.