Title: Warning: Illegal string offset
Last modified: July 27, 2020

---

# Warning: Illegal string offset

 *  [dougc16](https://wordpress.org/support/users/dougc16/)
 * (@dougc16)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/warning-illegal-string-offset-35/)
 * Hi
 * I recently installed the ‘Who’s Logged In’ plugin but I get the following message
   displayed on the top of the screen.
 * “Warning: Illegal string offset ‘wli_auto_kick_inactive_users’ in …../New_WordPress/
   wp-content/plugins/whos-logged-in/whos-logged-in.php on line 202
 * I’ve disabled the plugin until a solution is found.
 * The system information is as follows:-
 * WP Version: 5.4.2
    WP Memory Limit: 256 MB WP Debug Mode: No WP Cron: Yes Language:
   en_GB PHP Version: 7.3.20 MySQL Version: 5.7.28 Plugin Version: 1.3
 * How do I solve this problem?
 * Many thanks
 * Doug

Viewing 1 replies (of 1 total)

 *  [dphoenix](https://wordpress.org/support/users/dphoenix/)
 * (@dphoenix)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/warning-illegal-string-offset-35/#post-13354295)
 * I’m also getting the same error msg “Illegal string offset ‘wli_auto_kick_inactive_users”

Viewing 1 replies (of 1 total)

The topic ‘Warning: Illegal string offset’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/whos-logged-in.svg)
 * [Who's Logged In](https://wordpress.org/plugins/whos-logged-in/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/whos-logged-in/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/whos-logged-in/)
 * [Active Topics](https://wordpress.org/support/plugin/whos-logged-in/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/whos-logged-in/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/whos-logged-in/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [dphoenix](https://wordpress.org/support/users/dphoenix/)
 * Last activity: [5 years, 8 months ago](https://wordpress.org/support/topic/warning-illegal-string-offset-35/#post-13354295)
 * Status: not resolved