CSS tags not working in Pbwiki 2.0

uh, why don't u try add style code into that HTML plugin thingie?

that doesn't work either. I am not trying to be rude but is this an attempt to make users pay to get that custom css support?

I found the notice about css in Pbwiki 2.0 (http://pbwiki.com/content/pbwiki-2-us...)

...Custom CSS? We've added the ability to insert arbitrary code to the header of your wiki. This is useful for inserting things like Google Analytics or custom CSS. However, this differs from how we used to implement custom CSS. Note that PBwiki 1.0 users with custom CSS won't be able to transition their custom designs to PBwiki 2.0. We apologize for the inconvenience.

I can't see how to do this in the beta version. Could someone from Pbwiki please comment.

I think Seanmac's actual question for PBwiki is "how do I insert arbitrary code in the header of my 2.0 wiki", as claimed in the link he posted?

I think the real question here is: why is PBwiki 2.0 mangling up my code in HTML plugin? This used to work in a previous beta incarnation ... not anymore, indeed!

Between the spotty support for JavaScript (like the entire incredibly useful widget.pbwiki.com library failing) and the lack of custom CSS, I really hope that PBwiki keeps 1.0 available for a long time...

I'd love to see someone implement a page like http://cayamo.pbwiki.com/sort in 2.0...

Maybe the Easter bunny will bring us an answer as to why Pbwiki 2.0 strips out our Javascipt and CSS code??

I believe they stated in another thread that FCKeditor (I love that name) can't handle it. Apparently, a javascript editor gets confused by javascript. It's a shame they don't have some sort of text editor...

hm, where's that statement? it used to work in a previous incarnation, now every script, style, iframe & what else between < and > in HTML plugin is gone into hypespace 2.0!

I can't find that exact thread right now, but, since I have had some of my own posts deleted in the last few days, there's no telling what else may have been altered or deleted without notice.

I did find this thread, where they claim "security concerns", but there's nothing you can do with a raw tag that you can't do with the same tag inside the HTML Plugin, so that's possibly not correct. I'm sure one of the 20 people "listening" will begin "participating" in this conversation real soon now.

JavaScript and CSS are both working as of a few minutes ago. Go to "Custom HTML" under Settings. Yippee, PBwiki engineers!

Don't get ur hopes up, yet! The feature ur talking about is different: insert custom style and/or javascript code into head section of every wikipage, possibly a paid feature.
Here we're discussing the lack of writing arbitrary code into HTML plugin on a single wikipage.

I'm not worried about it possibly being a paid feature, since I have no problem paying for tools that make it easier for me to do my job. As far as not having a page-by-page customization... I can see how that would be a problem, but I suspect PBwiki will take a look at that once 2.0 is stabilized.

Good news! We are working feverishly to get the Widget Library working under PBwiki 2.0 (provided they let us, of course). There's more information over at the Widget Library wiki, so pop on over there and see what you can do to help!

Right, been off for Easter and glad to see some progress has been made. I don't know if I am one of the lucky ones to have been given the slide but I can insert style and script tags directly into the HTML of my pbwiki 2.0 page. However, I can't get the page to save to see if it works properly. Good news that the plugin is accepting css and scripts but the 1000 character limiltation prevails which makes the plugin redundant from my point of view. Great news that the widget librarly is been actively converted to work with pbwiki 2.0. I'll be signing up to that initiative and I would encourage everyone else who reads this thread to do the same. It is an awesome resource. Questions still remain though.

1. Why can I not save a page which I have added style and script tags to?
2. When will the plugin capacity be increased?
3. What is the story about this new feature that allows you to insert arbitrary code into the page header?
4. What the hell is going on with the CSS in pbwiki 1.0/2.0 this morning?.........
and finally..........
5. How many Easter eggs did you get? It was a bumper year for me with 3. That is a record! :)

Good news/Bad bad news

Styling is back and I can now save pages. However, saving strips the styling tags so back to square one. CSS is applied in the edit window but not in the view. Plugin doesn't accept css either.

"From a best practices standpoint, it's probably better to try to avoid page-based CSS anyway, and to use classes to handle individual cases."

So, if I want to turn off the display of the sidebar on one page, or a subset of pages, could you please explain exactly how I would use classes to handle that individual case? An example would be nice.

Hey, vangispen! I found that post I was referring to right here.

Superb. I have had a play and it works a treat. This was important to me. This is a much neater solution than inserting style and script tags in the page.

Many thanks