Wikidot Community

Yes, this is definitely the reason.

You schould klick pn your user-name and see thast your wikidot user7screen name is stored eith a hyphen: "ketan-sevekari" ( this is a unix-name)

on http://www.wikidot.com/user:info/ketan-sevekari

there fore you should use ketan-sevekari
( as Michal Frackowiak - the founder of wikidot itself - has to use michal-frackowiak )

Thanks. It worked.

I think he is asking how to hide content from "everyone else", which is accomplished by simply using the showto type instead of the hidefrom type. Unless or until groups can be used, it's going to be pretty hard to hide content from large numbers of users.

-Ed

Yes Ed, that was what I wast trying to say. Show this content to only me (for example)

Pity about the no modules but now that I have re-read the original post I understand that it is because it's based on ListUsers module.

Thanks to all.

But you can use the Extended NewPage Module in “Manual Mode”… this is basically an improved “NewPage Module”.

I'll have a look and post my results.

*edit* Not quite what I need. I need to be able to specify what the new name will be called. :)

*edit* Not quite what I need. I need to be able to specify what the new name will be called. :)

Not sure what you mean Hobstar, that is possible as far as I know.

Can you tell us the use-case, so we understand what you're trying to do? I believe there should be a way to do it, based on what you've told us so far :)

I need to be able to specify what the new name will be called. :)

That's the very reason I designed the Extended NewPage Module in the first place… The basic NewPage Module can't do that.

Shall we continue this on the Extended NewPage Module page? :)

I'll double-check the width - I'm pretty sure there's room for it. It could be some other factors in my theme causing this. When I place it on top, the menu item is on top of the rest of my menu. If I move it to the bottom, it's falls on a line below the menu.

Thanks for testing. I'll report back after I dig some more.

-Ed

Just a quick note, the admin menu isn't being detected as a menu option, because it has different styling to usual. (These screenshots are using a slight variation on your code, the include has been moved to the bottom of the page)

I got it sorted out with css. I am using #top-bar ul {display:table;} which makes it easy to center my menu, but was causing the break to 2 lines when I inserted the includes. Changing it to #top-bar ul {display:inline;} moved the admin menu to the left side, but I lose my centering. It still looks OK, so I'll probably keep it in place unless my friend doesn't like the new look.

#top-bar ul {display:table;}

#top-bar ul {display:inline;}

Thanks again for spending some time on this. Seeing your test results made it pretty clear it was something in my css and that made it easier for me to track down. I'll be sure to test this kind of stuff with different themes next time before I go running for help.

-Ed

At time like this, you just need to shout for help… ROB!

Did someone call?

Centering a top menu creates an extra bit of work when you have a liquid design. But one way to do it is to separate the top bar menu items from the background color behind them and, crucially, make the menu items a fixed width but the background color a percentage:

Set your current top bar to be transparent:

#top-bar, #top-bar a, #top-bar ul li { background-color:transparent; }

Set the top bar to be a fixed width, not a percentage, and set the margin to centre the menu:

Using a fixed with of 932px will be fine for monitors at 1024 or above and will include all the current menu items.

#top-bar { margin: 0 auto; width: 932px; }

You should now have a centered menu with a transparent background:

To add the background back in use the #header extra-div-1 rule:

Position the #header-extra-div, add the color and make sure it has a width of 100%:

#header-extra-div-1 {
    background-color:#004400;
    height:20px;
    margin-top:150px;
    width:100%;
}

And the result is shown below:

He's brilliant, isn't he Ed?

Thanks Rob, you're the best :D

Sorry, I'll shut up now. :(

Every time you say something on this page, it seems to be said in a completely foreign language…

Why? I understand HobStar perfectly well…

I know the dev team is really busy. My personal wishlist puts this parsing order thing at the top. I'm vague about how it all fits together, but it seems to be the critical issue for

• effective use of data forms
• conditional includes
• comprehensive integration of includes & %%variables%%

You've got these great ideas, and I know there are others out there that we could implement if only this issue were resolved. Should we be compiling a list of projects that depend on this? I wonder if Wikidot's priorities might be affected by a detailed list of the powerful tools that are waiting on this fix.

Keep in mind that Wikidot plans to work on improving the experience for new users next — that is also long overdue.

I'm sure they'll work on things like this for us next, but I think it's reasonable to at least let them work on improving the user interface first :)

Maybe I'll understand the value of that when I see it.

To me, we do well when we create these sophisticated tools, share them, and package them for simple reuse on other sites. Sure, there's always tinkering to do, but that's what nurtures the next generation of wiki-gurus.

I agree that the whole point of a wiki is to make it simple for new users. But I don't understand the distinction between sophisticated tools and improved interface for new users. Fully functional integration of data forms, page variables, includes, and ListPages would go a long way toward making things much simpler for our casual users.

I think the point is that people are being stuck before that.

Someone should be able to find wikidot.com, create an account, create a blog, write their first blog post, and share the link with their friends — all in about 10-15 minutes.

At the moment people are registering… and then not sure what to do next (as it illustrated with the occasional "how do I make a wiki" post in the community forums). Or, they are able to create a blank wiki, but have no idea how to edit the main page or turn it into a blog.

Most of what wikidot needs in terms of the user experience is "eye candy" IMO. Most of the functionality is there and there are very powerful tools at the users' disposal - the problem is finding those tools and knowing how to use them. It's not "idiot-proof" enough.

Edit: I'm going off-topic here. What I'm trying to say is, as much as I want these features just like you do, we should be willing to wait a while, as there are other things (UI) that need to be done first. Things that we won't use, but new users will.

I'll shut-up now :)

I'll wait, with plenty of good faith, knowing that the team is committed to their user base.

For many of us, there's nothing simpler and more intimidating than a blank page. I wager that's why most users' wikis never get going. I think the technical barriers are very secondary.

Hey James, %%name%% does the same thing in the ListPages as %%title%%, and is probably the better variable to use (it's a more natural choice, when what it does is to display the person's username)

I've been trying to teach myself to use %%name%% instead of %%title%%, so that I automatically do the same in my examples to new users.

As for this… un-freaking-believable! YOU ARE A LEGEND!!

Could it… by chance… be used inside the ListPages module? If I remember correctly, the ListUsers module itself does… and your SUO is based on the ListUsers module. Will do some testing.

This is the reason I enjoy being a part of the Wikidot community - there's always awesome new things being created out of the same syntax, because people are thinking outside the boundaries of the documentation and coming up with some awesome stuff!

As I said on my blog on 7th March, Creativeness is the best attribute a community can have.

Hey James, %%name%% does the same thing in the ListPages as %%title%%, and is probably the better variable to use (it's a more natural choice, when what it does is to display the person's username)

The SUO code generates something like this:

[[module ListUsers users="."]]
<your content goes here>
[[/module]]

So using %%title%% within the ListUsers module will generate “James Kanjo”, as opposed to %%name%% generating “james-kanjo”

Could it… by chance… be used inside the ListPages module?

Yes… in two ways:

• If the ListPages module uses the %%content%% variable, and THAT %%content%% contains SUO code — Works fine
• SUO directly hardcoded into ListPages module — Works, but only through using prependLine/appendLine, and separate="false"

For example:

[[module ListPages range="." separate="false"
prependLine="[[include :snippets:suo BEGIN |unique=kanjo-86 |type=showto |user=james-kanjo]]"
appendLine="[[include :snippets:suo END]]"]]
<YOUR CONTENT GOES HERE>
[[/module]]