Wedge

In the same vein, maybe it should be pointed out that the bug that prevented testers from downloading Wedge for a couple of days was due to the fact that the media profile permissions weren't set for them.

Which leads me to two remarks about permission copying:

- we should make it clearer in the permissions page what the difference between 'inherit' and 'base' is (I actually had to go through the source code to be sure I was going to 'copy' them from the Regular Members table!)
- when copying permissions from another membergroup, also copy their media profile permissions!!
i.e. go through all media permission profiles, get the original membergroup's permissions, and copy them for the new membergroup.

I know it's a PITA, but it's safer that way.
Do you think you can do it, Pete? I'm way too uncomfortable with permission code. But OTOH, here it's mostly media permissions, which you may not be as well versed into. My knowledge about them is not perfect either -- that feature was broken by Dragooon, and I had to learn how to use it first. And it was years ago...

Okay, I'll use this post to make a few things clearer...

- I was offline quite a lot this weekend. Sorry about that -- thankfully, Pete was very active :)

- Regarding thoughts. The MultiformeIngegno bug was indeed a known, and fixed, bug. It was committed long ago, but I forgot to apply it to wedge.org... I did it a few minutes ago, so it should not happen again.

- The Welcome template as provided in the Wedge package is a placeholder, really. It's up to you to modify it to your taste... I reckon I should still have it do something closer to what is live on wedge.org, because people probably expect that. I'm planning to rewrite my Welcome template to remove all of the crappy code from wedge.org's (notably, language strings are hardcoded in the file, ah ah...) and add variables at the beginning of the Welcome.php file to make it easy to enable or disable some areas (board list, stats, thought list, etc...)
Still, it's probably not going to happen overnight. I encourage everyone to remind me of it in another month if not already implemented.

- Also, thoughts in the Welcome template are probably not up to date. The 'right' code is on the wedge.org homepage, please bear with me.

- Yes, the profile homepage needs an overhaul as well. I've always planned to do something like noisen.com's (which is based upon UltimateProfile). Give me time... And yes, as Pete said, the fact that the latest public thought is shown is intentional. Still, I'm planning to add a feature to the thought code where by default, thoughts are posted in 'public', but you can also post it in 'public + profile', i.e. your personal_text field in the members table.

- Too many posts, really... I've seen one about the glob() bug. I've never seen that bug on my install..?!
Anyway, I guess a possible hack would be to replace, in these two lines, glob( with (array) glob(, i.e. casting the result as an array automatically. I mean, the worst that could happen is @unlink(false), which will just return false... :^^;:

Anyway, that's just for the 'easy fix', but locally, I've done the is_array() implementation, it's semantically more correct, and probably just as fast.

- Regarding show_when_*, this is from my to-do-list: "Database is missing UI for show_when in membergroups"
And yes, it's just what it means. You should analyze the source files, you'll find the values for show_when over there. Then you just need to apply them to your membergroup row.

- There are LOTS of 'hidden settings' like the one above, that should NOT be hidden settings. For instance, it is STILL not possible to set the default homepage via the admin panel. You have to manually edit the settings table and change the value for 'default_index'.

Possible values:
- A string: Welcome means that Wedge will load Welcome.php (which itself will load Welcome.template.php). You can change it to Stats (for instance) if you want to have the stats page show by default. The main function needs to have the same name as the file.
- An integer: Wedge will show the topics listed in the supplied board ID. Basically, it's a shortcut to myforum/?board=ID

- Also, I'm thinking that Norodo should start recruiting people to help with the documentation right now! Fact is, many of the bugs that were reported to us are actually features, and it takes us time to explain why we deliberately chose that route. Having a private alpha should also help finding the weak points that should be explained in an FAQ so that we don't have to explain everything again.
So, all in all, everything one of us finds some information they deem important enough to be in a FAQ, please post a small message to say so!

I'd just like to reiterate the fact that this area is broken, and, probably, should be removed entirely...
There are so many more ways to 'easily' customize a Wedge install.

No. I mean a link that says something like, "Post as Nao" or "Post as Wedge"...I'm thinking that to be consistent with AeMe, we could use the same thing -- if user has permission, add an input where they can simply type a name (with autosuggest) for the post author.Like..?

rev 1767
(7 files, 2kb)

! The event delayer doesn't like seeing double quotes and > signs. Because I'm a nice boy, I decided to let Wedge ignore > inside event strings (assuming they're either embedded HTML or just a comparison), and allow JavaScriptEscape to additionally escape double quotes. Now, if I can find a volunteer to do a project-wide regex search on on[a-z]+="[^"]*\JavaScriptEscape, and manually add a true param after it, that would be swell... What? Why are you looking at me all of a sudden..? (Subs-Template.php, Subs.php, ManagePermissions.language.php, ManagePermissions.template.php)

! Fixed admin area sending errors when using Warm (due to the difference in layer names). (Warm/skin.xml)

* French translation. (Admin.french.php)

PS: just because I decided to go for this solution doesn't mean it's the 'right' one. Please feel free to disprove me. Or even revert me... No problem.

Because you never posted a request on the relevant topic...?

I said it earlier: I'll give access to anyone with a bit of motivation. The only default pass is given to Wedgeward and Consultants. Because they have SVN access anyway... Friends are our friends, who have access to more private boards, but it doesn't mean they want to test the thing. Anyway -- just post a request! It's not that hard ;)

Hmm... I like the idea, but I have no preferences for where it should be, were it to be made.

Technically, we could also do it the Facebook Pages way...