cnilsson

Thanks for the feedback on this feature. Your insight proved to be very valuable in designing this upgrade.

Version 1.6 is now posted and should provide the features you need. Let me know how it works out for you!

Sitting down to work on this idea and the architecture brings up a few questions…I’ve never thought about using the library this way so I thought you might be able to provide some insight.

The default WordPress roles are hierarchal. Each one progressively adds additional capabilities on the site while keeping all the capabilities of “lower” roles. The Members plugin lets you add additional roles and assign those roles a custom set of capabilities allowing you to create non-hierarchal progressions…ie a role that can add users but not post.

You propose to create a number of new roles that would all have the basic WordPress capabilities. In effect they will all be the same as the default WordPress role “subscriber”. Your goal in the new roles is not really related to WordPress features but rather content access. This makes a lot of sense to me but the lack of hierarchy is challenging.

Let’s say to create the following roles:

Freshman

Sophomore

Junior

Senior

Normally if you assigned content to be visible to the Sophomore role I would expect Juniors and Seniors to have access as well based on WordPress’ hierarchal model. But, in this case it would only be visible to the Sophomore role because the Junior and Senior role are not really higher than Sophomore…they are just different.

To solve this in a content delivery/restriction model like you are proposing for the iCafe Library we could deal with this two ways.

Method one:

Content can be assigned to multiple roles. At the content level you would be presented with a list of all the roles you have created and you simply check all that have access.

Method two:

Content can only be assigned to one role. You would need to create more roles this way (Freshman, Sophomore, Freshman_Sophomore, etc)…I think management would be difficult this way.

My goal is that when someone “graduates” from Sophomore to Junior they don’t lose access to all the Sophomore content. I personally think method one is the way to go…

My last question…I’m assuming it’s at the “book” level that you would be granting access…not the chapter or section level…

Thanks for your input,

Chris

Still struggling with this. Does anyone know of a way to hook into the default WP search??? This seems to be a poorly documented area…

Aegis, I’m glad you like the plugin!
When you paste text into a web based editor all formatting is lost unless the editor has a “paste with formatting” feature like paste for word or similar. Right now, the iCafe library plugin does not have this type of editor…it only has simple text boxes.

Options:
The plugin does support HTML tags. If you know HTML you can format your text within the description field.

Example from your text above

<b>Trigger Control 1*</b>
<br /><br />
<i>Dry fire preparation procedures:</i>
<br /><br />
<ol>
<li>Ensure your responsibilities are taken care of (email, phone, other people), and you can reasonably expect fifteen minutes of uninterrupted time.</li>
<li>This will show up as number 2 on the list</li>
<li>This will show up as number 3 on the list</li>
</ol>

Option 2 still involves HTML but you could use the WordPress “Paste from Word” feature to create the HTML for you. Just create your formatted text in a desktop publishing program, copy the text, create a new WordPress page/blog (you won’t actually save it), paste your text in using the “Paste From Word” feature in the visual editor. Then click to the text version of the editor and you will see the HTML that WordPress created to represent your formatting. Copy/Paste that text into your description. It’s a round about way, but it avoids needing to know any HTML.

I wouldn’t be scared of learning some basing HTML formatting however…it is very straight forward.
Tags tell the browser how to display the text. Tags open and close.

<b>This will be bold</b> but this will not because the "b" tag was closed
<i>italics</i>
</br>
line break (this tag does not need a closing tag...it is self closing)

The UL tag is an “unordered list” or bulleted list. The “LI” tags inside of it are the list items.

<ul>
<li>bulleted list item</li>
<li>bulleted list item</li>
<li>bulleted list item</li>
</ul>

A “OL” or ordered list is the same but with numbers instead of bullets

<ol>
<li>Item One</li>
<li>Item Two</li>
<li>Item Three</li>
</ol>

Hope this helps!

Savarah, here is what I’ve found so far.
Jquery UI issue

I’ve traced to problem down to the JQuery UI Library. If I use version 1.8.9 the flash of white is gone but there are some broken styles in the accordion menu. If I include version 1.9+ then my plugin looks correct but the flicker returns. I’m going to keep investigating but in the end, I may just have to rewrite the broken styles to use version 1.8.9