spherical

This doesn’t have anything to do with PollDaddy, or at least it isn’t related in all cases. I’m not running it.

Exhibited behavior is reproducible on front page; shows Shave/Save panel where Subscribe panel should be.

Go to a full post with “Only show the menu when the user clicks the Subscribe button” checked and it shows the Subscribe panel. Go to another page/site/whatever, come back. Subscribe button now does not respect the “Click to show” directive and displays the Share/Save panel upon hover.

Leave “Only show the menu when the user clicks the Subscribe button” unchecked and the post Subscribe panel acts the same as it does on the front page; displaying the Share/Save panel upon hover.

On Pages, it works as it should.

A tiny bit later… Well, now I don’t know WHAT is going on. I went back through to check that I am reporting things above accurately and the whole thing works everywhere as it should. What the…? Only thing that may have triggered something was that I checked the operation on a Page. After that, it’s working. ???

That seems to be it, yes, although I’m not exactly certain what’s going on. The stripping happens whether the Visual Editor is enabled/used or not.

Okay. Going back in and re-enabling the Visual Editor yielded these results:

Switching back and forth between the two still changes some code.

hex color shortcut #eee gets lengthened to #eeeeee
margin:1px 1px 1px 1px; gets shortened to margin: 1px;
(I get that this is all that’s needed in real code–this is a test)
[caption]…[/caption] gets totally nuked
some <p>…</p> tags get stripped — not all — no idea why

I, like others who are comfortable with code, am reverting to Visual Editor disabled. It’s still broken after all these years. :/

BUT, the Visual Editor did not alter the hex #eee to rgb(238, 238, 238) which is what seems to trigger the stripping of the entire inline style specifications upon saving.

Thanks! Some additional info: when the first instances occurred, the Visual editor was available. Remembering some posts that said going back and forth between the HTML and Visual editors can mess up your code (why?), I work only in the HTML editor but Visual was available. When all of the stripping was happening, I disabled the Visual Editor to see if that made any difference and left it disabled. For the AtD re-install to get some data for you to work with, the Visual Editor remained disabled. Perhaps this may be a contributing factor to my being unable to reproduce the complete stripping of all specifications within the IMG tags (not just the changing of hex to RGB and subsequent stripping of only the inline style) that I had seen happen previously. I’ll make some tests going back and forth between the two editors; leaving AtD disabled, to see what happens.

Nope. FireFox 3.5.6. Only open stuff in IE6, 7 & 8 to debug code.

The text and link show up on the front page, just as they do on the permalink page, but the drop-down slider only opens one blank line’s worth, where there should be two complete series links. I only get a 3/16″ tall round-cornered white box with nothing inside. It momentarily tries to open farther but then shrinks back to the 3/16″ height.

>”Does the plugin homepage mention a shortcode? Nope.”

Didn’t say that it did. Not appreciating the assumption or the tone.

All I am asking is if there is a way to get one to work, because I see references _to_ them in the code, as outlined above, and wondered if I missed something. Also found the recentIn in the dev version but the mention of it in the readme wasn’t complete enough for me to get it to work. (tried: [recentIn series”my-series”] but no joy)

I deactivated NospamNX for that very reason, myself.

Thanks for the reply.

The author would do well, instead of fixing this ‘feature’, _make_ it a feature and write another version that is MU aware. That, or put in a switch to turn on site-wide for a particular widget in a particular location; leaving all others to cache/refresh at their own rates individually.

In order for this to work you’d only set the cache time equally for the one widget in all blogs and leave the time field empty (turns off caching) in all others that you don’t want to appear in all blogs with the same content. So, you’d set the time to something relatively short and any updates would refresh at the specified time, updating them all. Pretty cool, though not what was intended at first, I’d wager.