Recent Posts
1
Features / Re: New revs
« on May 14th, 01:39 PM by Nao »
Quote from Nao on May 13th, 08:50 PM
  • Fixed calc() recursive pattern: it was trying to match against the whole pattern, instead of the second group of brackets. Also simplified the rest of the pattern. (Class-CSS.php)
Not that it matters, but the reason I didn't notice the bug earlier was that usually, calc() calls don't include nested brackets, so I didn't test against a stronger string like 'calc(100% + (7px / 1em))', and even then, it probably would have worked in your browser even if not matched.
2
Features / Re: New revs
« on May 13th, 08:50 PM by Nao »
[Commit revision a51158f]
Author: Nao
Date: Mon, 13 May 2019 20:50:43 +0200
Stats: 1 file changed; +2 (insertions), -2 (deletions)

  • Fixed calc() recursive pattern: it was trying to match against the whole pattern, instead of the second group of brackets. Also simplified the rest of the pattern. (Class-CSS.php)
3
Features / Re: New revs
« on May 11th, 07:00 PM by Nao »
[Commit revision 294d044]
Author: Nao
Date: Sat, 11 May 2019 19:00:02 +0200
Stats: 2 files changed; +5 (insertions), -5 (deletions)

  • Implemented proper calc() support in Wess. Well, that was easier than expected... I thought I'd have forgotten how to write proper recursive regexes by now. (Class-CSS.php, Subs-Cache.php)
4
Features / Re: New revs
« on May 11th, 01:45 PM by Nao »
[Commit revision 9fd7470]
Author: Nao
Date: Sat, 11 May 2019 13:45:27 +0200
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • Fixing harmless issue when when trying to request a negative number of topics on the homepage. (Home.template.php)
5
Off-topic / Re: My Journey with Wedge.
« on May 11th, 01:45 PM by Nao »
I don't know much about Xen, except that's it's commercial, so it's not exactly playing in the same field as Wedge does...
I have no idea how Xen 2 would be much better than Wedge, either.
I've been using Wedge for several years on Lestrades.com (my main activity these days, although once again not a paid one...), and every time I have an issue (or need something), I fix it and commit it to Wedge. Let's be clear, it hasn't happened a lot!
Thus, I don't really know what you mean by 'couldn't get a lot of things to work for me'... They work for everybody. Of course, everybody needs their own tweaks here and there, but it's easy to do. Especially with a base such as Wedge, that doesn't change a lot, and also allows you to customize it fully without having to change any base files.
I don't know.
I don't even know what 'prosulation' means. ;)
What I know is that I'm still proud of the software, yes. Especially as free open source software that I never built with plans to get rich.
Posted: May 11th, 01:34 PM

PS: I just realized your message was a reaction to my previous one. Sorry about that, I didn't understand why you were trying to discuss XF here. ;-)
6
Bug reports / Re: Possible bug with custom fields
« on May 11th, 01:36 PM by Nao »
Is... that a fix, you posted below? Because your topic says 'possible bug', not 'bug with possible fix'... ;)
You could just as well post a PR..? Or maybe there's one... I must admit, I don't check the git page often.

(As a quick note: I believe the custom field feature for AeMe was written by Dragooon originally, so I'm probably not well versed in it.)
7
Features / Re: New revs
« on May 11th, 01:29 PM by Nao »
[Commit revision 9de5de8]
Author: Nao
Date: Sat, 11 May 2019 13:28:50 +0200
Stats: 1 file changed; +9 (insertions), -3 (deletions)

  • Page lists (1 2 ... 7 8) will now expand on both side of the suspension point, rather than just its left. This is MUCH more practical when navigating through hundreds of pages. Also reduced the number of entries to 20 per side (40 overall) instead of 50 overall, because 40 is already more than enough. (script.js)
  • Added strict mode to the main script file. I've been using that for years on Lestrades.com for years, and standards-oriented people like it anyway. It's just a few bytes. (script.js)
8
Features / Re: New revs
« on May 7th, 04:10 PM by Nao »
[Commit revision b3396c7]
Author: Nao
Date: Tue, 07 May 2019 16:10:27 +0200
Stats: 2 files changed; +2 (insertions), -2 (deletions)

  • Removed ellipsis from westr::cut() when $ellipsis was set to false but the string was empty. If it's empty, nothing was cut, so the ellipsis stands for nothing. (Class-String.php)
  • Fixed a link to Wedge, just in case. It's not in use for now. (Themes.php)
  • PS: And yes, I'm alive and well, and still ready to commit to Wedge at any point. It just so happens that I have no other bugs to fix, and I have no incentives to keep working on implementing new features.
9
Off-topic / Re: My Journey with Wedge.
« on March 1st, 04:00 AM by Wanchope »
Quote from Nao on January 29th, 12:06 PM
Dear "Sabrina" from Paris (?!), I would love to meet you in real life. Please, tell me more about the assurances obsèques you tried to innocently link in your quote to another message! Lol... Spammers are getting creative, I guess.

PS: Lol, this topic is so outdated, the guy seems to have switched to XF in the meantime... I still use Wedge on a daily basis on my other sites, and wouldn't change to anything else for the world, but of course your mileage may vary.
Sorry, switched over to Xenforo when I couldn't get a lot of things to work for me.
Wedge is your brain work and remained by far the best Smf fork so I can understand your prosulation, it no doubt can comfortably sit side by side with Xenforo 1x.
That said, Xen 2 outclasses every other Forum software. I mean forum software not all those cms bloats.
10
Bug reports / Possible bug with custom fields
« on February 1st, 12:54 AM by live627 »
  • Create a custom field in the gallery
  • Make it a checklist
  • Make it required
  • Make it searchable
  • Edit an item, don't fill that field
  • Observe errors when saving
Code: [Select]
// Add them to the form
  foreach ($fields as $field)
  {
- if ($field['type'] == 'checkbox')
+ if ($field['type'] == 'checkbox' && empty($field['searchable']))
  $field['value'] = explode(', ', $field['value']);
 
  // Options...
  $value = isset($_POST['custom_field'][$field['id']]) && (is_array($_POST['custom_field'][$field['id']]) || trim($_POST['custom_field'][$field['id']]) != '') ? $_POST['custom_field'][$field['id']] : '';
 
+ // JTR: preparsecode() corrupts the array by converting it to a string.
+ if (isset($_POST['custom_field'][$field['id']]) && !is_array($_POST['custom_field'][$field['id']]))
- preparsecode($value);
+ preparsecode($value);
 
  // Do the value checks
  if ($field['type'] == 'checkbox')
  {
- foreach ($value as $val)
- if (!in_array($val, $field['options']))
- fatal_error(sprintf($txt['aeva_cf_invalid'], $field['name']));
-
  // Nothing set?
  if (empty($value) && $field['required'])
  fatal_error(sprintf($txt['aeva_cf_empty'], $field['name']));
  elseif (empty($value))
  continue;
 
+ foreach ($value as $val)
+ if (!in_array($val, $field['options']))
+ fatal_error(sprintf($txt['aeva_cf_invalid'], $field['name']));
+
  // Set the proper value
  $value = implode(', ', $value);
  }