Martin A.

The arrow points at Monday.

That's how you should understand Invision Estimates

The arrow points at Monday.

Ok Thanks!  I got it fixed up.  Seems like the map still updated, I am at 1.0.4 when my CSS came back!

Run the support tool to fix and then apply the patch to prevent this occurring 🙂

They can be added automatically if the members location is saved in a profile field. I am not familiar with the Wordpress plugin, so I do not know how that works. As long as they are a member, and isn't marked as a spammer, they will show on the map. I can either make a custom plugion or change Community Map to change this depending on how manage these memberships. There is a setting to show the members in a list in a sidebar next to the map.  No. But you could have used this plugin which unfortunately isn't updated to 4.5 yet. It would add in some extra steps, as markers added to Community Map would not be synced back to that plugin, but Community Map will import locations from it.  

Make sure you're on the latest version. That bug was fixed in 1.0.2 which was released on Saturday.

XRegExp is 135KB when minified as part of root_library.js (that whole bundle is only 383KB, so it's a significant chunk), but it's only used in two places:
In ipsautolink/plugin.js, it's just used to evaluate a native JS regex, which I believe is totally unnecessary (use this.urlRegex.test(text) instead!) In ips.search.results.js, where it's just used to replace using a native JS regex (use $(this).text().replace(new RegExp(...), '...') instead, as you do for each subsequent replacement in that chain) (while you're at it, why does that code replace with HTML, HTML escape everything, then selectively unescape the content you just added?!) Removing those two places that don't, to my understanding, utilise the library in any meaningful way would allow you to slim down the site by a not-insignificant amount, and make certain people happy.

Your cache level should definitively be Standard, the default setting. Using anything else will break IPS' cache busting feature, which is needed to recache static assets.
Cache TTL can come down to a matter of preference. Considering important resources like CSS and Javascript assets are cache busted as needed, it's safe to use values up to even 30 days if you so wish.
The potential concern with this is, if image attachments are deleted but left embedded into posts as an example, they will still display as cached in the users browser for however long you set this to. So, it can be a minor privacy concern, as IPS currently does not automatically remove image embeds from posts when attachments are deleted from the users control panel.
That's really the only thing to keep in mind. Otherwise, I recommend at least 7-days personally.
 
Outside of these, there are several useful features Cloudflare provides that I recommend taking advantage of.
Note, some of these features are Pro only, but if you're a Free user, use the ones that aren't. They help if even a little bit and there's no reason not to.
Now, if you have a high traffic website and you can afford it, I personally believe it's worth upgrading to the Pro plan.
 
But to get started with the optimizations, under the Speed tab, go to Optimization and make sure these settings are enabled.

Polish with WebP enabled can be hugely useful if you have a lot of PNG attachments / avatar uploads on your site, as WebP can provide substantially better lossless image compression compared to PNG.
Auto Minify is disabled by default and you should enable it. The actual performance improvement is small, but it's still an improvement with no risks, so there's no reason not to use it.
Brotli, again, small improvements, but no risks and and no reason not to use it for clients that support it. All the overhead involved in performing the compression is handled by Cloudflare here after all.

Enhanced HTTP/2 Prioritization and TCP Turbo are again zero risk performance improvements and if you have access to them you should enable them.
Mirage can be great in theory for mobile browsers by automatically optimizing images on slow networks. It's in beta, but I do definitely recommend enabling this. Roughly half the of the internets traffic today is mobile. These optimizations can yield huge benefits to your users.
Rocket Loader I do not recommend enabling, as it can cause functional and perceptional issues with IPB. It makes things look and act in strange ways, and can potentially just break things. Rocket Loader is one of those things that works well for some sites, but is awful for others. It's not great for IPB in my experience. I say the same for PageSpeed JS optimizations and so on as well.
Under the Network tab, make sure these settings are enabled.

All of these are, again, zero risk performance optimizations. No reason not to use them.
Argo tunnel can potentially be useful as well, but note that it can be extremely expensive depending on your bandwidth requirements. It's an additional $0.10/GB of bandwidth. Do not enable it until you have at least a months worth of bandwidth analytics logged from Cloudflare so you have an idea of how much you can expect to pay if you enable this feature.

Ips has confirmed a fix for 4.5.4

This is out of my hands as soon as the new version is submitted to the marketplace. It may take a few days for the new version to make its way through the approval queue.

This is out of my hands as soon as the new version is submitted to the marketplace. It may take a few days for the new version to make its way through the approval queue.

Thank you, Martin.  I'll do that.

Hi All,
Just to confirm that is was my fault.
 I've completed the Marketplace setup process and told the system that his Member Map application is Community Map. After a ticket with IPS support all works fine.
Thanks to @Stuart Silvesterfor his help, and also to all that help me.

I honestly did not think this was getting approved (at all). But there it is.
The statement provided before still stands. Enjoy this while it remains valid. Not "approved-Marketplace" valid, more like "functional-valid".
And also remember the use-case this was generated for. To allow for users to download attachments (and Downloads for non-monetized Downloads instances) without the need for signatures. If your needs are greater, features and security-wise, look elsewhere... 

I suspect that @MrUtOpiK has completed the Marketplace setup process and told the system that his Member Map application is Community Map. We'll need a ticket submitting in any case.

Awesome!

No, this uses MapQuest for searching for locations, and free map providers to display the map. The map(s) you want to use can be choosen in the ACP (almost all of these)

It was indeed. 1.0.3 is submitted which addresses the old membermap URLs. It will do a 301 redirect from /membermap/* to /communitymap/*. 

It was indeed. 1.0.3 is submitted which addresses the old membermap URLs. It will do a 301 redirect from /membermap/* to /communitymap/*. 

Thank you, Daniel. I've submitted a new version that only addresses this issue.

There's a bug in the recent release..
Stack: 
TypeError: Argument 1 passed to IPS\communitymap\Members\_Groups::getData() must be of the type int, null given, called in /Applications/MAMP/htdocs/mpsept/applications/communitymap/extensions/core/GroupForm/communitymap.php on line 40 (0) #0 /Applications/MAMP/htdocs/mpsept/applications/communitymap/extensions/core/GroupForm/communitymap.php(40): IPS\communitymap\Members\_Groups::getData(NULL) #1 /Applications/MAMP/htdocs/mpsept/applications/core/modules/admin/members/groups.php(207): IPS\communitymap\extensions\core\GroupForm\_communitymap->process(Object(IPS\Helpers\Form), Object(IPS\Member\Group)) #2 /Applications/MAMP/htdocs/mpsept/system/Dispatcher/Controller.php(90): IPS\core\modules\admin\members\_groups->form() #3 /Applications/MAMP/htdocs/mpsept/applications/core/modules/admin/members/groups.php(39): IPS\Dispatcher\_Controller->execute() #4 /Applications/MAMP/htdocs/mpsept/system/Dispatcher/Dispatcher.php(152): IPS\core\modules\admin\members\_groups->execute() #5 /Applications/MAMP/htdocs/mpsept/admin/index.php(14): IPS\_Dispatcher->run() #6 {main}  

Completely understand, and yes you'd be stuck if you did not have a backup of your server's filesystem and database.
However, on the long list of reasons why it's not a dubious idea to use an ecosystem that has shifted to a black-box of dependencies that get direct installed for a community, the idea that "I paid money for access to IPS services in the past, so I should be able to use Marketplace when my license period has lapsed" is not a consideration our team is concerned about. We'd have no issue with the requirement of having an active license to be able to download Marketplace items.
If you don't have an active license, you don't have security updates, and your community shouldn't be online on the platform. In a circumstance where the IPS licensing is out of reach, it's time to migrate to a lower cost or open source solution that protects your community members interests by being accessible to security updates.
Edit: To clarify, however, I think it's irresponsible to not provide security updates to all active and inactive license holders to address situations like your hypothetical, yet that's how IPS does business today.

This is the support topic for
 

That is correct. I have thought about making this a paid app many times before, both for the 4.4 and 4.3 version. And the price I'm placing on this now is the same I planned to put on it back then. (It is also the same price Michael (InvisionModding) had on his Tutorials app 10 years ago in the 3.x series, so I would say it's about time the overall prices increase in this market)
Having this generate a bit of income will of course increase the motivation of keeping this updated and adding new features a great lot. The first version of this will not come with many new features, mainly just the IPS 4.5 compatibility.