Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Forum: Requests and Feedback
    In reply to: Security

    Thanks for your reply.

    Forum: Requests and Feedback
    In reply to: Security

    For security reasons, I was wondering if the Core Wp Software could treat the username/userID/loginname in the same manner as it does the passwords? I was wondering if it could be set up so that on the first login of a new user, including the admin accounts, you are instructed to create a ‘nickname’ and if desired ‘first’ and ‘last’ names as well, then the user must select which of those entries or combination of first and last names is to be used for front-end publicly visible stuff like ‘author pages’ or ‘posted by’ or the name displayed in wp chat plugins etc.etc… so the actual login name NEVER becomes publically visible just like the password? It seems like we’re essentially giving hackers half of the puzzle before they even get started by allowing this…am I right, or super paranoid wrong on this?

    Using WP 3.4.2

    Before updating to the latest version of Google Analyticator 6.3.4 I was seeing an error message in the widget area (There was an Analytics API service error 400:Error fetching OAuth2 access token, message: ‘invalid_grant’). So I figured there was probably an update available and sure enough there was.

    After updating and granting access, the site wouldn’t load properly. I had to disable the Google Analyticator widgets in all my sites because it breaks the theme right at the point the widget is supposed to load. This prevents the rest of the page from loading. On one site, that was a real problem because it prevented admin login so I had to delete the whole plugin folder on the server by FTP.

    I also tried using the “Twenty Ten” and “Twenty Eleven” themes just to be sure it wasn’t my Artisteer Themes and they broke too!

    After removing the sidebar widget from the sidebar, everything seems to be back to normal and working properly. I simply dropped it into the “Inactive Widgets” area to save the settings. Just to make sure nobody get’s confused, I did not disable “admin dashboard widgets” from the GA settings page.

    Thread Starter kf4tvi

    (@kf4tvi)

    @mandywhite – I was using version 1.6.6 when the problem arose (Jan4). I installed version 1.6.7 that day (Jan5), when it was pushed to the WP repository and yes everything seems to work properly now.

    And I agree, kudos to the developer for staying on top of things and continuing to update this useful plugin.

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