[resolved] Can't access wp-admin (8 posts)

  1. barnabasnagy
    Posted 1 year ago #

    I'm getting more and more bugs on this plugin!

    Today I tried to access wp-admin for my sites and it would not work. This is what I can see: http://easycaptures.com/fs/uploaded/718/9838890782.png

    Could you please fix this?


  2. Luke Carbis
    Plugin Author

    Posted 1 year ago #

    Hi barnabasnagy,

    Do you know which version of Stream you are running? Have you done any updates recently, and if so, from which version? You mentioned sites, are you running multisite?

  3. barnabasnagy
    Posted 1 year ago #

    I'm running multiple single wp installations.
    Deleted the plugin and installed again as suggested in my other topic. So it's now Version 1.4.3 - it has not resolved this issue. Still can't access wp-admin

  4. barnabasnagy
    Posted 1 year ago #

    Would you please advise how to resolve this as this is getting really annoying!

  5. Hi barnabasnagy,

    I know how frustrating it can be when stuff like this happens, hopefully I can help. Looking at the errors you posted in your screenshot (thank you by the way), another plugin you are using is setting the WordPress user object property caps to null. We had this same problem with W3 Total Cache when the new relic setting is active.

    Could you please provide a list of the other plugins you are using. You might have to disable all of them and re activate one at a time to determine the culprit. Thanks for your patience and the report. It is very helpful for us as we want Stream to be compatible with as many combinations of other plugins as possible.

  6. barnabasnagy
    Posted 1 year ago #

    Hi Chris,

    I have 11 sites, with different plugin combinations. Here's one of them:


  7. Thanks for the list. I'm going to go through them. At first glance it could be multi author restrictions but I can't find the code for that plugin anywhere.

  8. barnabasnagy
    Posted 1 year ago #

    That's a custom plugin developed by my developer. But it looks like this issue has been resolved. I do not get the error any longer.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Stream
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic