Forum Discussion

keithkelly's avatar
2 years ago

Select * from Categories (returns 0 categories 🤔)

I filed a support ticket, but as I frantically debug Stage, I'm curious if anyone else is seeing the same thing recently - or if any of you have seen this problem in the past. 

Notable problems:

  1. "select * from categories" returns 0 results.
  2. "select * from nodes" returns 2 results
    1. one forum
    2. the community node itself

PS this only happens on Stage at this point. 

 

The basics seem to check out fine:

  • Ran from an adminstrator account (or any role actually)
  • Categories aren't hidden from lists or menus
  • Boards within categories aren't hidden
  • Verified user-inherited permissions apply (in my case all inherited permissions are colored purple)

 

Practical implications:

  1. Our header menu structure doesn't show (Header nav v3)
  2. A volunteer developer is confused
  3. And now I'm confused

 

This may be a red herring, but I saw the Super Mario Movie tonight, and all fingers of speculation point right to the koopa troopas.  Nothing tangible though.

Any ideas or pointers?

  • Occasionally our staging site gets into a weird state and needs a restart. 

    Whenever I see odd behavior on staging (e.g. nodes I moved not moving, new nodes not being created or giving weird error messages, unexpected results from API calls) I ask support for a restart and it generally helps.

    Or it could be the koopa troopas 😄

3 Replies

  • What version of Khoros is you stage on? Not seeing it in 23.2.

  • Occasionally our staging site gets into a weird state and needs a restart. 

    Whenever I see odd behavior on staging (e.g. nodes I moved not moving, new nodes not being created or giving weird error messages, unexpected results from API calls) I ask support for a restart and it generally helps.

    Or it could be the koopa troopas 😄

  • keithkelly's avatar
    keithkelly
    Leader
    2 years ago

    This was essentially it.  Per Khoros Support, they had an indexing issue & they resolved it on their side.  It sounds like it was only an issue with our environment and probably won't affect others.