Blaine's dashboard

Thanks for sharing. That's a great service.

Hi,
I tried to use the
Contact The Wiki Owner
and appear to get the visual only captcha. There is a same page link if you cannot read the captcha text, but it does not seem to bring up an audio captcha.

As I posted in another thread, I also cannot figure out how to add a heading level 2 to a wiki using the Jaws screen reader:
http://hj.com/jaws
It appears this can be done either in a WYSIWYG editor or by adjusting the HTML source, but neither of these methods worked.

The wiki I am trying to edit is:
http://twitterpacks.pbwiki.com
and it looks to me like you need to create a heading level 2 in order to add a Twitter Pack to this wiki?

These issues should be resolved more quickly as they pose a critical priority 1 issue in terms of accessibility for content creaters.

I fiddle around with a pbwiki site for my local chapter of the PA Council of the Blind and have had some trouble with the graphic blocker on the 'Contact Owner' feature. I've found a couple of work-arounds that pbwiki might be able to engineer in. One is an arithmetic question such as 2 + 4 = [ ] Enter answer. Another is a 'what's the missing piece' question such as What's missing? abdef [ ] Enter answer. (If you consider this one, please don't make it case-sensitive. That would defeat the whole purpose!!!)
http://pcb-clrfld-jeff.pbwiki.com/
Thanks – Blaine, on July 04, 2008 20:53

what about an email notifcation system that is delivered to the users in a weekly digest?

Ok, so when is Guy Fawkes going to be let off probation?? He just happens to be one of the people I can count on to help me figure things out. I realize he occasionally is critical of pb wiki staff - but maybe you should hire him rather than ban him. My initial feelings about Satisfaction was definitely colored by the fact that he was on line, listening and had a LOT of technical skills.
I'm rather a newbie to the wiki world, don't know why pbwiki is offering everything for free, don't really understand satisfactions relationship with pbwiki, and certainly shouldn't be criticizing a group of people offering the whole thing for free - but to tell you the truth - after I finally started to get the swing of it - I began to wonder. Specifically why:
1) pbwiki does not have a front page which lists the features available
2) do not explain limitations of the website
3) would even setup a wiki in the first place that does not allow you to
a) get rid of the side bar OR add it.
b) does not have a calendar that fills the screen, can change to monthly, weekly, daily view AND have a print feature ???
c) does not have an interactive spread sheet available ??
I mean it seems like these are the basics?? are they not?? and at the very least BEFORE you get people to sign up and spend hours and hours setting up their web pages - that you should note the features and limits it has rather than AFTER the fact. - such as no we don't have that but we're considering it.
As I said, I shouldn't bite the hand that feeds me, but I understand where Fawkes was coming from.
And it's possible I have no idea what I'm talking about. That I don't truly have a perspective on the scope of the problem and that to level ANY criticism at pbwiki is rude, crude and uncalled for. I'm sorry, I don't know where that came from. I am trying to quit smoking. Do you think you could at least have EXAMPLES of web pages to show what is possible?? with a clear explanation of what is not possible. And maybe a "why you should choose our wiki over all the other wiki's"
Thanks for listening,
Sara `
I realize this is inappropriate for this topic - not sure how to introduce as a new topic??

I'm not sure ... sounds like one of two things. PBwiki is hiccuping during the save, or are you inserting the code in the wrong manner? If you are clicking 'Source' after opening the 'wysiwyg' editor, you should be able to pick your spot on the page full of code and insert your code. If you're using the wysiwyg editor then you have to use the Html plugin after placing your cursor on the page where you want the code. If you still have trouble, you may have to make a support ticket and see what the support group has to say.

An easy way to save just the copy of the wiki you want is to use the backup function. Get your wiki to the point you want it, and then got to Settings | Backup and take a .ZIP "snapshot" of your wiki.

This will get you HTML and text files of every page on your wiki in their current state, no history.

Then, you can delete all the pages (which will also delete their history), and then all the revisions of the FrontPage (a lot fewer revisions to delete!).

From there, you can re-create your wiki using the HTML or Text files in the backup you made earlier. Just make sure to name the pages correctly, they're case-sensitive!

How does that sound for a work-around? :)

Best of luck!

I'd just like to have a way to quickly and efficiently clean up after a project is completed, leaving, usually, the final draft, or just one choice draft. If and when possible, I can delete the entire set by simply erasing the page's file name, but that doesn't work when I need to preserve just one example out of MANY. Of course one work-around would be to save the contents and try to save the formatting of the choice page on disk, erase the file name, then reconstitute the example saved on disk to another file later on named the same as the original file so I don't have to change every link to that page on other pages. – Blaine, on May 24, 2008 02:07

Why do you want to delete all or many revisions of a page?

Would a function to restrict who could revert a page to a previous version help? (I think currently this is available to writers and above)

Thank you.

Check out this page - http://kb.mozillazine.org/Editing_con...

It's by Mozilla, so it should have some pretty thourough instructions on how to fix things, but I know it's pretty high-level stuff, as Vu mentioned in the other thread, so try and write down the things you change in case you need to go back.

The trick is to use Blogger's Atom feed of the blog's comments as the data source to the feed page element, or go all-out and write some JS that operates on the JSON representation of the same data.

Ramani at Hackosphere has a good customizable recent comments widget that you should check out.

Sounds like you are trying to force-enable JavaScript. Not sure if we can help you in this section, but maybe I can find someone who can.