jac2's dashboard

Got to agree with you here. I would like to see a text box on top of the links which would allow you to input a keyword which would dynamically filter the list of links

jac2 -- That's exactly what I was hoping for. I'm thinking since the Files box already has a "Browse" text entry-esque box, there would definitely be room for one on the Links page... Please, oh, please!

I posted another thread before finding this. I thought an edit you type into and it does an incremental match anywhere in the list of pages, so you start with the full list and as you type the list shrinks

When you create a link that has an external URL, a new tab appears above in the box allowing you to specify opening in a new window. Hurray! (Although if we were following this topic shouldn't we have received a notification? Hm..

It would be nice in the box where you specify the type of link if you could just check an "open in new window" option. It's a lot of work doing every link through plugin or editing the source code.

Hi Jason - I'm not able to replicate this issue. Is this happening on all your links or just one?

I had this same problem too. When I looked at the CSS in Firefox Web Developer, I saw that the PBWiki stylesheet had a number of declarations that were not in the stylesheet for the Minimalist skin.

They all start with: #displaycontent div.sidebar_v2. When I added them to my custom css with my settings I was successful in styling my sidebar.

I am remember that bit of CSS now. With !important, if two identical selectors are used, then the last !important gets priority.

http://vupublictest.pbwiki.com/CSSExa...

And you're right, as a skin-designer and web-developer, Firebug has saved my life many times. Too bad IE doesn't have anything as useful.

Vu,
As I should have said, I am not an CSS expert, in fact trying to debug the issue on mine was my 3rd foray into CSS.

See https://vs1.pbwiki.com/common_both-v0...
which I am pretty sure is before my CSS. Notice the "important" overriders. I am right in saying the first one it hits sticks aren't I?

Also see thread: http://getsatisfaction.com/pbwiki/top... toward the bottom.

My advice would be to use firefox + firebug and see what css attributes are being enforced and by which CSS.

Actually jac2, I don't think I've seen !important being used in our built-in CSS very often. It's more likely that a complex order of cascades is going on and the most simple version of a declaration won't work. For example, let's say PBwiki defines h1's like this (I actually don't remember, and it's different for each skin anyway):

#wrapper-root #root div#displaycontent h1 { color:green; }

For you to get the header changed to red, you'd have to be AS specific, or MORE specific. Otherwise, this declaration would get precedence. For example, even the following would fail:

#wrapper-root #root #displaycontent h1 { color:red; }

You would have all the same steps, but since you did not define the element type for #displaycontent, it's not as good.

Furthermore, a problem where the blame is with us a little more is when we link our CSS after the user CSS, allowing our's to have the last say. For example, if we did something like:

<link href="/f/wiki.css" rel="stylesheet" />
<link href="sidebar.css" rel="stylesheet" />

Even if you DID get the declaration with the right priority/specificity, we would still be overriding it. So that's why with any user skinning, if you are having trouble, the best bet to try first is to use the !important keyword yourself, since we use it sparingly if at all and you can then override the built in styles.

Sorry for the longwindedness!

Most sites use the link tag's "title" field as a hover tip, such as:

<a href="http://pbwiki.com" title="Create a wiki!" >PBwiki</a>

Example: http://vupublictest.pbwiki.com/LinkHover

This sounds like a problem I reported ages ago. It was that somewhere in the nested CSS's used by the developers of PBWIKI they had used an "important" tag, which AFAICS stops the property from being modified by later CSS's. My problem was that I couldn't change "Header1" font size and weight. It worked fine in the CSS editor, but ignored in the live WIKI.

After a lot of digging around and using firebug to work out what effective CSS was actually effecting properties I got to the bottom of it. Reported, but still a problem on our V1 wiki.

Not sure it if is the same, but sounds similiar.

Tim- this is great! Thanks for pointing this out :) – Rachel Pennig, on June 10, 2008 17:58

jac2, since you said that you have a private wiki so can't let google in.. what you can do is use the google search appliance.

http://www.google.com/enterprise/gsa/

I've worked at a few places where we've used the google search tech to crawl our intranet (not data that's on the internet) and get good search results back from that.

Perhaps that would help you out?

We're looking at ways to improve our search engine. Currently, wiki searches are exact word searches.

If you have a public wiki, you can install a Google Search bar for your wiki, instructions here: http://newfaq20.pbwiki.com/How+do+I#a...

So stay tuned, we're going to be improving this soon!