Jump to content

Nathan Explosion

Clients
  • Posts

    6,915
  • Joined

  • Days Won

    127

 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 Nathan Explosion

  1. Here are your reproduction steps...

    1. Login to a site
    2. Logout
    3. Change your IP address
    4. Login to the site again, ensuring same browser and account
    5. Set the "Remove IP addresses after" setting to whatever you want (I believe the minimum is 1 day)
    6. Wait that amount of time, then run the task.

    To reproduce it quicker, you're going to need to manipulate database records to change the last_seen value to meet the criteria.

    Potential fix: modify that primary key to include the last_seen value.

  2. Reporting it as it just occurred on my live site...

    UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses`  SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709136738
    IPS\Db\Exception: Duplicate entry '0138fdaa72c8135e62b3487f5be7b11d-2970-' for key 'PRIMARY' (1062)
    #0 /home/fbaeefdf/live.ynwa.tv/system/Db/Db.php(1159): IPS\_Db->preparedQuery()
    #1 /home/fbaeefdf/live.ynwa.tv/applications/core/extensions/core/IpAddresses/Logins.php(33): IPS\_Db->update()
    #2 /home/fbaeefdf/live.ynwa.tv/system/Member/Member.php(6504): IPS\core\extensions\core\IpAddresses\_Logins->pruneIpAddresses()
    #3 /home/fbaeefdf/live.ynwa.tv/applications/core/tasks/pruneipaddresses.php(43): IPS\_Member::pruneAllLoggedIpAddresses()
    #4 /home/fbaeefdf/live.ynwa.tv/system/Task/Task.php(281): IPS\core\tasks\_pruneipaddresses->execute()
    #5 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run()
    #6 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask()
    #7 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute()
    #8 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute()
    #9 /home/fbaeefdf/live.ynwa.tv/admin/index.php(13): IPS\_Dispatcher->run()
    #10 {main}

    I believe this is a knock-on effect of it NOT having been pruning the IP addresses correctly previously - the issue you'll have is that there could be multiple entries for a specific device_key and member_id, but with different IP addresses. Now that task has been fixed to do the pruning, when it tries to remove the IP address on those multiple entries, the PRIMARY key for each row will end up being the same as the key is made up of device_key, member_id, IP address (which is now blank)

    Sample content attached:core_members_known_ip_addresses.sql

    When the query in the task runs against that data, the error occurs:

    UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses`  SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709135288

    Could contain: File, Page, Text, Webpage

     

     

  3. GBoard is the default keyboard of the Google Android OS (it's on Pixel devices, it's on most OnePlus devices, plus others that don't massively deviate from the stock OS)

    'Samsung Keyboard' is the native keyboard on the Samsung version of the Google Android OS, but can be overridden by the manual installation of GBoard from Google Play, just like SwiftKey is available for all Android devices.

  4. First mention of filtering there, so wasn't aware it was a requirement. If it is then crack on with a Pages DB - you then have to figure out how to keep that data up to date, and when to do it. Alternatively, look at IPS\Helpers\Table\Custom to allow you to create an table based on an array datasource instead of a DB table.

    With all this in mind, I'd now advise you to look into developing an application to do all this instead...

    1. You can design your own table to store the data
    2. You can create a module/controller that will display that data, and add filtering on there easily.
    3. You can create a task that runs on a schedule to retrieve/store/update the data.

    Not much more to add really - if I knew what this mysterious API was, and where it was getting the data from, and what the data looked like then I might even get bored and throw together a POC of it.

×
×
  • Create New...