CoffeeCake

If you click on the phpinfo link at the upper right of the compatibility checker, the path to the PHP version being used by your web server will be shown.

This would require a modification. It's all or nothing out of the box.

Have you tested this conversion on a test environment first?

This is happening because your server checks for the presence of a file on the filesystem first. If found, it executes or serves the file. If not found, it passes to IPS, and IPS has to work to determine if the URI if the request represents something to serve out, if the request has permission, and whether or not to return the not found error. You can identify the traffic that is asking for things it shouldn't be asking for and block it with a firewall, either on your server or in-between your server and the requestor. This configuration may be complex and depends entirely on your environment, yet the behavior you are seeing is precisely by design otherwise.

Yes, look into using a firewall to block these connections. Unfortunately, the request has to go to IPS to see if there's an address to return. There aren't files on your server for every thread, forum, etc. Cut them off before they hit your webserver.

Oh I'm sorry, I had no idea you were on CIC.

You might be interested in this:

Maybe do the upgrade on the old server then, and then move everything to the new server.

If your 3.x MySQL database is not on the local web server, then this could be an issue. Maybe it would help if you outlined every step you took to prepare your new server in detail. I am not familiar with the steps involved in a IPS 3.x to 4.x upgrade, yet I would think that it would be similar to other upgrades, where you'd update your conf_global.php file to point to the IPS 3.x database, then run the upgrader and never run the installer. Right now, it sounds like you've installed a new copy of IPS, with its own new database. You'll need to wipe all that and start over.

No idea how you upgrade from 3.x to 4.x, but my guess is the part where you said /admin/install/ Perhaps this should have been /admin/upgrade?

If you haven't already, you should open a support ticket.

You'll need to sort out with Cloudflare how to set the correct security policy. Edit: https://support.cloudflare.com/hc/en-us/articles/216537517-Using-Content-Security-Policy-CSP-with-Cloudflare#:~:text=Cloudflare doesn't require changes,locations specified in your CSP. You'll need to make sure the CSP headers are correct for your site. Looks like Cloudflare simply observes whatever your webserver sends.

Here's significantly less sucky implementations: https://kevinfaguiar.github.io/vue-twemoji-picker/ https://emojipanel.js.org/

It's the Twitter style emojis. They are absurdly slow to load.

Is this a self hosted site? If so, what content security policy is your web server sending if any?

It may have an impact. Interesting to know how IPS, in the no-access-to-code-before-install model, will check for and notify of compatibility.

What are MailChimp's instructions for validating your domain? You will likely need to do that regardless for them to send e-mail on your behalf and from your domain regardless of whether or not you use this third-party plugin. You'd only need that plugin if you did not want a separate opt-in for your newsletter beyond the registration in IPS, and you didn't want to manually extract and import member information into MailChimp. The plugin automates those tasks for you, from what it says on the tin (have never used it, can't vouch for it doing what it says). MailChimp probably also want you to make a modification to your DNS to indicate that they are allowed to send mail on your behalf. I'm a self-hosted customer, and I'm not sure how you do that with IPS Cloud. You'd likely need to ask IPS support for help with that part.

Roadmaps are scary. They set expectations, they get people upset and up and arms at things in advance, they relinquish control of any competitive advantage a surprise release or implementation might bring with it. Some character in a remote part of the world is upset that IPS isn't adding native electric shaver support. Someone else is irrationally unhinged that some feature they'll never use is being added and turned off by default. Someone else immediately wants the thing yesterday. But you know what? I say put on your big person pants and publish one anyway. Because you're not about to be defined by cowardice. You've got the cojones to share your plans, state that they're only plans, and give some insight into what's upcoming and when approximately you'd expect it to turn up. And when things get hard, and targets slip, or you need to change course, you'll apologize that you missed the mark and keep us all informed.

A roadmap, of any sort, would be a welcome change. A blog post about a future feature coming some day off in the yonder does not a roadmap make. Some examples: Discourse: https://meta.discourse.org/c/releases/30 Flarum: https://github.com/flarum/core/milestones & https://discuss.flarum.org/d/6755-the-new-improved-flarum-roadmap Tribe: https://community.tribe.so/post/product-roadmap-2020-5e34aa3949858b2fdcba9ef7 Wordpress: https://wordpress.org/about/roadmap/ Xenforo: Suggestions, sortable by popularity - https://xenforo.com/community/forums/xenforo-suggestions.18/?order=vote_score

I think that happens when someone purchases the product. There are not pre-generated keys. You can generate an invoice and mark a product as purchased if you'd like to get one outside of the normal self-serve checkout process.

As far as I can tell, this remains an issue in 4.5.4.2 + all security and patch updates as of now. Not only does it impact Support requests, but seemingly anything other than the individual posts within a single thread. If you had 100 spam threads in a given forum, you'd encounter the same issue.

I cannot reproduce this. If I select 25 threads on page one, navigate to page two of a forum, and select two more threads, my count is set to two, and the action I select only applies to the two on the current page I am on. This is still broken in 2021.

If you have the grid view enabled, it's in forumGridItem as well.

Search your template for redirect_hits and remove the bits you don't want.