Todo List

bBlog

getPass()

  • add the link to the users blog in the email message
  • create dump or expand error message for failed mail send
  • for security reasons, use global or instantiate within function?

identify_admin_archives()

  • now it may be an idea to do a if(!defined('IN_BBLOG')) die "hacking attempt" type thing but i'm not sure it's needed, as without this file being included it hasn't connected to the database, and all the functions it calls are in the $bBlog object.

identify_admin_plugins()

  • this is supposed to be a GUI for plugins. need some help with some sort of api. in the mean time we'll put them in an array.

identify_admin_usermanager()

  • himself (select * from t_authors ... ... ... where nickname='user')
  • this boolean, and if a user isnt an admin, then mask all other users but
  • Add an extra 'isadmin (bool)' field in authors table. So add
  • edit them at will. We need this to happen only if the user is an admin.
  • Currently, anyone who logs in can see all other users details and can
  • xushi - major security enhancement

index.php

  • xushi: flyspray #55: make sure install/ is deleted

MAIL_HEADER

  • xushi: we could use bblogMailer class here

SettingsAPI

  • add a docblock here

SettingsAPI.class.php

  • Add addslashes()/stripslashes() everywhere it's required to support nifty setting name / setting values.

standalone.upgrade.php

  • be expanded to the whole upgrade proccess.
  • and 0.7.2 corrected it by doing the exact method just explained. The same could
  • This idea occured to me while merging 0.6, because half of the db was missing,
  • now.
  • of the patcher, you make a $db->query($q);, instead of several small ones like
  • a check to see if what you have is old, missing, or the same. At the very end
  • I mean it will look similar to the install php, but with each querry protected by
  • If anything is different/missing, then it patches and updates. Thats really it.
  • 2) What your current db looks like.
  • 1) What the last version of the db looks like, and
  • anything from you except 2 things.
  • of the code. The upgrader doesnt need any versions. It doesnt need to know
  • I just noticed a nice idea which will greatly reduce the complexity and size

  • call the function from there instead..
  • coz for the life of me i can't get it to
  • from bBlog_plugins/builtin.plugins.php
  • I'm going to just copy the code here for now

  • xushi: flyspray #55: make sure install/ is deleted

  • : Delete blogurl section from install page (i think i already did that..)
  • ------
  • or FAIL.
  • case with functions.. Atleast with functions you can return SUCCSES
  • Remove the switch case. Either stick all code in 1 blob, or replace
  • ------
  • note:
  • weather you have a full config.php or not.
  • i like how in 0.8, by default, a new install is determined by
  • -----
  • note:
  • third single page.
  • 3) All the other installation info can be grouped to a
  • fill his details for the installation
  • 2) The second page will be the one asking the user to
  • button on the first page (with the licence)
  • 1) The 'file permissions' can be binded to the 'agree'
  • from 6 pages/steps, down to 3.
  • im thinking of reducing the GUI installation steps
  • -----
  • note:
  • xushi: notes

  • Uncomment the line to enable.
  • xushi: flyspray #55: make sure install/ is deleted.

core

GeSHi::disable_highlighting()

  • Rewrite with an array traversal

GeSHi::enable_highlighting()

  • Rewrite with array traversal

GeSHi::enable_important_blocks()

  • REMOVE THIS SHIZ FROM GESHI!

GeSHi::get_language_name_from_extension()

  • static?
  • Re-think about how this method works (maybe make it private and/or make it a extension->lang lookup?)

GeSHi::highlight_lines_extra()

  • Some data replication here that could be cut down on

GeSHi::load_from_file()

  • Complete rethink of this and above method

GeSHi::set_case_keywords()

  • Error check the passed value

forsell

parser.php

SmartBee

search.class.php

  • boolean ".T_SEARCH." +word -word