Title: undefined variable: StylesString
Last modified: February 21, 2017

---

# undefined variable: StylesString

 *  Resolved [awpt](https://wordpress.org/support/users/awpt/)
 * (@awpt)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/undefined-variable-stylesstring-2/)
 * Im logged in and Im getting this php notice with the following you must be logged
   in messagge
 *     ```
       Notice: Undefined variable: StylesString in /var/www/html/mytheme/wp-content/plugins/front-end-only-users/Functions/EWD_FEUP_Styling.php on line 11
       You must be logged in to access this page. 
       ```
   
 * Do you have any idea! Im working with debug on because Im creating my own theme.
   The notice is not so important but Im logged in and it says to log in
 * **[account-details]**

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

 *  Thread Starter [awpt](https://wordpress.org/support/users/awpt/)
 * (@awpt)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/undefined-variable-stylesstring-2/#post-8831568)
 * Added also a login and registration form to test the plugin but realy many undefined
   idex variables in your plugin
 * `Notice: Trying to get property of non-object in /var/www/html/mytheme/wp-content/
   plugins/front-end-only-users/Functions/Process_Front_End_Forms.php on line 89`
 * another one
 *     ```
       Notice: Undefined variable: StylesString in /var/www/html/mytheme/wp-content/plugins/front-end-only-users/Functions/EWD_FEUP_Styling.php on line 11
   
       Notice: Undefined index: Payment_Required in /var/www/html/mytheme/wp-content/plugins/front-end-only-users/Shortcodes/Insert_Login_Form.php on line 60
       Login failed - incorrect username or password
       ```
   
 * All this php notices are not scure and will effect on server load.There are many
   many other php warning and notices.
    -  This reply was modified 9 years, 3 months ago by [awpt](https://wordpress.org/support/users/awpt/).
    -  This reply was modified 9 years, 3 months ago by [awpt](https://wordpress.org/support/users/awpt/).
 *  Plugin Contributor [etoilewebdesign](https://wordpress.org/support/users/etoilewebdesign/)
 * (@etoilewebdesign)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/undefined-variable-stylesstring-2/#post-8831820)
 * Hi awpt,
 * Thank you for letting us know about the PHP notices. We will have a look at this
   and see if we can remove them in an upcoming update.
 * For the “You must be logged in to access this page” message you’re getting, this
   is when you’re going to the page with the [account-details] shortcode on it? 
   Is this the only place it’s happening? For example, if you place some restricted
   content on a page (i.e. [restricted]Test content[/restricted]) and then log in,
   can you see this content?
 *  Thread Starter [awpt](https://wordpress.org/support/users/awpt/)
 * (@awpt)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/undefined-variable-stylesstring-2/#post-8918345)
 * I will try it again thanks for your reply I was very busy at this time but I 
   realy like your plugin i will test it again and will let you know all.

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

The topic ‘undefined variable: StylesString’ is closed to new replies.

 * ![](https://ps.w.org/front-end-only-users/assets/icon-128x128.png?rev=1805921)
 * [Front End Users](https://wordpress.org/plugins/front-end-only-users/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/front-end-only-users/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/front-end-only-users/)
 * [Active Topics](https://wordpress.org/support/plugin/front-end-only-users/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/front-end-only-users/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/front-end-only-users/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [awpt](https://wordpress.org/support/users/awpt/)
 * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/undefined-variable-stylesstring-2/#post-8918345)
 * Status: resolved