Jump to content

CoffeeCake

Clients
  • Posts

    1,916
  • Joined

  • Days Won

    24

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by CoffeeCake

  1. For those on your Community in the Cloud platform, the public status service is a step in the right direction. I'm sorry to hear there have been such significant problems and launching it is likely the result of an onslaught of inbound support chat requests that the world is on fire for them.

    It would be great to take that reactionary energy and channel it into useful proactive solutions by being equally transparent with the status of known bugs/issues (and workarounds if applicable) and the expected resolution availabilities beyond "some future version."

    Your list of issues is welcome, however formalizing this along with "available next maintenance release," "next minor release," "next major release," "4.6.3.1," etc. would be greatly appreciated. I have no idea when the PHP8 error will be made available that the team worked hard to fix this week.

    I know you probably don't know either right away, and that it takes a bit of discipline, yet so does maintaining a status page.

  2. 20 hours ago, Tim Tyler said:

    On my forum, after receiving a bunch of 404 Search Console notices from Google, I just noticed that the last posts in several subforums are missing.

    Have you submitted a ticket? This seems to be a serious issue.

    1 hour ago, usmf said:

    I never ended up starting a ticket on this one, as we have had three serious issues since and I have worked on those.

    How are you sure it won't happen/isn't happening to posts in other forums?

    As Adriano suggested, do you have archiving turned on?

    If so, is it a different database (the remote database option)?

  3. 2 hours ago, Jordan Invision said:

    dots = progress!

    There have been four releases today as of the time of this post, only two of which are publicly numbered (4.6.5 and 4.6.5.1). It's best to wait a bit for the oopsies to settle down before downloading and committing to your local code repository.

    • Fixes an issue upgrading from older versions of Invision Community
    • Fixes an installer issue in some environments

    Yes, it's progress, but not a fan of the hidden progress.

    train fixing GIF

  4. 34 minutes ago, Andy135 said:

    clearly for the user in question it would be very welcome to know that they can communicate freely without fear of their comments being used against them offline.

    It's your community, and you know it best, yet I'd suggest this is a slippery slope and offers a false sense of security. How do you know that another trusted long term member won't get into a situation with another member, necessitating you to intervene between those two? Or, that this person's ISP will randomly allocate them a new address? Or that this person has a new address every few weeks through no action of their own? Perhaps the IP space they are connected from blocks a large segment of others interested in your community. I would argue that IP blocks are antiquated and should not be used via IPS software, yet in CIC, it may be your only tool available. This type of blocking should be happening at the firewall.

    Making spaces for more closed-knit interaction and giving members tools that empower them to be responsible for their online safety are far better directions to head. Consider using forums that are only available to long-term members, or clubs that members can decide who gets in and who does not. Give members the ability to change their display names. Link to resources that help users understand their role in being safe online.

  5. It seems that if this is a concern for your community, you might consider registration (and being logged in) as a requirement to view content.

    While it's noble to want to prevent someone malicious from seeing content that another person is posting, you'll find that short of controlling who can register and who can see your content, you will not be able to achieve the level of restriction you're seeking otherwise.

  6. While turning it off and on again is a tried and true method of fixing the most dastardly of computer issues, this queries appear to be related to your usage of the ACP and looking at members listings who haven't yet validated. Is it slow in other areas or just here?

    Have you run the support tool in ACP to ensure your database schema is correct?

    Have you looked into MySQL maintenance (ANALYZE/CHECK/OPTIMIZE)?

    https://dev.mysql.com/doc/refman/8.0/en/table-maintenance-statements.html

  7.  

    41 minutes ago, Ocean West said:

    Not that I fear it would happen out of malice or intent but rather by accident or curiosity what happened if a moderator flagged someone as spammer who is a long time member?!

    We have had this happen in the past--accidental flagging of a long term member with tens of thousands of content items. 

    42 minutes ago, Ocean West said:

    I would prefer that this option be only allow to work on  specific groups (newbies) not blankly across all groups -

    This is an excellent suggestion. I believe we made a modification to do just this.

  8. 1 hour ago, usmf said:

    One last question -- when the "Flag as Spammer" button is pushed, does the spam info get shared into the broad online spam prevention, in that way helping more than only Invision customers?

    Yes, this is one of its primary purposes. The data sent to IPS is used by other communities that have enabled the spam prevention service and have elected to use the return scores to address new account registrations.

×
×
  • Create New...