DawPi

Totally agree.. I just added my 3 cents here. 🙂

Totally agree.. I just added my 3 cents here. 🙂

There have been quite a few developers and theme designers that have left the marketplace or are on the fence as to whether they will continue developing for v4 let alone the v5 platform.
Your team has been working extensively on two different codebases and have become quite intimate with it. 
I would recommend trying to visualize how difficult it would be for a developer new to the platform to setup a development environment and learn how to effectively create programs that meet your marketplace acceptance criteria.
Things to generally think about:
How closely do your programmers adhere to common programming methods for each of the languages you utilize? Is your codebase entirely PHP 8 compliant or are you still utilizing code written for earlier versions?   Are your APIs intuitive to use? Is the cost for entry too high for the first couple of years a developer is learning how to write really good programs and their sales are next to none? Could your error messages be more informative? How does a programmer effectively test their apps?  What lessons learned from your testing team could be useful to a new programmer or to your customers that help beta test two different versions of your suite until such time as v4 is fully deprecated? Would it be beneficial to put a little more structure around public beta testing to minimize the number of additional betas or dot releases after final release. What might you do differently to make becoming a developer more appealing to make recruitment "MUCH" easier and to keep the ones you already have for the long term?

A suggestion, if I may. To enhance communication and avoid situations like that, it would be helpful to create a topic in Developer Connection every time a new version will break something.
For example:
At least to me, it isn't clear that will break all apps without extensions.json. It may be to others, but it isn't to me.
That would help the 3rd-party dev community to update their resources during the beta stage.
Thank you.

This issue was resolved in our recent 4.7.12 release of the platform. Please upgrade to this version to resolve the bug, and if you experience any further issues with this, please let us know.

I was sure that it works that way! If not then it's not logic at all. It should be generated when exporting... Why isn't? 🙂

I was sure that it works that way! If not then it's not logic at all. It should be generated when exporting... Why isn't? 🙂

If we have anonymization of posts turned on, then after editing the post, the username stays in the log. It should also be anonymized.

Probably it was removed somehow from the applications / appKey / data / extensions.json

Weird. I've added second extension with the same code as first and now it... works.

Hello,
my app works fine on 4.7.11 but suddenly stopped being displayed on 4.7.12. Did you changed something in that extension?

@abobader, sorry, it has been fixed. Waiting for approval.
 

@abobader, sorry, it has been fixed. Waiting for approval.
 

☀️ Welcome to this week's Invision Community Insight! ☀️
Thank you for checking out this weekly update. I hope you have had a lovely, productive week.
This week's updates from the Invision Community team are below. 🙂 
 
Current Happenings
New Version
Our latest July beta is ready! Upgrade to the official July release next week. 
As with all beta releases, upgrading your community is at your own risk. Please make sure you backup before upgrading! 
Here is what is slated for the July release, version 4.7.12. https://invisioncommunity.com/release-notes/
 
On Deck

Release Chat
Our July release chat will be happening at the end of the month. Join us live if you can or catch the video and discussion in the converted topic after the event. 
 
Finally, for those that like to see what we are up to line by line, here is the changelog for the week for version 4. Changes are limited for now as we focus attention on version 5. More information will be shared about version 5 at a future date. 
Changelog
 

Thanks, report it to MP Moderator, not me. I'm not responsible for this at all.

Thanks, report it to MP Moderator, not me. I'm not responsible for this at all.

All good, everything is working fine, I was probably tired when I tested this.

Yeah, that should be a stock option. Not just Gallery, but pretty much any content type could be available as custom field in a Pages database. 

I think a good improvement here would be for the flag as spammer action to clear profile fields, member photo and custom field data as well.  If not their profile will remain as a spam billboard (see above).  
Maybe another complementary option would be to simply have spammed flagged profile not be visible publicly (even the user name is often SEO crafted).

Go to ACP and look for „Post Before Registering” - should be disabled.

{{if ! \IPS\Member::loggedIn()->member_id}}  

Almost all functionality will be available to those with active licenses, certainly more than enough to combat the surge we've seen. We may add a little more algorithm-crunching stuff for cloud given access to AWS computing power and more room to swallow additional costs given cloud pricing. It's very much in progress, so we'll have news when everything has been completed.

Matt, it will be available for Cloud only customers? Also - free of charge or…? 

Best regards. 

Done. Waiting on approval. 🙂
 

Done. Waiting on approval. 🙂