Jump to content

Clover13

Clients
  • Posts

    1,418
  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Forums

Events

Store

Gallery

Posts posted by Clover13

  1. 4 minutes ago, Jim M said:

    Was that image uploaded before or after a change there?

    Nothing changed in settings.

    Been running the latest version of InvisionCommunity 4.7.4 for awhile now.

    The one change today was moving servers by my host, but I wouldn't think that would influence it as it was a full backup and restore on the new server.

    Also quite a few pictures were posted in the same topic post (by OP) and some thumbnailed while others didn't.

    Here's an example of one that thumbnailed but didn't have that 216px width set

    <img class="ipsImage ipsImage_thumbnailed" data-fileid="157995" data-ratio="66.70" width="1000" alt="xxxxxxxxx" data-src="xxxxxxxxx" src="xxxxxxxxx" style="height: auto;" data-loaded="true">

     

  2. Not sure where there is a setting that drives this, as I thought the post settings state a maximum image dimension and anything larger gets resized to it.  Somehow it seems some are being resized in a topic while others aren't (same topic post, same poster).  The only place I see thumbnails mentioned is in Gallery settings and these aren't in or from Gallery but rather direct uploads to the forum topic.

    Example de-ided with xxxxxxxxx

    <img class="ipsImage ipsImage_thumbnailed" data-fileid="157996" data-ratio="66.67" style="width:216px;height:auto;" width="1000" alt="xxxxxxxxx" data-src="xxxxxxxxx" src="xxxxxxxxx" data-loaded="true">

     

  3. On 11/14/2022 at 4:57 AM, Marc Stridgen said:

    Glad to see that reduced the size. Please also check in Support (top right of your admin CP) and ensure you address anything under the mysql section. We do tend to see less issues like this (although it is indeed a hosting issue) when people are using INNODB that is recommended. I'm wondering if you may not be in your case

    Support checks were all clean.  And MariaDB was setup to use INNODB for the InvisionCommunity tables.  Wonder if it's our heavy usage of Activity Streams that contributes to that particular table sizing if they are related?

  4. Addendum, core_search_index is around 5GB+, which isn't particularly large but it does account for more than half of the DB storage and seems to be growing at an incredibly fast pace while activity grows at a much slower pace.  This was particularly noticeable from the last few upgrades where the size of this table has nearly doubled to tripled in the last 9 months to a year. 

    The next largest tables are:

    1. forum_posts at 741MB
    2. core_reputation index at 448MB
    3. core_follow at 99MB
  5. 1 hour ago, Jim M said:

    You would need to look at the database to determine which tables these are. If it is your log tables, you will need to review the logs to see what is happening and correct the issue.

    It appears core_search_index is the culprit.  What would cause it to be more than half of the DB size?

  6. 4 hours ago, Marc Stridgen said:

    There was some issues with the license server yesterday, which may have meant your license was showing as an issue .This would in turn mean the spam service wasnt working at that time, but should be working again now

    Ok thanks Marc.  Seems to be ok now! 

  7. What is the $form reference in the following code for streamWrapper?  I have one site showing the streamOverview blurb and another that isn't but unclear what setting is influencing this?

     

    <div class='ipsFlex-flex:11 sm:ipsMargin_bottom:half'>
      <h1 class='ipsType_pageTitle'>
       <span data-role='streamTitle'>{$stream->_title}</span>
      </h1>
      {{if $form}}
      <p class='ipsType_reset ipsType_normal' data-role='streamOverview'>
       <span data-role='streamBlurb'>{$stream->blurb()}</span>
      </p>
      {{endif}}
    </div>

     

  8. 11 minutes ago, Jim M said:

    With the account provided, I am not seeing any issues. However, the only content I see is by the individual who you are logged in as and as you have "Members can react to their own content?" disabled, you would only be able to react to other individual's content. You will want to either enable the setting mentioned or create content by someone else to test reactions.

    You would still see it however even if you couldn't react to it yourself no?  Do you see the reactions available to select?

    Hmm apparently that was it, I had thought you could always see the options you just couldn't cast one.  Thanks Jim, sorry to waste your time on that one!

  9. I figured it out, thanks Randy, your links helped spark where to look.  It came down to the S3 permission sets for those objects (certain images files) were not set to public read.  Also the favicon.ico did not move over in the S3 Storage Location usage, however it was referenced by it (i.e. tried to pull from CDN/S3 but was still local on my server).  Not sure if that is a bug, but I just moved it over manually to S3 and set the public read access on the object.

×
×
  • Create New...