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

Forums

Events

Store

Gallery

Posts posted by bfarber

  1. On 1/15/2021 at 11:30 AM, MNOfficial said:

    I checked the error logs within my Admin CP, and there are no errors being reported via the Server Error Log.

    As far as I am aware, I am not using any kind of CDN or Cloudfront at all. It is weird it is doing this for a brand-new PM post, when the previous PMs have more images and commentary than what it being attempted in.

    I meant the server level error logs, which aren't available in your AdminCP and are separate from your php error log. Where they are located will depend upon what webserver software you are using and what operating system you are using typically.

  2. 8 hours ago, m3rk0rd said:

    Thanks!

    I missed that somehow. Interestingly I can find most settings by searching but when I search for “truncate” nothing comes up. 

    Thanks for pointing this out, I've put in a note to have this looked at for our next release.

  3. If you are self-hosted, we recommend taking a backup before applying upgrades as mentioned by @Miss_B.

    It is often a good idea to upgrade a test installation first to ensure there are no compatibility problems before upgrading your live site. That said, as a general rule upgrading between minor point releases (i.e. 4.5.2 to 4.5.4) should not cause you any issues, while upgrading major point releases (i.e. 4.5.x to 4.6.0) should be treated with extra caution due to a higher likelihood that third party customizations such as plugins, applications and themes will no longer be compatible.

  4. This is almost certainly some sort of server issue - unfortunately I couldn't begin to guess what. You may be able to start by reviewing server error logs to see if perhaps an Apache plugin is crashing or something along those lines.

    If you use a CDN like Cloudfront, you may wish to temporarily bypass it for further testing to see if a more concrete error response is returned.

  5. The reality is it's pretty rare that a "corrupted" file occurs with software like ours, outside of when someone is manually uploading files and they have connection issues (i.e. the connection drops mid-upload).

    That said, if this is something that actually comes up we could look at a "reapply files" button for applications in the marketplace. We wouldn't likely do that unless we see material instances of this happening outside of hypothetical situations mind you, but it's not something that's a blanket "no". It is, however, something completely separate from what was originally requested and discussed.

  6. Indeed, the "post before register" feature didn't even exist in 2014 so some of these posts you are looking at are simply posts attributed to a guest, and not specifically posts made by a guest since the new feature was introduced.

    You'd have to look at the old posts to gather some more information really. They could have been made by a user who has since been deleted, you may have allowed guests to post at some point, there may have been a bug in a previous version of the software - it's difficult to definitively give a blanket answer for 209 posts dating back to 2014 on this end I'm afraid.

  7. If you make the request within the client/browser, you need to content with CORS which is designed to allow cross-domain requests to work but also provide protection against javascript-based attacks. Essentially, you'll need to add a few response headers for these requests which is typically done at the server level.

    Postman doesn't run in the browser context which is why it works without an error.

    One word of caution - running any sort of API requests via javascript exposes the API credentials. We'd only recommend using an OAuth-based client for API requests if javascript is going to be executing the API requests, since the permission level will match the current logged in user anyways.

  8. Not exactly accurate.

    The "Allow filtering" option does not control the sort menu, but rather which fields are filterable.

    That said, the filter form does not display by default on the page. What you need to do is open the sidebar widget manager and add a "Database Filters" widget to the list of records page to add the filter options.

    image.png

     

    This will give you the following (taken from our bug tracker here)

    image.png

  9. Sometimes a ticket is the easiest way to diagnose a problem, even if the issue can be duplicated on a fresh install. When you look at the steps necessary to reproduce a problem and it can take an hour to set up your test installation to duplicate the problem, but you already have a live example we can look at, it's often more effective and efficient to look at the live example.

    Support is included with your license and we encourage anyone experiencing a problem to make use of our support.

×
×
  • Create New...