Re: Subpages overwhelms the content

Example:  Turns out my original example was me not understanding the 
form setup correctly.  But, I also noticed when going to check that the 
/html/elements [1] form structure seems odd.  Is the entire table and 
list displayed on that table compiled using the "Print all subpages 
rooted here" check under the Basic Listing Configuration?  Also there is 
a See Also section but nothing is in that section of the form.  Is that 
due to it using a Topic Cluster?  If so then we should find a way to 
improve the usability of these forms and let people know how they work 
better.  It seems to be a pretty intricate system.

As far as touching goes since we can't do a DB query, if we do just 
touch things should we summarize with simply "touch"?  I could work on 
this here and there and make a bug report for it that people could 
hopefully work on during a Doc Sprint and add to the Most Wanted Tasks 
list as something people can just do to help out.  I understand wanting 
them to be organically edited to be brought into the new system, but if 
this is all it takes I think it is worth doing to try and get things 
sorted ASAP.

-Garbee

On 10/31/2012 1:18 PM, Alex Komoroske wrote:
>
>
> On Thu, Nov 1, 2012 at 1:55 AM, Jonathan Garbee <jonathan@garbee.me 
> <mailto:jonathan@garbee.me>> wrote:
>
>     You have made perfect sense to me.  I also found this [1] bug
>     report which is also about the subject as well.
>
>     Something I have noticed though is some of these pages when you go
>     to edit them the content is not shown,
>
>
> Do you have an example of this? I'd like to debug.
>
>     you must go to edit source.  If we just open then save would the
>     content be brought over?
>
>
> Generally semantic forms is /pretty /good about maintaining the bits 
> that don't fit into structured form fields between an open and a 
> save. But I'd like to test that to verify. :-)
>
>
>     If it is really just doing that is there no way to do a DB query
>     of some kind to just set everything the way it needs to be for all
>     articles?
>
>
> Unfortunately, it's a bit harder than that, apparently.  The magic 
> part of the "touch" process is when semantic forms looks at what 
> templates are /supposed /to be on the page and then puts them there if 
> they aren't yet. Semantic forms, in my limited understanding, is 
> layered pretty much just on top of MediaWiki, which of course is 
> layered on top of the database part. So you'd need to do something far 
> more intricate than just working directly with the database. What 
> exactly that would entail, I don't know.
>
>
>     -Garbee
>
>     [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=19348
>
>