2.2.6b2 has expired now.  Got another? :-)

Thanks!

We're focusing on getting 2.5.3 wrapped up right now, but after that 2.2.6 will be up. I'll post a new beta shortly.

2.2.6b1 has expired.  Any timeframe for release?

Sean

When 2 or more instances of the plug are shown in the sidebar, manipulating inspectors controls for one, cross-couples to the other(s).

As before, this ONLY occurs on the page being edited.  Switching to another page, or "reloading" the current page, brings it all back into proper display.  Also as before, export & publish work perfectly.

I'll be sending an email shortly, with a link to download the working plugin, so you can see what's happening.

Sean

I've got this issue figured out.  It was due to a combination of things:

1) because some designs use "!important" on list rules, I also had to use "!important" to override them

... in combination with ...

2) declaring HTML elements with multiple CSS classes

eg. an <LI> element with both "classA" & "classB" styles.  If the generated CSS was a rule for "classA" with a "!important", then later changed to a "classB" via inspector, the view would not immediately override the "!important".  This is what required the page change/refresh to re-render.

I've rewitten the HTML elements w/single class, and it works fine now.  It did need more specificity to some of the CSS strings too.

Thanks for your help!   Sean

Following up from the other thread:  I've implemented 2 placeholder strings, (via -(NSString*) placeholderString;).  They do work, but there's one rather bizarre behavior:

With a placeholder active:

I can switch from "sidebar" to "inline" and back all day long, and they render.
I can switch from "sidebar" to "callout" and back all day long, and they render.

But, if I switch from "callout" to "inline" it fails to render: the outline is collapsed. NSLog entries show that the placeholder string IS being set & invoked.

Just as with the CSS images, if I change to another page in the Site Outline, and then back, it DOES render.  I don't know what to make of this, unless it is also related to the same cause as the CSS inherited images not immediately updating.

Sean

If you can send me a plug-in that demonstrates the problem, I'll have a better chance of debugging the problem :)

Will do.  Do you want the source, or just the compiled plugin?

Either way, it will be tomorrow or after. I've got a lot of non-working code to clean up, from attempts to work out the "index" plugin issues I've come across, and have to run off early today.

Where to send it?

Thanks!  Sean