Log in Discussion History Go to the site toolbox

BluWiki talk:Beta Testers

From BluWiki

Give feedback here!

Have a problem with a BluWiki Beta feature? This is the place to speak up!


Customize the status bar

Is there an howto to customize the status bar ? I would like to change the icons to get text instead, and add my own menus (especially put the search feature onto the status bar)


Please add these lines

<?php $this->html('headscripts') ?>


if($this->data['trackbackhtml']) print $this->data['trackbackhtml']; ?>



in the file bluwiki_skin.php . That will let the possibility to run global feature like FCKEditor or thins like that! -Anon

Good suggestion, the change has been made and will be incorporated into the next release. --Sam Odio 04:20, 25 November 2006 (EST)


Sorry to be an ass-pain Sam. The justification seems to be a variable commodity, sometimes it obeys the requested setting in Preferences|Misc|Justify paragraphs, mostly it does not. When I recently reported odd behaviour in this area, I thought that you had just got it working properly, however, it is not. I have set my text to fully-justified, but it usually displays as left-justified. I'm sure you don't need an example to know what I mean[1]. Are other users having this difficulty? --Migrant Worker 15:44, 15 October 2006 (EDT)

Justification is working fine for me. I suspect the problem is that you have not followed the instructions on the bottom of the preferences page:
Note: After saving, you may have to bypass your browser's cache to see the changes. Mozilla / Firefox / Safari: hold down Shift while clicking Reload, or press Ctrl-Shift-R (Cmd-Shift-R on Apple Mac); IE: hold Ctrl while clicking Refresh, or press Ctrl-F5; Konqueror:: simply click the Reload button, or press F5; Opera users may need to completely clear their cache in Tools?Preferences.
Try that, and see if it helps. If it doesn't, you may need to clear your entire firefox cache. --Sam Odio 17:37, 15 October 2006 (EDT)
Thanks for the clue Sam; clearing the cache does indeed restore the required format, but the real culprit is the auto-logout feature, (bug), which resets it. We really should stay logged-in for the entire session, one never knows whether one has been logged-out until one tries to make a change. --Migrant Worker 17:56, 15 October 2006 (EDT)
That will take longer to troubleshoot, as logouts / logins work fine for me. I'm not sure if its a browser setting problem (like cookies being deleted) or a problem with the site. --Sam Odio 20:05, 15 October 2006 (EDT)


Regarding the new 'skin', whilst it is most welcome to have more of the page, it seems to exacerbate the problems in formatting, specifically the auto-generated TOC. It would be nice to force its position on the page, as one does with images.

The TOC can be disabled by inserting the code __NOTOC__ into your page. You can also specify where in the page the TOC appears by inserting the code __TOC__ --Sam Odio 16:03, 24 September 2006 (EDT)
I'd found those commands but they don't allow one to aesthetically format the page. For instance, I can't get the same layout as with the old default skin. Is there a way of forcing the TOC to sit on the left, as one can with an image. Whereas before I had the TOC on the left and to its right, an image, now the TOC sits below the image and the text wraps around the image. The last application that ever allowed me 100% layout control was the Xerox Ventura Publisher, V2; those were the days! --Migrant Worker 20:38, 24 September 2006 (EDT)
Migrant Worker, try inserting this code in the location where you want your TOC:
<div style="float:left; width: 25em; margin: 1em; clear: both;">__TOC__</div>
Hope that helps. --Sam Odio 20:50, 24 September 2006 (EDT)
Thank you Sam, that has provided an acceptable layout. --Migrant Worker 21:58, 24 September 2006 (EDT)

In the Monobook skin, the auto-generated TOC does not "float right" by default as it does in the default skin. It's easily fixed with div style code, but I have a bunch of pages, so I added the div style code to the template I have on every page. That makes the TOC appear on pages with only 1 or 2 sections. Is there a better way around this? -Rae ArdGaoth 22:35, 20 March 2007 (EDT)

Show me some pages so that I can figure out a solution for you. --Sam Odio 23:10, 20 March 2007 (EDT)
Living ENWorld:Feats is an example of a page with a long, auto-generated TOC (which I want!) but which doesn't automatically float right in the Monobook skin. I "fixed" it by adding div code to the Living ENWorld navigation bar template (feel free to revert it or mess around in there). As an annoying side effect of adding the div code to every LEW page, Living ENWorld:History is just one of many pages that doesn't need a TOC but now has one. --Rae ArdGaoth 14:04, 21 March 2007 (EDT)

Status Bar

The top blue status bar isn't being used to its full potential. Since a page loads so as to read from the top, one shouldn't have to immediately navigate to the bottom in order to choose an option. Please consider putting the following items on the bar: LogIn|History|Discussion|(Un)Watch|Preferences. --Migrant Worker 16:31, 28 September 2006 (EDT)

Right now the majority of comments I've received are from users are comments requesting a simpler status bar - so that the page is kept clutter free. The new skin attempted to address this issue, which is why there is such limited functionality in the top right.
Regardless, I'll look into a way to give the user more functionality while maintaining the purity of the page. I'm thinking about doing a AJAX drop-down box, instead of sending the user to the toolbox @ the bottom. I'll just have to get around to developing it.
In the mean time, the green down arrow is your friend. --Sam Odio 19:29, 28 September 2006 (EDT)
We've already allocated the space with the blue bar, why not use it. The big release of real-estate, was to lose the side-bar. I don't like drop-downs, there's enough room to place the items I've mentioned. Sort it! --Migrant Worker 09:03, 29 September 2006 (EDT)
Thank-you for your comments. I'm not exactly sure what you mean by "Sort it!" - but I'll assume you didn't intend it in an offensive way. Regardless, this would be a good time to remind you that BluWiki is a free service, for which I receive no compensation.
You are correct in your assumption. The internet is somewhat 'dry' and if I had been speaking directly to you, the intonation and smile on my gob would have betrayed all. Sorry, I thought it, so I just had to say it!
Now, I realise I'm not paying a bean towards your running costs, that's why I'm going out of my way to help you improve the product; that way we all win. --Migrant Worker 16:00, 29 September 2006 (EDT)
Let me clarify my previous comments: I wasn't referring to screen real-estate. The 50 vertical pixels that the bar occupies is acceptable. However what is not acceptable to many users is a large BluWiki presence - especially on the top of every page. The last thing they want is a half a dozen default BluWiki actions that 95% of their visitors will never use. This discourages them from passing around their BluWiki links because they feel they are promoting BluWiki, not their content. I've even had users specifically request that BluWiki have no presence at all on the page.
Okay, in that case I did get the wrong end of the stick; apologies. --Migrant Worker 16:00, 29 September 2006 (EDT)
I will definitely take your requests into consideration - just keep in mind that I must address the concerns of others as well. Hopefully I can make BluWiki both useable and aesthetically pleasing. Thanks for choosing BluWiki, and I appreciate your patience while I sort out these issues. --Sam Odio 09:42, 29 September 2006 (EDT)
Understood, it's just that I don't hear them making any requests; shouldn't they be using this forum? --Migrant Worker 16:00, 29 September 2006 (EDT)
There was a decent amount of time that went into the development during which I consulted my aplha testers (aka close friends). They unanimously called for less clutter on the top / left.
But functionality is always good - I'll see what I can do as a compromise. --Sam Odio 17:16, 29 September 2006 (EDT)
Migrant Worker: In response to your comments, I have created a set of icons in the top right that give the user access to most of the the functionality you requested. --Sam Odio 14:18, 5 October 2006 (EDT)
Sam - I'd like to compliment you on the simplicity of the default Bluwiki skin. It's a different way of looking at a wiki for me, and I must say, it's very nice. Migrant Worker's suggested additions (though I had no idea they were his when I first started using this site) I used often. I think I would find it tedious to have to click the green arrow all the time. All that being said... I'm using the monobook skin now, because my friends were seeing different things than I was. =P -Rae ArdGaoth 22:27, 20 March 2007 (EDT)
Rae, thanks for your feedback! I'm glad to hear that you've found it useful. If you (or your friends) have any suggestions about the skin, feel free to let me know! --Sam Odio 23:02, 20 March 2007 (EDT)

BluWiki:Clean URLs

Very nice Sam, thanks.--Migrant Worker 20:18, 4 December 2006 (EST)

Doesn't look like they work with subdomains.--Nkrishna 21:37, 18 September 2006 (CST)

unfortunately their mutually incompatible at the moment --KaiAdin 08:58, 19 September 2007 (EDT)

interwiki links ( [[randompage]] ) don't stay clean. also, logging in overrides cleanliness. Benrothman 02:12, 26 April 2008 (EDT)


I'm very confused about subdomains. They aren't really subdomains if all of the pages correspond to the entire BluWiki domain. For example, if one user has a subdomain with a page called "Page" and user wants a page called "Page" for their subdomain .. it's the same page, so they can't do it. I really don't understand. -- 06:02, 12 January 2007 (EST)

Thanks for your feedback. Although we are in the process of allowing users to create separate Wikis, this feature is not yet available. --Sam Odio 20:03, 16 March 2007 (EDT)

  • I added a subdomain, sum1els. It is not supposed to be capitalized, but my user name and subdomain both appear to be capitalized.
That is correct. This is a known issue; we are working to fix it; do you know anyone who is willing to help us? Thanks again for your feedback --jcarroll 11:37, 23 August 2008 (UTC)
  • When I click on the Sum1els link in the Personal tools section, it takes me to a page called User:Sum1els that says it is empty, but when I click the link to edit the page, it goes to the page Sum1els, which is not empty.
  • I put a link on the root page of my subdomain, and when I clicked it to add a new page, the new page appeared to be just like any other random page. I expected to be able to put all of my pages in their own namespace, but it did not seem to work that way.
  • I'd really like to set permissions on the pages, but the feature tells me it is not working. I hope when it is working that the permissions are on a per-page level. New pages created by clicking links from existing pages should get the same permissions as the "parent" page by default.
  • --Sum1els 19:38, 16 March 2007 (EDT)
Thanks for your comments. Because of limitations, the first character of all pages are capitalized. Your user page is empty, and you can edit it here. You're going to have to manually put all pages in your own namespace. For an example of this, see http://startup_weekend.bluwiki.com. Permissions aren't yet working, but we will definitely announce when they are. --Sam Odio 20:03, 16 March 2007 (EDT)
Yes, I can get to my user page that way. The bug I am reporting is that if I go to my empty user page, all of the edit links on the page (the "Congratulations! This page is empty" page) point to Sum1els, not User:sum1els. --Sum1els 21:02, 21 March 2007 (EDT)
Ok, refresh the page and try it again, hopefully it should work. Sorry about that! --Sam Odio 22:55, 21 March 2007 (EDT)


I realize that BluWiki subdomains are still in the beta stages, but I'm having trouble with mine and I don't know where else to put this comment/question. I have a page LEW, all caps. The url http://lew.bluwiki.com/ leads to Lew. Which is annoying, but I sucked it up and dealt with it by adding a #REDIRECT [[LEW]] to the Lew page. Unfortunately, when you use the .ORG url like this, the redirect doesn't function. I don't know if this is a fixable problem, but at the very least I suppose you'd want to be aware of it.

Rae ArdGaoth 01:19, 11 March 2007 (EST)

I'm not sure why the redirect functionality isn't working for you with .ORG urls, it seems to work fine here. I'll try it on a different machine later, and see if I can recreate the problem.
Can you try on another machine as well, so we can see if it's just your PC or if there's something wrong with the server. Thanks! --Sam Odio 09:52, 11 March 2007 (EDT)
Hmm. It works now. It didn't work two days ago, and it didn't work last night. I have no idea what happened. I'll try it again some other time. Thanks for looking into it though.
--Rae ArdGaoth 13:09, 11 March 2007 (EDT)

"Soma" spam filter

For some reason, the spam filter catches "soma" as spam and won't let me edit the page. It won't even let me do it on this page! Now, I have no problem with a spam filter, but why "soma"? (I did find away around it using s_o_m_&_#_9_7_; without the _'s) -Rae ArdGaoth 22:33, 20 March 2007 (EDT)

Let me start by saying the spam filter sucks. I hate restricting speech on bluwiki, but I have to balance that ideal with the necessity of preventing users from vandalizing the pages of others. 30-50% of spam on bluwiki is drug related - most of these being sites that are trying to increase their rankings on search engines by creating backlinks for commonly searched drug keywords. As a result, I ended up blocking soma and several other drugs (like viagra).
If this is a problem (and you're willing to police bluwiki for soma spam!), I'll remove it from the blacklist --Sam Odio 23:39, 20 March 2007 (EDT)
No, it's not worth it. And besides, I found a backdoor. =P -Rae ArdGaoth 00:44, 21 March 2007 (EDT)

Some glitches

  • From any page, I cannot go back to the frontpage
    Found out later that there's a link at the bottom, but it's hard to spot!
  • A horizontal scroll bar appears at all pages (fixed using the hack width:99% on body)


Site Toolbox:

Personal tools
GNU Free Documentation License 1.2
This page was last modified on 23 August 2008, at 11:37.
Disclaimers - About BluWiki