Levels Page

Issue #31 resolved
Alexander Celeste created an issue

We need to get the Membership Levels page set up. I think that this should be modeled after the equivalent page of RCP. The page would therefore have two basic sections:

  1. The table of existing levels
  2. Form for adding a new level

At minimum levels need to have:

  • Name
  • Description
  • Duration
  • Cost

Duration being 0 would be what Staff and Gratis member levels are. Relates to #3 as this is the set up for the level membership data. Editing existing levels could be done by populating the add new level form and using that to update levels, but it may be cleaner to use a subsequent page for editing existing levels.

Comments (25)

  1. Alexander Celeste reporter

    The next steps for this are:

    1. Fill in the model functions for levels, add_level( $fields ) and get_all_levels(). This will be related to #9.
    2. Test the adding of a membership level
    3. Work on the display of the membership level rows in the membership level table.
    4. Implement editing and deleting levels

    That is the game plan for this issue. When we complete these steps this issue can be resolved, I think. A few more notes related to this:

    I’ve come to the conclusion that working on this should be the first element of deeper model work that we do. Therefore the first step is to figure out the data structure for levels, and then implement it in the aforementioned functions.

    Once we have levels in the system we can turn to #3 to create additional user profile fields for membership. With those in place we can actually assign memberships. So, at that point we can turn back to #9 and work on contact-specific functions that center on creating and updating contacts (including adding and removing memberships, etc.).

  2. Eric Celeste

    I actually don’t much like the RCP style. I’d much prefer the standard WP style of a table with a “New Level” button at the top. Then all creation/duplication would take place on a separate screen, just like posts, pages, etc.

    In fact, is “level” just a custom post type?

  3. Alexander Celeste reporter

    Form validation is currently happening back on the main levels page. We need to validate fields before going back to the main page, maybe via JS. We may want the entire add process to go on the add level page, and then redirect to the main level page afterwards.

    Of course, if we make levels a post type all of this changes anyway.

  4. Alexander Celeste reporter

    I just noticed that there is no proper title on the page for adding/editing levels. We should figure out why that is and fix that.

  5. Alexander Celeste reporter

    add-edit level page now works for both adding and editing. next step: the model parts of this, including level db tables, db helper functions, and filling in the level functions (see #31)

    → <<cset 24e66291dc21>>

  6. Alexander Celeste reporter

    The lack of a proper title for the add-edit page may be related to it’s parent being null in the menu layout so it isn’t on the menus. For sure that is why our menu isn’t highlighted when on that page. If possible both should be fixed. Maybe we just buckle down and decide that in truth we do have to have the add-edit level page somewhere on our menu.

  7. Alexander Celeste reporter

    changed members page description (see #12). changed levels page description and made add-edit levels page temporarily appear in menu so that it has a proper title and highlights our menu (see #31)

    → <<cset f3556d33c6ba>>

  8. Log in to comment