Jump to content

Randy Calvert

Clients
  • Posts

    3,916
  • Joined

  • Last visited

  • Days Won

    78

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Randy Calvert

  1. What happens when you click on the refresh license data above that date you circled?
  2. Because IPS is able to take the feed of bounces/complaints from AWS and write a service that disables email for the relevant account. If you’re self hosting, there is not anything to generate that bounce/complaint feed that is consistent across most self hosted platforms. In fact a majority don’t have any sort of API to query/track bounced mail at all. That means doing this in a self hosted setup is impossible to get the input to do what you want them to do.
  3. ALL emails that come from CiC are sent from that address on behalf of whatever address you have as your default board address. This means if someone replies to that message it goes back to you and not IPS. IPS cannot send mail on behalf of your domain without a ton of extra setup work (such as DKIM and SPF) regarding spam. In addition it would require IPS to get your domain approved by AWS to send email, which in itself can sometimes be a large task. If you don’t want to have the invisioncloudcommunity.com as the outbound, you’ll need to use your own SMTP server for outbound email or configure sending email through Sendgrid. This means you are responsible for the outbound email delivery instead of IPS.
  4. I can't reproduce it on my Mac, iPhone, or iPad. I tried it on a Windows VM using Chrome and could not reproduce it either.
  5. Yup... but then removed again shortly afterwards. 😄 It's like a yo-yo or boomerang.
  6. There should be a way to whitelist your site or turn it off. Step one is to temporarily disable all their protections. See if it fixes the problem. If so, they can either figure out how to whitelist your site or find the specific protection that is blocking it and work with McAfee to fix it. Otherwise it could still be something else on their computer. We still don’t definitively know McAfee is the problem.
  7. As a stupid question... why not just upload a smaller image instead of trying to resize the existing one?
  8. There is not a default feature to do this. I looked in marketplace around the phrase “password” and did not find anything either. It would most likely need developed by a 3rd party.
  9. That means you’re not being caught in the reputational risk database. But it could still be interfering with JS. (For example thinking it was an ad that it was blocking.)
  10. Total Protection includes things that can block JS and acts as a firewall, so it’s absolutely possible. He should be able to temporarily turn it off to test. If that’s the case, there should be a way to whitelist your site. For example: https://www.mcafee.com/support/?articleId=TS101116&page=shell&shell=article-view
  11. That is something IPS will need to setup on their end. Once they do, you’ll need to change your dns settings at your domain registrar. The ticket will have details. 🙂
  12. Not to be rude, but yes... that's kind of the point. Business do that. They introduce new features to get you to use their stuff. 😉 ESPECIALLY the services that have higher margin and lower support costs.
  13. I'm sorry, but that is incorrect. 85% of features released have been for everyone. The features that are actually "cloud only" are that way because it requires stuff that does not typically exist in a regular web hosting environment. @Matt explains this pretty well in the following topic:
  14. Check out the following... it looks to be IPS's direction for APIs. This is something they've noted they'll be heavily investing in as we go forward as a way to reduce the amount of 3rd party apps breaking with new IPB releases and PHP version changes, etc.
  15. The first mention that I saw of it was Feb 23rd. Though the deprication discussion is the first talk I've seen of actual timelines. 🙂
  16. By the way... just to help you understand... https://www.php.net/supported-versions.php If your host is only supporting PHP 7.4, I would highly suggest finding a new hosting provider. They're running critical software they cannot get security updates for and that is highly outdated.
  17. Are you installing a new version of IPB software? If so... have you checked to make sure your host meets the requirements for it? The reason I mention this is because the 4.7.x versions of IPB require PHP8. Your path mentioned in the error code reflects PHP7.4, which is not supported. (PHP7.x is end of life and not supported by PHP itself anymore.)
  18. The 4.7.x series of IPB have all REQUIRED PHP8. So if you're running the latest version, it's absolutely compatible with it. Either you're missing a PHP module as noted by Marc above... or you have a 3rd party resource (application or plugin) that is not compatible with PHP8. If Marc's check above comes back clean, I would suggest disabling all 3rd party resources and testing. If you can't login to your ACP, use recovery mode to disable everything for you.
  19. I think it’s a more of a “just because you can, it was not intended for you to do it” thing. My guess is they’re not directly wanting to support you trying to do what you’re doing despite that it works in some circumstances.
  20. IPB's systems are already smart enough to reject those kinds of activities. You don't need to code anything if you're using the suite. The fact that it was attempted though is still logged even though it's stopped. But if that IP itself is doing that sort of activity, why allow them to even try? Just block the IP itself from even reaching your server.
  21. They look to be ATTEMPTING brute force logins and switched to trying to look for a PHP exploit. Each of these would have failed, but it looks like a malicious actor. You might want to just block their IP itself in your firewall if you have one or have your host block them.
  22. I would disable EVERYTHING (all third party applications and plugins), and switch to a default theme. While everything is off, in ACP visit the support section and clear the system cache. Then test… if it’s working, you know it’s something that is disabled. Turn things back on one by one till you find your culprit.
  23. This would be something done within your theme. You would need to find the appropriate section of the theme code and add additional HTML code for whatever you want to add.
×
×
  • Create New...