RoyalKnight's dashboard

Nathan Schmidt's reply to "Fatal error when trying to view stats page: Cannot redeclare proc_nice() in /home/stats/pbwiki/common/datamodel.inc on line 2221" was just promoted to the most useful! RoyalKnight and 2 other people think it's one of the best replies.

Folks, here's the scoop (vanilla, goes nice with those cupcakes)

Ok, wiki stats are up and running again, but may take a while to load the first time you bring up the page, and may actually time-out the first time. Sorry, it's lame but I'm working on improving that.

Details: The stats system runs on separate hardware from our main servers. This is done to prevent the huge volume of disk, memory, and cpu load from interfering with general usage on the remainder of the PBwiki service. We installed some otherwise routine security upgrades on several non-core machines including the stats server and ran into some compatibility problems during the process. I've addressed those issues and things are back online. We're sorry for the confusion and brokenness, thanks for you patience!

RoyalKnight replied on September 20, 2009 07:09 to the problem "Can't edit PBwiki 2.0 pages in Google Chrome (beta)." in PBwiki:

The latest Chrome dev (currently 4.0.206.1) is able to save pages correctly. I forget if the recently stable Chrome 3 is able to do it, as well.

However, in regard to aikidave's post, the table editing problem is still present. When I right-click on a table, it may or may not open open the context menu. Apparently, the in-page scrolling in Edit Mode messes up the placement of the context-menu; if you edit a table at the top of your page, it should be fine, but as you go farther down, the context menu will move up relative to your current position.

This is a bit annoying (at the moment, I'm using Firefox to edit wiki pages, as I'm currently organizing a lot of data in several sizeable tables), but I'm not sure if this is more of a bug with Chrome, or Webkit, or PBworks.

RoyalKnight started following the question "Overfull Folders wrecking Nav-Bar. Solution?" in PBwiki.

RoyalKnight started following the idea "Request - instant justification of text" in PBwiki.

RoyalKnight replied on February 23, 2009 03:07 to the problem "Links to new wiki pages are not differentiated" in PBwiki:

Been a quite a few months now, so I've been wondering about the status of this problem.

With wikis being automatically migrated to 2.0 on March 9th, I went ahead and upgraded my wiki to 2.0 so I could get a head start on cleaning things up. However, I create quite a few links to non-existent pages as both callouts and as constant, relevant reminders about what pages I still need to work on.

And nothing makes the problem seem more urgent when a user browsing the wiki calls you out on it, complete with a sad face.

So... uhh... any update? Or even a "we're still trying to nail this problem, but right now we're trying to ensure that wikis don't catastrophically break with the version rollover?"

RoyalKnight started following the problem "Links to new wiki pages are not differentiated" in PBwiki.

RoyalKnight replied on October 22, 2008 12:03 to the problem "Can't edit PBwiki 2.0 pages in Google Chrome (beta)." in PBwiki:

Just found this out a bit ago, but my Chrome seems to be working with PBwiki 2.0 now. Didn't test a lot of the editor's features out yet, but I can edit my and save my pages fine now.

Either this is because...
1.) PBwiki changed things on their end to allow Chrome's V8 to work properly, or...
2.) The development build I'm using (0.3.154.3) fixed it on Chrome's end.

Either way, something is happening that's making both ends meet. Yay~

RoyalKnight started following the idea "Can we have a way to "save and continue editing" pages, so that we aren't forced to leave editing mode every time we want to save our work?" in PBwiki.

RoyalKnight replied on September 17, 2008 09:29 to the question "Preview before posting?" in PBwiki:

Mmm...

In PBwiki 1.0, there's a "Preview" button right next to "Save" which allows you to get a preview of the page before you commit changes.

In PBwiki 2.0, the Edit mode is fairly WYSIWIG (What You See Is What You Get), so there's no need for a preview function.

RoyalKnight started following the idea "Suggestion: Feature good Pbwiki page examples on homepage." in PBwiki.

RoyalKnight marked one of Rachel Pennig's replies in PBwiki as useful. Rachel Pennig replied to the question "Disable the Comment Box on the Front Page only?".

RoyalKnight replied on September 12, 2008 02:56 to the question "Why do I have to click SAVE so many times when editing the same page?" in PBwiki:

I take back some of my words: it seems this technically happens in Opera, as well, though not with some other bugs (but that's a completely different issue).

The JavaScript does seem to act differently in browsers, and seems most compatible with Firefox. I'm not sure what else you can do, besides what you already suggested or (gasp!) switching to Firefox. This situation persists in IE 8, and probably IE 7 as well, so upgrading your browser won't do much for you.

On one of my wikis, I leave breadcrumbs at the top of the page, and I usually work in an order where page CS will have links to A and B. On another, I populate my Sidebar with "A" pages and other common ones to save me a step from clicking on Home.

Honestly, though, the Back Button's drop-down feature is probably the best you can do at the moment, and I have a tendency to do that myself (due to the nature of 1.0 wikis). I'm not sure if PBwiki is working on this at the moment, but it'd be nice to have the same navigation flow across browsers, though I myself have gotten a headache just looking at some of the JavaScript.

RoyalKnight marked one of Clif's replies in PBwiki as useful. Clif replied to the question "talk page function missing".

RoyalKnight replied on September 09, 2008 00:57 to the question "Why do I have to click SAVE so many times when editing the same page?" in PBwiki:

Generally speaking, you'll want to avoid hitting the Back button after you edit a page. It seems to me that when you hit Save, your browser loads up a "new page" (like it should). Hitting the Back button will bring up the previous page (that is, your Edit Mode).

I think this only happens if you use Internet Explorer and a Version 2.0 wiki. Other browsers seem to avoid going back into Edit Mode.

So, after you hit the Save button, just the use the navigation on the page to go where you want from there.

RoyalKnight marked one of Vu Nguyen's replies in PBwiki as useful. Vu Nguyen replied to the question "Launch macro in Word from wiki?".

RoyalKnight marked one of Nathan Schmidt's replies in PBwiki as useful. Nathan Schmidt replied to the question "Restrict file access on a 2.0 wiki?". RoyalKnight and 4 other people think it's one of the best replies.

RoyalKnight marked one of David E. Weekly's replies in PBwiki as useful. David E. Weekly replied to the question "Files Security".

RoyalKnight reported a problem in PBwiki on September 02, 2008 22:42:

Can't edit PBwiki 2.0 pages in Google Chrome (beta).

I know the Google Chrome beta pretty much just got released today (and it IS a beta), but I'll bring it up anyway just so that people are aware.

I'm able to edit and change 1.0 pages just fine. However, two 2.0 wikis that I use (one private, one public) are both uneditable in Chrome.

Safari apparently works with 2.0 wikis, judging from what I've read here. (Safari seemed to have the same problem, but that bug got fixed.) So, I'm less inclined to think that it's some odd WebKit bug, if that helps, though I wouldn't know for sure.