Issue: Suggest forum post text for wiki inclusion

This is one of those features that ties deep into why its beneficial to run Vaultiwki instead of wikimedia. If ANY forum member can quickly suggest a text for wiki inclusion then this has tremendous value:
1. select a text. a tooltip will appear similar to xenforo selective quoting.
2. click 'suggest wiki inclusion'
3. type the article name into an autocomplete field and submit.

Please mind that this feature is not aimed at wiki editors. Its intended for the average forum user who is afraid of wiki. If they encounter a text that they feel should be a wiki, then they should be able to suggest it with 3 clicks. And then get on with their normal routine.
Wiki editors can then review the suggestions and include as they desire.

I am certain that if this is added, this will be appealing to many webmasters because it means that ordinary users can get texts into the wiki.

Pegasus, any update on this? This shows that it was accepted, just trying to get an idea of when we might see this?

I think it would be important to also give the option for the moderator/wiki editor to:

• replace the original post text with a notification/link to the wiki article to avoid duplicate content, OR
• place a notification/link-back on the post that it appears as a wiki article

Give the option not only to suggest as a full article, but to include as a link in a link compilation article or as a footnote:

• In this case, users would just suggest a link to the original post and the name of the article where the link should appear
• Also place a link-back on the post

For reference: https://xenforo.com/community/thread...threads.52425/

If I understand you correctly then I would not want this in the form that you describe here. If you make it please make sure that we can disable this globally. Duplicate content is not an issue at all when it concerns single posts in a thread. The whole page/thread is significantly different. And in many cases the editor would rewrite the text to some degree.
What would be very useful is if a post that was (partially) included in a wiki, would get a link to that wiki.

It would be useful if the wiki editor has the option to include a link to the original content. However, there are many cases where the link is not relevant.

I think it would be extremely useful to be able to create such a ToC in threads or to do cross site linking. The Vaultwiki autolinks are very powerful in terms of SEO and usability. If VW would offer more such tools then this would be very good. A reference manager would also be such a useful tool.

I agree with you that duplicate content is not an issue concerning single posts in general. And I personally don't like the idea of removing non-SPAM content from otherwise normal threads. However, some people, specifically one in the thread I linked, believe otherwise regarding duplicate content, and I was thinking that the first option might give them a means to limit that easily.

However, I do think there is some merit in the argument that duplicate content may occur if we have a relatively authoritative post as the first post that then gets suggested and included in nearly identical form. Since both the original thread and the new wiki article would be nearly identical for a greater portion of the page content, in this case, someone might just want to use a "moved to the wiki" message.

I do not see a need for blanking out authoritative posts. That would be bad for SEO and would disrupt threads. In 99% of the cases the text would need to be edited to suit the wiki. So there would not be duplicate text. And as illustrated about duplicate text does not equal duplicate content.
The problem may exist in exotic cases and in such cases a moved to wiki text would be useful. But if you give that power to users then it will result in more harm than good.

I was suggesting that the power is given to a moderator, not regular users (like by using the built-in can-delete-posts permission). Obviously if regular users have it, they could maliciously "delete" each other's posts. Apologies if it was ambiguous in my earlier post.

But regular users would be able to suggest a text for forum inclusion right?

Yes, still trying to come up with a design for this feature, but this is what I have come up with so far:

• Regular users would have the power to suggest, using a link at the bottom of a post near "Edit" and "Like" (perhaps "Suggest for Wiki"), and possibly by integrating into XenForo's Select-to-Quote popup if it can be extended. Not sure yet if an existing or separate usergroup permission would be for suggestions, but it would be nice to prevent guest or banned users from using the suggestion system as a spam vector.
  
• Editors can accept suggestions and can choose:
  
  • Create a new article based on the suggestion
  • Merge the suggestion into a suggested existing article or a different article. There would need to be a way to show both the suggestion and the target article's editor on-screen simultaneously.
  
  A great opportunity to integrate footnotes: this page should also suggest a FOOTNOTE to include, to provide a link back to the original post.
  
• Moderators can review the accepted suggestion later (or at accept-time, if a moderator did the accepting). The moderator can decide whether the old post should stay as is or be replaced/flagged as "moved".
  
• Even if the post stays, put a "this post was used as a source in X article" link in the footer of the post. This should be good for SEO and make the original poster happy. Of course this can be an admin option whether or not the link is automatic or needs to be approved by a moderator.
  
• The original poster should get an alert that their post was used as a source. The user that suggested it should get an alert that their suggestion was accepted.

Obviously this can't use the built-in moderation or reporting systems, since that requires that the accepting user be a moderator. The feature would be most useful if anyone that can edit the wiki can look at suggestions. I haven't really come up with this aspect yet, how it would link within the wiki, or how users might get notified of new suggestions.

As you can see there's still a lot to think about before we can nail down a spec for this.

The main thing that is missing in your description is the selection of the wiki by the regular user. I would suggest:

• add 'wiki suggestion' link next to edit / reply links. Much better would be selective quoting popup.
• when this is clicked/selected open an overlay with the text and a wiki article selection field. The latter would be an autofill field similar to how vbulletin tags work.
• The user edits the text, selects a article and submits.
• Members who have edited the page in the past will get an alert.
• Wiki editors will see the number of suggested texts on the wiki article page.
• The wiki editors should have a handy function to insert the text into the article, even if the text is a compilation of snippets suitable for different chapters / paragraphs.
• Once all text is included in the wiki, the suggestion will be marked as accepted or denied.
• References to the original posts should be automatically included. Preferably in APA format.
• Wiki moderators should be able to revert or edit the inclusion.
• If set as such in admincp then the moderator can opt to mark the original post as replaced/moved.
• Always add a link to the footer of the original post to the wiki article / content location.
• The author of the text will receive an alert.

Would this cover it?

Is this paid for feature going to make it into 4.1?

Amazing that I paid for this feature to be included 9 years ago.

Wow

@pegasus do you see any future for this suggestion?

Yes, you may have noticed that we have been working through our backlog of suggestions quite vigorously recently (over the course of RC, we closed over 30). We've reached back to 2010 for a number, so we are getting to them. If we don't plan on getting to one, we generally say so and close the request.

It is unlikely this particular one will appear in 4.1 due to time reasons. RC 3 is supposed to feature-lock the branch, which as the XF2 support branch, wasn't really going to be a full feature branch. We included a small number because:
- They are a baseline for some stuff scheduled for 4.2 (mostly the old 4.1 designation that had to be renumbered and pushed due to XF2's release).
- We will need them to fully migrate off of vBulletin over the next few months.
- To resolve a regression.
- They added to a feeling of better integration with XenForo 2.

There was a debate on whether to include this in RC 3, and it got thrown around quite a bit over the past few months, so it is not ignored.

This is pretty well spelled out in terms of the design, so it's just a question of scheduling - what features build on top of each other, need related new code, or are similar to each other thematically. 4.2 is going to be a full feature release, and will have a lot of things people have been waiting for. I don't see this being pushed later than that. We will be dropping support for some old forum versions to improve development speed.

It should also go faster due to the fact that we basically just rewrote the entire framework in 4.1 to make it run better (more tightly) on XenForo. Not including testing, that took about 9 months, which was time not spent on any features at all. It's work that doesn't need to be done now, so apart from our site migration, it will be full steam ahead with features and 4.2.