Build 926 - Private messages

Continua CI Bugs
1

Private Messages -> View All -> try and "Mark" an entry with the check box.

A new event has been added to the event log: 

Exception: ParseException 
Message: No property or field 'Mark' exists in type 'PrivateMessage' 
Stack Trace: at Continua.Shared.ExpressionParser.ParseMemberAccess(Type type, Expression instance) 
at Continua.Shared.ExpressionParser.ParseIdentifier() 
at Continua.Shared.ExpressionParser.ParsePrimary() 
at Continua.Shared.ExpressionParser.ParseUnary() 
at Continua.Shared.ExpressionParser.ParseMultiplicative() 
at Continua.Shared.ExpressionParser.ParseAdditive() 
at Continua.Shared.ExpressionParser.ParseComparison() 
at Continua.Shared.ExpressionParser.ParseLogicalAnd() 
at Continua.Shared.ExpressionParser.ParseLogicalOr() 
at Continua.Shared.ExpressionParser.ParseExpression() 
at Continua.Shared.ExpressionParser.ParseOrdering() 
at Continua.Shared.DynamicQueryable.OrderBy(IQueryable source, String ordering, Object[] values) 
at Continua.PrivateMessages.PrivateMessageManager.GetPrivateMessagesForUser(User user, Paging paging) 
at Continua.Services.PrivateMessageService.GetPrivateMessagesForUser(String userName, Paging paging) 
at SyncInvokeGetPrivateMessagesForUser(Object , Object[] , Object[] ) 
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) 
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) 
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) 
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc) 
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet) 

2

At the moment we only support sorting of columns that are database backed. That holds true for all tables in Continua that are pageable. The error here is the “Mark” column being marked as sortable when it shouldn’t be. All the other columns are sortable but at the moment they’ve all got either the wrong values or their sorting code on the backend is very wrong. I’ve pushed a fix which will be in the next build.

3

Thanks for the quick fix. I do remember clicking the title by accident.