Title: thirdfloor's Replies | WordPress.org

---

# thirdfloor

  [  ](https://wordpress.org/support/users/thirdfloor/)

 *   [Profile](https://wordpress.org/support/users/thirdfloor/)
 *   [Topics Started](https://wordpress.org/support/users/thirdfloor/topics/)
 *   [Replies Created](https://wordpress.org/support/users/thirdfloor/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/thirdfloor/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/thirdfloor/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/thirdfloor/engagements/)
 *   [Favorites](https://wordpress.org/support/users/thirdfloor/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WPS Hide Login] WPS Hide Login not working with Translatepress](https://wordpress.org/support/topic/wps-hide-login-not-working-with-translatepress/)
 *  [thirdfloor](https://wordpress.org/support/users/thirdfloor/)
 * (@thirdfloor)
 * [5 years, 12 months ago](https://wordpress.org/support/topic/wps-hide-login-not-working-with-translatepress/#post-12815478)
 * Yes, I encountered exactly the samen issue.
    I solved it in this way: –> Settings—
   > TranslatePress –> Use a subdirectory for the default language –> No
 * In this way the default language doesn’t redirect to a separate folder, e.g. 
   to yoursite.com/en
 * Hope this helps.
    -  This reply was modified 5 years, 12 months ago by [thirdfloor](https://wordpress.org/support/users/thirdfloor/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[3CX Free Live Chat, Calls & Messaging] Plugin could not be activated because it triggered a fatal error.](https://wordpress.org/support/topic/plugin-could-not-be-activated-because-it-triggered-a-fatal-error-564/)
 *  Thread Starter [thirdfloor](https://wordpress.org/support/users/thirdfloor/)
 * (@thirdfloor)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-could-not-be-activated-because-it-triggered-a-fatal-error-564/#post-11703534)
 * Hello [@dylanauty](https://wordpress.org/support/users/dylanauty/),
 * I just uploaded and tried to activate the version 8.036. However the error is
   still there:
 * Fatal error: Uncaught Error: Call to a member function add_cap() on null in /
   home/k7curtx6/public_html/wp-content/plugins/wp-live-chat-support/functions.php:
   2180 Stack trace: #0 /home/k7curtx6/public_html/wp-content/plugins/wp-live-chat-
   support/wp-live-chat-support.php(3400): wplc_mrg_update_db(”) #1 /home/k7curtx6/
   public_html/wp-includes/class-wp-hook.php(286): wplc_choose_activate(”) #2 /home/
   k7curtx6/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(
   NULL, Array) #3 /home/k7curtx6/public_html/wp-includes/plugin.php(453): WP_Hook-
   >do_action(Array) #4 /home/k7curtx6/public_html/wp-admin/plugins.php(174): do_action(‘
   activate_wp-liv…’) #5 {main} thrown in /home/k7curtx6/public_html/wp-content/
   plugins/wp-live-chat-support/functions.php on line 2180

Viewing 2 replies - 1 through 2 (of 2 total)