Jim M

Excellent! Glad to hear it worked.

Did you finish applying the patch? It sounds like it may have stopped prematurely. You will want to check in {your-base-url}/admin/upgrade to see if it finished. If it did not finish, run it. If it says there is nothing to update, you'll want to follow the instructions and manually apply then run the upgrader at the URL mentioned above.

We have a bug report in for this but you will want to ensure your server configuration is suppressing deprecation warnings.

Glad to hear you got to the bottom of your server configuration.

As a software provider, we do not provide hosting support. Software does not control this but rather your hosting configuration does. If you are unsure, you would want to hire a server administrator to help you.

This would be dependent on your server configuration. We cannot tell you this as server configuration support is outside our scope of support. Only your hosting provider or server administrator can tell you why it's not working.

The application can't open the /uploads/logs folder. Ensure that it is writable and has correct ownership.

Switch to an unmodified language pack and theme then try again

This would be your email provider.

Typically, we see this when you are using a service like SendGrid and they implement their own click tracking on links. I would suggest disabling that if you are using that service.

We recommend keeping it as the default admin folder as this will be removed in version 5. You can find more info below though: We only provide the latest release of supported versions. It would not be recommended or supported to run anything else as they will have bugs and security issues.

Please open a ticket with us and we can get you a backup of your community and explain the process.

Without any further info here, I believe you're referring to Profile Completion, which you can read here in the guide how to manage it:

You will want to check your server's caching. It looks like it is caching whole pages or sessions which should not be done in a dynamic website.

We have replied to your ticket 🙂

Are you encoding the characters of your body parameters correctly so that they are passed as desired?

Glad to hear you were able to resolve the issue!

Template syntax is effectively just PHP so we would not define that, no. We do not provide a definition of all our Classes utilized but this can be found in developer mode and some detail in our Developer docs:

That's the access log, not the error log. You will need to contact your hosting provider if you are unsure how to obtain these.

Yes, you can find documentation on template syntax here:

You will continue to be able to use version 4. We will make an announcement when we will require version 5. However, that is likely once version 4 is no longer supported and version 5 has matured. While I'm sure many clients will jump into version 5. We respect that some will want to wait for it to mature or have third party services they need updated, etc... With that said, we likely will have a cutoff period once version 4 is no longer supported as technology has to keep innovating and remaining secure 🙂 . When that is though, I don't think we have a date in mind as we are still in version 5 beta phase.

It is available in the latest release of version 4. 404s will slowly dissipate from Google's webmaster console. 404s are a natural part of a dynamic website. Google brings these up for your action in case you need to take action but if the link no longer exists, it is completely natural and you can ignore. Google will slowly phase that link out of it's index.

Unfortunately, custom code is outside our scope of support. I can only say, if you think something may be an issue, remove it and test. The issue in general is related to: IPS\forums\Topic\Post::shareableUrl() So I don't think it is that though. Something, whether a third party application/plugin or part of the theme is calling that and creating an issue.

You would need to look in your server error logs to find that 500 Internal Server Error. It may be a timeout, it may be something else entirely. If it is a timeout, you'll want to extend it or investigate why your server is taking a while to process this.

You would build the download function into your application consuming our API. Otherwise, you would simply direct your customers to the Downloads application where the download URL is hidden and protected when downloading. Currently there is not a bug here as the API is working as intended.