Some carry-over from Discuss Version 0.40 DevTrack:

  • Shortcode "discusspage"?
  • Page description and keyword fields
  • Notifications/subscriptions?

-- AaronGraves Wed Mar 25 14:38:00 UTC 2015 (69.4.28.21)


I've got this thought for category pages: Have the pages start with Category: followed by the category name (similar to Wikipedia). We call RegSpecialPage on Category:.* and have it call sub DoCategoryPage() (or similar). This will then run a search query for all pages tagged with that category.

The only problem now is deciding how to tag a page with a category. Should it be in the text itself? Should it be a separate field on the edit form? Do any of you have any thoughts on this?

-- AaronGraves Tue Mar 31 18:13:27 UTC 2015 (69.4.28.21)


Saving this for category pages: http://alistapart.com/article/multicolumnlists

In case of showing a list of pages in a multi-column list.

-- AaronGraves Wed Apr 1 15:49:35 UTC 2015 (69.4.28.21)


The sub [RegDashboardItem?] has been created to allow the registration of a new dashboard item to be displayed.

-- AaronGraves Wed Apr 1 18:37:03 UTC 2015 (69.4.28.21)


I'd like to look at implementing a feature similar to Wordpress' add_filter

-- AaronGraves Wed Apr 15 02:53:37 UTC 2015 (68.106.213.102)


Also regarding the admin dashboard... it should probably have it's own CSS. This, of course, could be customized/overwritten by a template (theme). But it would be handy...

-- AaronGraves Wed Apr 15 03:02:14 UTC 2015 (68.106.213.102)


To clarify the previous comment... Aneuch should serve CSS for the dashboard, which can be overridden/customized by the theme, however this will make sure that the new look remains at minimum consistent in themes where it wasn't planned for.

-- AaronGraves Wed Apr 15 14:48:52 UTC 2015 (69.4.28.21)


For the add_filter idea, here's a handy link: http://docstore.mik.ua/orelly/perl/cookbook/ch10_05.htm

The most relevant pieces are probably:

$me  = whoami();
$him = whowasi();

sub whoami  { (caller(1))[3] }
sub whowasi { (caller(2))[3] }

So each sub can call something like ProcessFilter (or similar). That sub would (in the above example) call whowasi and determine the name of the calling sub. It would then check the hash value and pull the filter from that hash.

There's also this:

cat currsub.pl
#!/usr/bin/perl
package Aneuch;

sub GetSubName {
  my $package = __PACKAGE__;
  my $caller = (caller(1))[3];
  $caller =~ s/^$package\:\://;
  return $caller;
}

sub MySub {
  print GetSubName();
}

MySub();

-- AaronGraves Fri Apr 24 18:58:16 UTC 2015 (69.4.28.21)


I've sat too long on this release. I'll gather up some info on what needs to be done to close 0.50 out and get it released.

For 0.60, I think I want to focus on code review mostly. There is code in Aneuch that hasn't been changed (or even looked at) for a few years probably.

-- AaronGraves Sat Aug 29 19:41:51 UTC 2015 (216.105.250.127)


For sure there is a "blocker" in the editing function (see Discuss Version 0.50)

-- AaronGraves Sun Aug 30 16:20:40 UTC 2015 (216.105.250.127)


AlexDaniel reported Issue 15, "XSS vulnerability everywhere". Several places are not checked, and need to be. While this affects all releases of Aneuch, it'll only be corrected in 0.50.

-- AaronGraves Sat Sep 5 17:40:07 UTC 2015 (216.105.250.127)


This version is already very delayed, however, consider developing a new theme using bootstrap. If not for this version, then for the next.

-- AaronGraves Sun Dec 13 14:31:21 UTC 2015 (216.105.250.127)


Name:
Message:

Show markup help