Early parsing update problem
Not 100% sure I have not touched anything else, but after updating to 2.10 early parsed logged-in_member_id seems no longer to function
In Low Variables panel, this and a couple of other snippets are shown with white text against a black background. Anybody else having problems?? 
Replies
Low 30 Mar 2012 07:38
What version of EE are you using?
Can you turn on Template Debugging, then look up the lines that say Snippets (Keys) and Snippets (Values) -- you should be able to see the variables listed there.
Also, are you nesting early parsed Low Variables in other early parsed vars? If so, you might want to take note of the order in which they are parsed: in the same order as they appear in their group.
icebreaker 30 Mar 2012 18:44
1. The version is v2.4.0 - Build: date 20120123
2. I have tested with a template consisting of a single string featuring ---{logged_in_member_id}---, which returns empty together with +++{member_id} which returns 1 which is my member_no.
3. With template debugging on the logged_in variables appear in the key section separated with a pipe . {logged_in_member_id} is the first of these. It is difficult to see where the values are, but there is one section consisting of
" ||||||||||||||FALSE|" which seems the place where the values should appear. They are followed by global variable content and content of EE snippets.
4. The low "snippets" entered in a low variable textarea works as previously - and output is as expected. It seems that the problem is isolated to the logged in member part.
Low 1 Apr 2012 14:31
Looks like you stumbled upon a bug. I can send you a patched file if you want. If so, drop me a note at hi at gotolow dot com.
The bug is fixed for the next version.
icebreaker 1 Apr 2012 22:33
I hardcoded a temporary solution, and will manage OK until the regular update. Thanks for the effort.
I am glad I can hold on to Low early passed variables - they make life simpler.
Low 2 Apr 2012 13:36
Version 2.1.1 should take care of this.
icebreaker 2 Apr 2012 19:19
Tested 2.1.1 against pages where the error occurred. They now pass, and everything seems back to normal. Problem solved. Thanks.
Low 3 Apr 2012 07:39
Excellent.