24.2 is the first release in a while to break my site so I'm going to ask for a rollback so I can compare something odd I noticed. 

Stage on 24.2, this query shows 133 results

https://community.DOMAIN.com/api/2.0/search?q=SELECT * from nodes limit 500

Production on 23.12, this query shoe 178 results 

https://community.DOMAIN.com/api/2.0/search?q=SELECT * from nodes limit 500

I can't seem to identify why this is occurring beyond stage was upgraded was working fine yesterday so I'll reach out to support. 

tyw we are also having problems with this release - no nodes are being returned from some API queries that power our custom navigation. Will have to ask Khoros to roll it back from our staging server / hold off on the prod launch.

Update: We rolled back but the LIQL issue persists and whats odd is i can add, and edit new items to the EN category, and have them appear in LIQL, but the other items, that have existed since we went live years ago no longer appear, specific to our EN category only? 

CarolineS , if you roll back, does LIQL still show a issue? 

The Q I'm trying to solve now, is there any setting that can prevent something from appearing in LIQL? As far as I know nothing like that exists? LIQL should return everything based on access of the person requesting and im using admin?

tyw the "Hide from lists and menus" option in a node's properties can do that:

Did you try to just get a count(*) from the nodes collection, e.g. adapt the query you posted above to

SELECT count(*) FROM nodes

Update: I've been able to fix the issue but suspect there's a underlying issue. 

luk , re Hide, thank you! I can confirm this has always been unchecked and during troubleshooting while on 24.2 I did toggle this at the EN root category level - no change occurred.  EN was still missing. 

For a test now, after rolling back I toggled that Hide option on the new category and board I added and verify the node count query updated to reflect the change (counting when shown, dropping by 1 if hidden).

It shows 140 with the new items I added, set to appear. 

I then toggled the EN root category options hide option, saving as checked,, then unchecked and boom - LIQL now shows 220 items which is the missing EN category and content. 

Yay! My issue is solved, but why did this occur when that Hide option has not been used in years in Stage? 

CarolineS , I'd love to know if you see similar results? Toggling hide on, and off after rolling back? 

tyw omg that's it!!! I took a node (which has never had "hide from lists & menus" clicked before), clicked "hide from lists & menus" & saved. It was hidden as expected from OOTB node lists (and still hidden from our custom nav). I then UNCLICKED "hide from lists & menus" for that node, and, lo and behold, it appears on our custom nav.

This is definitely an issue! I do not wish to hide/unhide all of my nodes in order to get the nav to work.

(Edit: This was on 24.2; they haven't yet rolled us back)

Yay! Thanks for the confirmation CarolineS and the 24.2 edit! 

It's only a suspicion, but we have seen issues like that on and off over the years, not even necessarily related to updates, e.g. we don't know the root cause ourselves, but it looks like some internal API caching / aggregation issue which can be "resolved" by triggering certain actions (like hide/unhide) which then "re-generate" the internal cache (or whatever it is)... would be great if Khoros could shed some light on that 😉...

luk tyw CarolineS - Thanks for submitting a support case on this! The development team is taking a look at this urgently. We are investigating the cause and will add more detail once we know more.

CC: BlakeH 

LarryI  there's something similar strange going on when editing robots.txt user rules, the interface in Studio shows the rules "correctly", but if you go to the actual robots.txt e.g. at https://community.yourdomain.com/robots.txt it shows "wrong" entries. This happens if you edit existing rules, or delete existing rules and add new ones. It can be resolved by adding a dummy rule last and then delete that dummy rule again, but it can cause problems if one is not aware of that. I suspect some kind of caching is going on there as well.