• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 3.x Series
    • Bug
    • Make pages.php more intuitive

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Make pages.php more intuitive

    • Issue Tools
      • View Changes
    1. issueid=2732 June 1, 2012 11:20 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Make pages.php more intuitive

      I'm not entirely sure if this is a task, a bug or both.
      Pages.php is confusing when it comes to the display of comments, discussions and the associated functionality.

      Looking at the page its clear that there are multiple buttons to start comments or discussions.
      Its not clear what the difference is. The page should make clear what the functions are for. Possibly on hover or by improving the buttons / text.
      Then there is a big block at the bottom, which has in bold large text: 'Post New Comment'. It shows a lot of whitespace, and a button 'post new comment'
      Below the whitespace there is a default button to post new comment or the go to the advanced editor. It seems to me that this is currently unfinished and ckeditor will be implemented later. If not, then this part of the page needs to be reviewed.
    Issue Details
    Issue Number 2732
    Issue Type Bug
    Project VaultWiki 3.x Series
    Category Editing / Posting Articles
    Status Fixed
    Priority 1 - Security / Login / Data Loss
    Affected Version 4.0.0 Alpha 1
    Fixed Version (none)
    Milestone (none)
    Software DependencyAny
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. June 2, 2012 12:28 AM
      pegasus pegasus is offline
      VaultWiki Team
      ckEditor was broken due to a bad database backup we used. I fixed the relevant database tables and it's back now.

      The difference between the Post New Discussion / Post New Comment:
      Post New Comment will show the comment on the current page (unthreaded).
      Post New Discussion will create a thread where comments can be added separate from the ones on the current page.

      Think of Post New Comment as posting on the page's wall (ala Facebook), and Post New Discussion is a separate thread from the wall.
      Reply Reply  
    2. June 2, 2012 2:49 AM
      pegasus pegasus is offline
      VaultWiki Team
      I think the best solution might be to change the word "Discussion" to "Topic" in most locations. We use the word "Topic" in the AdminCP to refer to something else (admin-created global discussions), but it's probably safe to use this word interchangeably in the front end since I don't think a distinction is ever made. However, developers and modders should still be aware that there's a difference, since they are stored differently.
      Reply Reply  
    3. June 2, 2012 12:41 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      The difference between post new discussion and post new comment seem clear enough and the word topic is not needed. But:

      1. You said that the 'post new discussion' function is for page descriptions. This is where I get confused. For example on the page pages.php?title=Help I posted a discussion. I would expect to be taken to a function to start a new thread. Instead there is a small comment box and small title field. Instead of a thread function to discuss issues surrounding the page, this seems to be a page description? Please explain this function.

      2. There is 1 'post new discussion' function, 2 'post new comment' buttons and a 'post new comment' editor. There seem to be 2 superfluous 'post new comment' buttons that need to be removed. Why are 3 'post new comment' functions needed for the same page?
      Reply Reply  
    4. June 2, 2012 12:52 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      When clicking on 'post new discussion' I am taken to pages.php?title=Help&do=comments&action=talk
      The url states do=comments not do=discuss
      This indicates to me that this is a comment, not a discussion.
      Reply Reply  
    5. June 2, 2012 3:41 PM
      pegasus pegasus is offline
      VaultWiki Team
      I have reorganized the buttons so that Post New Discussion and Post New Comment are not next to each other.
      Also I removed the "Comments for: X" header from above the discussion list, and added a separate header below it before the start of the current page's comments, which more explicitly states which discussion you are currently in.
      Reply Reply  
    6. June 2, 2012 7:53 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Now the the post new discussion works, its clear how its supposed to work.

      There still are 2 comment functions: one button and one CKEditor. It should be one or the other. Not both.

      Some suggestion for improvement:
      - To avoid confusion place a colon between 'Pages in' and the article name. And also a colon between 'Discussions for' and the article name. This avoids confusions like 'discussions for help'.
      - Place a subtle separator between each discussion.
      - The post new comment' and 'go advanced' buttons should have the same appearance as the other 'post new comment' buttons.
      Reply Reply  
    7. June 2, 2012 8:19 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      I have just posted this in a bug report for discussions:

      The description defines what the discussion is about and what the issue is. For example it needs to be discussed that something is wrong about the page/article or a statement is disputed. Therefore its very important that the discussion clearly shows the description. I would even go as far as putting the description at the top of each discussion page and putting a clear border around it to make it stand out.

      Because the description describes an issue, dispute, etc, 200 characters are not enough for the description. I suggestion to have the full description on the discussion page, while only showing a limited amount of text on the main page.
      - I suggest to rename 'Short Description' to 'Discussion Summary'
      - The summary should have an editor for a few bb codes and allow more characters.
      - The main page should show a preview of the summary, with a 'read more' link.
      - The Discussion summary on the main page can have a smaller font, reduce the space between the left border and the text, and move the Last update bit to the right, to make better use of the available space.
      Reply Reply  
    8. June 8, 2012 4:00 PM
      pegasus pegasus is offline
      VaultWiki Team
      Renamed Description to Summary, but not adding an editor for BB-Codes or more characters. That's not what the summary is for - it's not searchable and not designed to be used as a first post. Instead, users should create a first post. There is already a request to put the first post editor on the New Discussion screen, and we already have a Sticky Comments feature in mind for the future, so I'm closing this issue. The OP was only about the presentation of discussions vs. comments at the page level anyway.
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 1:17 AM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.