W6 Site moves to BETA
W6 Site moves to BETA
.

W6 Site BETA release.  

Key features are listed Below

cropped-W6PZA-Cali_SOTA_TAB-Logo.jpg
Bugs, features, and fixes will be added to the bottom of this as needed.

Key Site Features

  • Built on WordPress + plugins

  • Rich Text Editor via Pagelayer editing (user documentation needed to help our publishers)

  • Page component templates create modern page designs and consistency.

  • New, Events, Spotlight, Trip Reports are categories all fed from the "Posts" widget (make it easier to manager)

  • Table view of trip reports with filtering and search using the
    (working on the latter 2)
    (using "Posts Table" plugin to do this)  Search does work if the text is in the trip report.  Most likely search is the summit ID.  Currently working with tech support to find out why.

  • Flexible menu system, easy to edit

  • Custom New user / registration workflow approval using Forminator. 

    • Registration notices sent to one or more e-mails for approval. 

    • Approvals via one click on email or using Forminator / Submissions page to review and approve.

  • User Roles
    We can have users that can only create and edit their post submission for a "Trip Report", but not publish.  This could also be used for news and spotlight to be reviewed.
    "Authors" role doesn't need approval to publish a post.
    Editors and Admins can approve new posts so that they show up.  We will use this for Trip Reports"
    Because "Pages" are a core element, only Editors and Admins can create and edit those.

    • Subscribers can view only and I think comment

    • Contributor role can do all above and create but not publish.   This is our default new user role so that people can create trip reports.  New posts created by this role causes a notification to be sent to editors and above for the post to be made visible in production.  It gives us a chance to check that the post is not spam, appropriate, and contains the proper metadata (for now it should have the key words in the trip report so that search works).
      Contributors can edit their draft submissions.  (I don't think we want Contributors to create "pages".  This should be done by editors.  Will look into controlling who can create a page.  Can't create "Page"

    • Author role can do all above and create and publish without approval. This is our new user default.
      Can only edit their posrts.
      Can't create a "Page"

    • Editor role can do all above and approve submissions by others and can edit any page.
      We will use this for "Trip Reports" approvals.
      Can create "Pages"
      We will have many people in this role.

    • Admin role is basically super-user and can change core site configuration and modify existing user roles.
      We will have more than one trained user in this role.

  • Notification system for new posts so that they are approved in a timely manner
    (using Post Status Notifier Plugin for this)

  • Custom fields for posts via Advanced Custom Fields Plugin.
    This allows us to collect minimum metadata for trip reports.
    It puts the input form that we defined ONLY on the Trip Reports posts (not news....)

  • The Trip Report display page now displays the custom fields 30 hours of work trying to figure out how to do this in a supportable way and then implement it.

  • Automated backups via Updraft

  • Fixed search on the trip report page

  • UI changes when using mobile phone.

Backlog

  • Fix the contact form.

  • Need volunteers to be "admins" (to approve new users and others with WP experience to manage site)

  • Need volunteers to be "Editors", responsible for approving content and managing core pages. (I'll train you

  • Need a site logo banner from someone that knows how to work around WP screen resizing.
    I'm not a graphic designer.

  • Login link should go away after you log in.

  • Restrict blog posts to "Trip Reports" Category

  • Security

    • Protect against automated bots doing SQL injection attacks, direct Db API attacks, WordPress API attacks, and more.  Need someone who has fought these bots before check out your configuration.   Consider purchasing a subscription to a WAF or other security tools.  Will need donation $$$. 

    • Look at currently installed but not activated Akismet Anti-spam

    • Using Loginizer.  Consider pro version.

    • See about implementing automated callsign lookup to QRZ (code written by Brian, AB6D)