Jump to content

bfarber

Clients
  • Posts

    163,911
  • Joined

  • Days Won

    346

 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 bfarber

  1. Yes, can you clarify what you mean by that?
  2. It sounds like you believe you've found a bug, but I'm having trouble understanding what bug you want to report from the screenshot alone.
  3. Contextually, it can be quite awkward for a conversation to be newest to oldest so I have trouble seeing the use case for this in forums. I could potentially see a use case for this in certain areas, such as specific Pages databases.
  4. With 4.5, this will rely upon each user's "Content view preference" option already.
  5. Edit the entry and change the "Feature Photo"
  6. As a random example.....
  7. BBCode has been deprecated in 4.5 so I would recommend moving away from it. We won't be fixing bugs related to BBCode moving forward.
  8. Don't take this as a definitive answer, but I believe it's not possible to distribute an app through the Apple app store that allows adult content to be viewed, so it's a non-starter unfortunately. That wouldn't even be a decision we have control over, if I'm remembering correctly.
  9. Where are you seeing an error or notification that the RSS is failing to import and throwing an error?
  10. That's not true. UPDATE core_members SET members_bitoptions=members_bitoptions & ~1048576; UPDATE core_members SET members_bitoptions=members_bitoptions | 524288; Something along those lines should do what you are after.
  11. The -200 error just generally means there was an error uploading the file. It can happen for multiple reasons, but with images specifically it often occurs because of memory limitations. That isn't, however, the only cause. A slow upload speed could cause an upload failure as well, yes.
  12. Yes, I would think if you have 20 running that they're not stopping for some reason and they obviously should. It's really hard for me to say much more at this time from here unfortunately.
  13. We made an intentional decision not to do that, because we outright want a developer creating a new controller to explicitly review and ensure they've implemented CSRF protections. I'm afraid this change is unlikely, at least in the immediate future.
  14. I would recommend trying a standalone script that connects to redis, stores a value, then retrieves and displays it just to make sure everything is in fact working correctly.
  15. With padding (and similar) CSS properties, if you only define two values then the first one will represent top and bottom, and the second one will represent left and right. So "12px var(--sp-3)" is like saying "12px var(--sp-3) 12px var(--sp-3)"
  16. It's theoretically possible you've hit a PHP bug where the script is not exiting as it should. It's really hard to say from here. And it's worth mentioning that two tasks running at the same time is not in and of itself an issue. The first execution could be sending notifications and the second could be running a separate (quicker) task manager task. It's ok if they stack a little, particularly when you have background tasks running.
  17. Just for clarity, in the ticket Marc was indicating we could not provide support for getting your 3.4.x installation working - we do support the actual 4.x upgrade. Essentially you get your 3.4.x database in place, ensure MySQL and PHP are on versions supported by our latest release, upload our latest release files, restore your conf_global.php file, public folder and uploads folder from your 3.4.x installation, and then visit community.com/admin/upgrade/.
  18. There are still many theme changes occurring in the betas - your customizations to a theme should not be wiped out during upgrades, but particularly during betas things can change that may have an impact. For instance, the header logo was redesigned slightly so that might explain the issue you were seeing here.
  19. This was due to a configuration oddity on our side here. It should be resolved now, thanks.
  20. Have you verified the redis details are still correct with your host?
  21. There is no built in option to do this I'm afraid.
  22. Do you happen to have a bunch of background tasks queued on your dashboard presently? If you just upgraded to 4.5, you may have many background tasks queued to run, which would explain why cron tasks are taking up above average resources.
  23. That sounds like the OAuth provider (Auth0) is throwing the error. You may need to look through their documentation or reach out to them for clarity.
  24. If this issue exists in 4.5, post it in the bug tracker please.
×
×
  • Create New...