Recent Forum Posts
From categories:
page 1 of 212next »

There are a few things that don't work as well as hoped (need to make a list and post it in the projects forum…) , but this is still pretty much completed. Is there any specific way to pay for these pledges yet? I'd prefer PayPal, personally.

My pledge by leigerleiger, 12 Feb 2010 01:51

I've used 'cancelled' all my life but the US-centric spelling checkers on all my boxes are slowly 'fixing' my spelling.

I saw that you had written "canceled" and, having used cancelled all my life, I assumed you had made a mistake. Needless to say a quick search tells me that both are right! :)

e.g. http://blogs.msdn.com/tristanc/archive/2004/02/06/68858.aspx

Ah, nice to know it works. Let me ask.

Re: Aspect Delivered by pieterhpieterh, 07 Nov 2009 17:29

Pieter, I have successfully managed to change the site name to Lord Lieutenant of Ross and Cromarty which is 36 characters, so it appears that this aspect has been delivered and Google, Bing etc will index the site properly in due course. Thanks very much for this. What are the arrangements for paying the pledge?


Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.

Aspect Delivered by RobElliottRobElliott, 07 Nov 2009 13:02

Many thanks.


Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.

How did you get on with your pushing?

Yesterday we fixed the database (which had limits on these fields) and with luck today we'll push the changes in the application code.

Re: Remarkably simple to do? by pieterhpieterh, 21 Oct 2009 12:41

How did you get on with your pushing?

Rob


Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.

At the moment this aspect seems to cover giving all members permissions for all private categories on a site. However, although it would add to the complexity, one thing I would like to see is that the permissions for each private category can be assigned to specific members. So it's not that all members can see all the private categories but that each private category can have its own assigned group of members.

Rob


Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.

The Scope of this Aspect by RobElliottRobElliott, 04 Oct 2009 19:12

So… I've started getting my hands dirty in the wikidot codebase over the last week, and made this change. I raised the site title and subtitle to 200 characters, and the name (subdomain) to 50. We'll try to push that next week.

Re: Remarkably simple to do? by pieterhpieterh, 03 Oct 2009 08:00

No, thsi is not true for a modern database - the varchar(x) means exact the "lenght" of a fields is variable and the storeed value in the database too.

The max(lenght) normally means the maximum (prepared) allowed space in a table for such a field.
- and as we see - not necessarily the max display-length automatically…


Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.

Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?

Re: Why 50 and not 70 ? by Helmut_pdorfHelmut_pdorf, 03 Oct 2009 07:36

Well, it depends what is currently being used to store the site title, e.g. varchar(30)

If every site title always uses the same amount of space in the database, regardless of the string's actual length, then increasing that limit would mean a massive decrease in the amount of free space (for every wiki, extra space would be used even though the title isn't that long). In such a case, increasing it by as least as possible would work best.

I'm rambling… xD

Re: Why 50 and not 70 ? by leigerleiger, 03 Oct 2009 07:18

in some month we get the next increase - season…


Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.

Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?

Why 50 and not 70 ? by Helmut_pdorfHelmut_pdorf, 03 Oct 2009 07:07

This sounds like something that wouldn't take much development time — so it's easy money for Wikidot.com ;-)

Remarkably simple to do? by leigerleiger, 03 Oct 2009 06:18
pieterhpieterh 30 Sep 2009 11:09
in discussion Hidden / Per page discussions » About

You're right… OK, home page is fixed now.

by pieterhpieterh, 30 Sep 2009 11:09

But the option is available for pledging $50.00 USD as well. Homepage should be updated?

pieterhpieterh 29 Sep 2009 09:44
in discussion Hidden / Per page discussions » Private categories

Pledges go through me before they're posted. If there are many small pledges on an aspect, a few people who change their mind does not matter. If there is a large pledge, I'm going to need convincing before we take it seriously.

by pieterhpieterh, 29 Sep 2009 09:44

for the last changes to my mind… it is exact what I thought.


Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.

Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?

Thanks, Pieter! by Helmut_pdorfHelmut_pdorf, 29 Sep 2009 06:55

When this is developed, the first thing I'll be changing is this page on my main website.

Each NewPage module has only one option changed — the tags. If I could move all of that into one drop-down field where the user selects the skin 'category', it'll make things so much easier, and I'd feel comfortable putting it into a more obvious page where everyone will see Wikidot's latest feature update ;)

What this will be used for by leigerleiger, 29 Sep 2009 03:32

So, technically, I could pledge $10,000 USD for this thing, then when it's developed, I'll just withdraw my pledge.

Do you have any ideas about how to combat this type of situation? Perhaps a marker against someone's name, so that if they cancel a pledge, they need to wait a month before they're allowed to pledge again for any aspect?

Cheating by leigerleiger, 29 Sep 2009 03:07
page 1 of 212next »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License