Jump to content

Ryan Ashbrook

Invision Community Team
  • Posts

    12,669
  • Joined

  • Days Won

    13

 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 Ryan Ashbrook

  1. 1 minute ago, Clover13 said:

    But only the CF Pro account and domain would do this, not the 2 other CF Free accounts and domains?

    Most likely - on their site, the Pro account advertises that they have blocking / challenging of automated traffic. In most cases, this is simply detecting that the request is coming from an IP from a data center and not an actual ISP (I should know, our corporate VPN gets hit by this all. the. time.).

  2. This would definitely be something server side and / or associated with other software on the server for a few reasons.

    1. While we do use a custom session handler, we use the proper session_set_save_handler and related functions, rather than ini_set.
    2. The only usage of ini_set throughout the software is during an automatic Admin CP upgrade to disable errors, which is a fairly typical use case - and if it fails, the error is suppressed and ignored. This is the case for both 4.16.12.1 as well as the current version.

    Based on the error itself, it looks like there may be a configuration issue somewhere in php.ini, or in a .htaccess file that is present on the server, attempting to set that directive (which is incorrect in itself - the directive is session.save_handler instead, though that could be as simple as the server interpreting the dot as an underscore in the error).

  3. By default, it's 90 seconds. Then it looks at the max_execution_time PHP configuration and will then use that instead, if it's less than 90 seconds.

    Then it looks at wait_timeout in MySQL and if it's less than max_execution_time, it uses that instead.

    Then, it looks at the memory_limit PHP configuration and if it's not unlimited, it takes that into account.

    Then it will run the task as many times as it can until one of the following happens (in this order):

    1. The task indicates it has nothing else to do.
    2. If the task is explicitly told to run X amount of times, it will stop when it reaches that amount.
    3. If it gets close enough to the timeout that it cannot run another cycle.
    4. If it gets close enough to the memory limit that it cannot run another cycle.
  4. You are missing your beginning and end delimiters. Try this:

    /^(fa(-[0-9a-zA-Z]+)+)( (fa(-[0-9a-zA-Z]+)+)+)*$/i

    And then set Apply text formatter to Yes, and then set Formatting Option to All lower-case in case someone enters a valid Font Awesome icon class, but uppercase.

  5. Working with images, particularly large ones, is actually a pretty intensive process. For instance, if I open Affinity Designer, t immediately uses about 750-800MB of memory, then opening a single 1.6 MB file makes memory usage jump to 1 GB. If the files are going to /tmp then it's likely because ImageMagick is running out of memory available to it so it's forced to use disk instead, which has larger space to work with, but is much slower.

    It may be worth contacting ImageMagick with your configuration to see if any improvements can be made.

  6. Any of the following would likely work.

    {{if \IPS\Member::loggedIn()->inGroup( array( \IPS\Settings::i()->guest_group ) )}}
    
    {{if \IPS\Member::loggedIn()->member_group_id == \IPS\Settings::i()->guest_group}}
    
    {{if !\IPS\Member::loggedIn()->member_id}}

    Generally speaking, the third one is the most accepted way of determining if a user is a guest or not.

×
×
  • Create New...