The answer is here<https://groups.google.com/forum/?hl=en&fromgroups#!searchin/tiddlywiki/teamtask/tiddlywiki/6AfFmFhKbCI/Ht55eIXgnbEJ> I think for the TTReportView error.
If a "task" does not have a value set when created the filters are not robust enough to assume a definition value for the field E.g, in the html code the values for the defined fields may be *tt_scope="Issue" tt_priority="High" tt_user="cflow" tt_status="In Progress" * but if the values are populated like this:* tt_scope="Issue" tt_priority="High" tt_status="In Progress" *where *tt_user** *does not exist AND it has no value I think we have a problem. In your tiddler you have: <<TTReportView DisplayFields:"Title,User,Priority,Status,Scope" OrderBy:"Title,asc" Scope:"Issue" Status:"!Complete">> If any of those fields are not populated with a value I guess the issue starts. I would open each of the tiddlers that are tasks and ensure they have values set. Even if the fields appear to be cleared (outstanding issue!!!) as you set them the values do seem to get populated to the tiddler and therefore the TTReportView error should disappear. I guess if you could set a default value for each field for a new task this error would be non-existent. Not sure how to do that :| On Thursday, May 23, 2013 5:01:52 AM UTC+10, [email protected] wrote: > > I think I found part of my problem. I was using build, 2.7.2 and something > appears to be broken with ValueSwitcherPlugin. > > - The base CFlowTeamTasks uses build 2.5.0 beta 1 and works great > - This version appears to suffer from IE10 / FF20 import from local file > issues. > - This was fixed in build 2.7.1 beta 2 > > - Upgrading CFlowTeamTasks using method found > here<https://groups.google.com/d/msg/tiddlywiki/IZLKHHfewh4/T_WRXNBjHeoJ> > . > - Upgraded to 2.7.2 successfully > - ValueSwitcherPlugin now appears to have issues allowing the user to > select any list definitions > - Upgraded to 2.8.0 beta 1 successfully > - ValueSwitcherPlugin issue persists > > Do you think that may be the issue? > > On Wednesday, May 22, 2013 12:09:15 AM UTC-4, cflow wrote: >> >> I don't think its the theme/skin, the tasks features don't work at all as >> you haven't got fields displaying on the tasks, therefore no selections can >> be made, therefore broken macro! >> >> The reason the macro is failing is due to the values for DisplayFields, >> OrderBy and Status not being available at all in the task records. It looks >> like you just imported some of my tiddlers (and some of the other ideas) >> into a base TiddlyWiki without the javascript work done by Phil >> Hawksworth (which is how the teamtasks things all work), but I haven't >> checked the back-end of your file to see if that's true. >> >> In your file you have the following macro call in the Open tasks tiddler: >> >> <<TTReportView DisplayFields:"Title,User,Priority,Status,Scope" >> OrderBy:"Title,asc" Scope:"Issue" Status:"!Complete">> >> >> >> If you modify it to just <<TTReportView>> you will see that the report >> performs and gathers all items with the "task" tag into a viewable table. >> It doesn't look the same as the standard teamtasks due to differences in >> the CSS. >> >> This is how we all learn though, by breaking it a couple of times :) >> >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
