Randy Calvert

Like anything EVENTUALLY you will need to upgrade. For example when PHP 8.X eventually becomes end of life and no support for it is available. What Charles is saying is that time frame is so far out, they don’t even know when it is yet. You literally have YEARS before that point. By never upgrading under no circumstances ever… you are going to subject your users to eventually running the equivalent of Windows 95. This can eventually allow your user’s data to be stolen and your site compromised. There is not even a timeline yet for when IPB5 will be released yet… so whatever that ends up being, add some years to it. If you seriously can’t figure out an upgrade path in that time, I would suggest not running a site at all.

Are you able to send a test message to them? Their mail server may be rejecting emails from your server.

Take a look at the following: There is a section around what to do once you have changed the license.

It is fixed in 4.7.13. Generally IPS does not promote manually editing files and instead will recommend waiting for the version to be released.

It sounds like you have a problem mapping fastcgi properly so that it passes requests to the server for processing. https://antonlytvynov.medium.com/nginx-serves-php-downloads-instead-of-executing-6d0442c579a6 It’s also possible your converted htaccess logic is interfering with how requests are mapped and needs to be adapted. These sorts of issues are server related and not related to IPB itself. If you are not comfortable managing server configurations, I would recommend looking at IPS’s cloud offering which takes care of managing all of the underlying technology stacks.

IPS does not officially support nginx. There are converters you can Google to convert htaccess directives however if something goes wrong or you have issues later… you will be asked to switch to Apache for support

ACP > Customization > Appearance > Themes Click the Create New button. 🙂

You can wait for an IPS staffer to confirm, but I can almost assure you this is not a problem in the software. It’s either your server not allowing it to reach the smtp server (firewall issue), or the recipient server is rejecting it.

It’s saying something you’ve provided is wrong. It could be that you’ve chosen the wrong version of SMTP protocol or the port number is wrong. But this is not an IPB issue. It cannot handle authentication issues.

Bounce management is done by the CiC environment because IPS can see the actual bounces. (One of the perks for the way it is deployed now.) If you use a third party service, bounce management is on you to figure out. There are some APIs written to interface with some various providers out there by third parties. Regarding is it worth $20 for email coming from your site… only you can answer what the other company is doing for you. For example do they offer tracking opened emails? Do they show CTR and other stats? Can you use it to prove delivery of email? If so, what’s the value of those things not in the core IPB system to you. You are not required to use a third party service. As a result, if you do choose… it’s on you to evaluate what that provider does beyond what IPS does for you already and if there is enough value from it.

That sounds like a question for Facebook. They are the ones who have changed their requirements/policies. I personally gave up on the social media platforms. They change their rules on a whim and don’t give others a chance to adapt. You just suddenly find one day sometimes stopped working and you are left holding the bag.

This would need some sort of custom development.

They also have the size/scale AND the budget for it in terms of people and money. 🙂 Thats like saying a little league baseball team should be able to do something simply because a professional league baseball team can. I can see why and agree that it makes sense to pull IPS out of the transaction. What would be nice is if there was a better aggregated resource discovery tool. Nothing that handled the sale… just discovery.

It’s funny how things start working just before a tech person looks at something… I can’t tell you how many times I’ve seen it happen. I blame the gremlins!

Mail is mail ultimately. The only big difference with IPB's sending of email is that it is sent from a generic address. See my comments in for details. I switched my community to using IPB's mail system and have not had any issues at all. Users never realized anything was "different".

I don't believe this is permission issue with File.php. Nothing is actually stored within that file for it to be written to. What I think is happening is an issue with the bucket itself. IPB is trying to save stuff to the bucket and not getting proper permission to do so. File.php is triggering the save to AWS, but with the bucket not working properly, it is throwing an error.

I’m not Charles but as a teaser based on prior comments by IPS staff… IPS has actually removed the native app from prior versions with the note it is highly unlikely to be added back again. Instead they are focusing on PWA and better responsive mobile design. 🙂

If by “it does not work” you mean the mail does not end up in the recipient mailbox… it’s most likely you do not have mail setup properly on your server. For example, is SPF and DKIM configured properly? Your mail is most likely going out but being rejected by the recipient server thinking it’s spam.

From the FAQ on the self-hosted page: For the most part, IPS stance has been to use the Requirements Checking script to check your server versus listing every single PHP module/version. They also recommend if you are unsure or are uncomfortable with the requirements to consider using the IPS cloud hosted version where you don't have to worry about all of that and instead just use the software (like using Gmail).

IPS does not make old versions available. Only the latest versions of the software can be downloaded.

IPS has a guide for moving to a different server: Before you begin the migration, make sure the new server has all of the required modules…

You won’t be able to use Gmail for sure unless you are using an app specific password. I believe the same is true for Outlook. They don’t allow you to send with the same password you use on their website. https://support.google.com/accounts/answer/185833?hl=en

https://developers.google.com/search/blog/2020/05/google-translates-website-translator You want the website translator. Once the widget is on your site, a user would just pick a language from the drop-down and the page is translated.

As someone who went through this year ago… I can talk about my own experience. Moving to the cloud has been a good choice overall. I’m very happy with the decision. I no longer need to worry about things like Apache, PHP, MySQL, etc. I no longer have to optimize the configurations for each of the systems for performance. I also no longer have to worry about things like firewall tuning and scaling for bot traffic etc. At the end of the day… it’s like using Gmail. I just simply use the service. The hardest part of the experience was simply letting go. I can’t go play in the database anymore. I can’t go manually edit a file, etc. This was hard at first, but eventually I came to realize that at the end of the day I really did not NEED to. By not manually playing around in those areas, I’ve had better stability and easier times doing upgrades, etc. If you can think of your site being a SaaS solution instead of just another script to install, you’ll have a much easier time. Regarding the migration… Olivia and Marc have the process down to a science. They will communicate exactly what is needed, work with you to agree on a date/time to do the move, explain exactly what needs to be done, etc. In a nutshell, you need to upload a complete copy of your site files (so they have any uploads and 3rd party resources) along with an export of your database. They will import it and configure their side to handle it. You can use a temporary address to test to make sure all is good and once ready, change the DNS to their control to make it live to the world. We arranged for our site to be taken offline at 3am while I exported everything and uploaded it to IPS. By 8am, I was doing my final testing and go live.

If you're comfortable with Centos, you will want to look at any OS that is a derivative of RedHat Linux (RHEL). Take a look at either Alma Linux or Rocky Linux. Rocky in fact is developed by a Centos co-founder. Either of those two are also directly supported by cPanel as well. (I don't know what your hosting provider might support, so that might make a difference as well.) Anything based off of RHEL should be pretty comfortable for you though just in terms of how the OS feels and operates.