Whoo! Finally got Invoices to the point where I’m mostly happy with them.
Just gotta work out a good way of tying time reports to invoices, and it’ll be finished! Well … the core invoicing functionality, anyways.
I’ve had several people e-mailing me lately about road-maps for the future of the plugin. My plans from here are to do the following:
- Tie in time reports to invoices.
- Build in a system whereby users and clients can attach ‘messages’ and ‘files’ to either ‘tasks’ or ‘projects’ in general.
- This will probably entail using Uploadify on the front-end, as it’s just freaking handy and slick.
- Files will be stored in .htaccess protected subdirectory of /wp-content/uploads/ so that random moochers can’t surf right in and snoop out your files.
- Haven’t decided yet whether people will be able to link directly to the files, or whether I’ll have to include an ‘intermediary’ php script that will read them out to confirm permissions. Any thoughts?
- After that’s in and handled, I’ll probably knock out some of the ‘small stuff’ that I’ve been putting off for a while, such as
- Adding in the front-end widget for logged-in-user time entries.
- Migrating internal functions from a seven-variable (-ish) call to a `$args` array-based call.
- Including nonce-functionality to the forms, to protect against accidental ‘oops i refreshed the page and it submitted again’ and other less-accidental glitches.
- Patching the admin-header time entry form to just be a button or the like that lightboxes a form for adding a time entry. This will let it use enough space, and not shove other bits out of the header.
- Writing ‘non-administrative’ user time entry pages … that basically list all that user’s time entries, with a form as the first row for adding new time entries all ajaxy and such.
- Building in filtering into admin-pages.
- Building in reports. Let me know anything you’d like to see included for reportability.
So that’s the basic road-map. Oh yeah, and I’m planning on actually using that little ‘help’ drop-down you always see in WordPress at the top-right, that plugin developers always seem to ignore. (It may be a futile effort, as users by this point may be trained to not even bother with it)
Leave all comments below!