I'm going to begin using this page as a place to list my wants and problems that I'm having as I work through application development in Sputnik.

• UID system is vulnerable to growing (thus taking longer to generate a UID) and makes the data directory rather messy. Should be fixed somehow.

To-Do List

Bugs and Patches

• Currently cannot access the ip address of a user in sputnik. We need to wrap the wsapi_env in a way that allows us to get this information.

Problems

Editing

• There are a few problems when using the default edit action (which is desirable)
  • You HAVE to include the prototype as a hidden field in your edit_ui or the actions get screwed up
    • Create a ticket and give me more information. It works when I try it. - Yuri
  • My custom field is not being saved properly, need to figure out how and why this is happening
    • Your custom field needs to be included both in "fields" and in "editui". "editui" controls the interface, but "fields" controls what will or won't be saved. Make sure you have it in both.
• There is no way to easily have different editing forms depending on user permission level. This is something I need for most of my wiki.

Concurrency

• Look into what is necessary to implement the edit_revision field for all nodes, so we can flag out of date edits and take corrective action.
  • Detecting this is easy. Figuring out what to do about it is harder. -- Yuri

Features/Requests

Authentication Module

• In addition, I'm afraid that the split between authentication and permissions will be bad, but I don't have any conclusive evidence on this yet.
  • Perhaps userisadmin() is a good case for making the auth/permissions into a single module

Nodes/Sputnik/Versium

• It would be useful (in a few ways) to be able to check the existence of a node rather cheaply without actually returning the node. Perhaps sputnik:node_exists(name)?

Queries

• What is the default markup module that sputnik uses, and what are the alternatives?
  • see [[Markup]]
• This markup module is terrible, and very confusing to me.
  • try "medialike", as used by luarocks
• Is there currently a way to give non-standard widgets to the htmlform function? For example, I need to have a textfield that is longer than the default one. Rather than having to add a template to _templates and then some special case code is there a better way this can be handled?