fix errors that displayed in new workshop detail code

I reinstated the second part of the condition for the workshop id query and created the missing records in workshop to support the landing pages.

This still left the error though.

Then I saw the query, which was only supposed to return 1 field was digging deep into the relationships. So I added another parameter:

'contain' => false

to stop the related data search. That too care of the error.
prepare to manage option-sets for different products

Establish a theoretical framework for an HTML node click to control the mixed visibility of a set of HTML nodes
expand logic for management of option-sets and start framing code

I've chosen to lock in OneMaster->controls->OneSlaveSet to keep server-side complexity down.

Also, to make nameSpace optional.
expand code of management of option-sets

correct major jquery syntax error in use of each()

Create an array that holds the list of eligible Classes for an Option Master node
try to make option-set commenting better
prevent obscure error if nameSpace contains the string 'master'

Contact page provides testing platform for the javascript.

Fix one comment

Fix the selector and regex so the only option attributes with the prefix "master" or "master-" will be detected.

This prevents option attributes that are slaves, in nameSpaces with the string 'master' in them from being incorrectly treated as master nodes.
expand testing platform for options manageement

verifies one-master and no accidental activation on a namespace with string 'master'.

also shows how to construct a slave that is also a master.
bring option-set manager near to completion

build the initializer that hides all slave for all masters on page load.

work out the hide and show processes for the click method.

Write up more test lines in the contact page.

Having slaves that are also masters complicates the page. The slave of a slave/master must be tagged so it will respond to it's master's master also. Otherwise it might be left showing inappropriately.
expand testing page for option-sets

This page allows a more sophisticated testing of the behavior of slaves who's masters are slaves.
update option-set managers comment

Remove the multi use warning.

I tested the substring problem. all is ok.

Explain Slave-that-is-a-Master coding
plan possible option-set manager improvements

add new ideas to the comments