Hashtag in Posts [library support]

[Ishy]

With div styles it doesn't work when you need to use background-color, color, or border-color. I tried adding the & and it converted it anyways, ignore the &.

[adminabp]

Nov 12, 2014 18:30:18 GMT -8 Wormopolis said:

Nov 12, 2014 9:40:07 GMT -8 adminabp said:

I run a primarily comic book-related forum, and I figured with things like issue numbers (ie Batman #314) etc there would be some unwanted conversions with this plugin, but I didn't foresee any real problem.

Then I did what I usually do every Wednesday, paste a list of the day's new comic book releases into a thread. It turned the #'s into unwanted click-able links, but no real problem.

Then I went back to work on the custom home page I'm making, which has at it's center a widget displaying recent posts. Only it's displaying what I posted like this:

All-New Captain America [HASH]1 (Alex Ross Variant Cover), AR
All-New Captain America [HASH]1 (Blank Variant Cover), AR
All-New Captain America [HASH]1 (Carlos Pacheco Variant Cover), AR
All-New Captain America [HASH]1 (Kris Anka Colbert Variant Cover), AR
All-New Captain America [HASH]1 (Paul Pope Rocket Raccoon & Groot Variant Cover), AR
All-New Captain America [HASH]1 (Rae Sremmurd Custom Interscope Variant Cover), AR
All-New Captain America [HASH]1 (Sara Pichelli Variant Cover), AR
All-New Captain America [HASH]1 (Skottie Young Variant Cover), AR
All-New Captain America [HASH]1 (Stuart Immonen Regular Cover), $3.99
All-New Ultimates [HASH]10, $3.99
Avengers And X-Men Axis [HASH]5 (Of 9)(Dave Johnson Inversion Variant Cover), AR
Avengers And X-Men Axis [HASH]5 (Of 9)(Jim Cheung Regular Cover), $3.99
Avengers And X-Men Axis [HASH]5 (Of 9)(Sara Pichelli Young Guns Variant Cover), AR

Literally like over 400 #'s in a list all displaying as [HASH], and all un-clickable text. I don't really need for the plugin to convert those #'s into clickable links in the first place. I only really want the plugin to run on a couple of my boards, primarily for fan-art and fan-fics to allow for easy searching by character. Would it be possible to be able to select which boards it runs on?

And on a side note, I have a suggestion for the plugin, but I have no idea if it is even doable with the search feature. Put the #HASHes into some kind of a custom field, a HASH-Box if you will, and have everything outside of that ignored.
Like:

#example #cool-idea #solve-A-LOT-of-problems-if-possible
You are the brains that makes stuff happen, I am at best a humble idea-monkey. Would be cool if possible though...

So you have provided a good example of needing someway to NOT convert to hashtag.  my problem is what is the difference?  how would you tell a computer "Oh I MEANT for those to be hashtags and not those".  I could try a minimum length clause but then if you had #123456 out of 1000000 it would try to still convert that if you set a minimum of 6.  If we change the symbol used for hashtags, then it isnt really a hashtag code anymore.  There IS the possibility that when you want to use the # symbol without the code seeing it, you could enter "#" where you actually wanted the symbol and I could make it never convert if the & symbol is immediately before it


the problem with a "hash-box" is when you go to save the post the contents are still part of the post unless you use a key. but then keys arent searchable using the built-in search system. if stored in the post, it would have to add more content into the post to provide a way to differentiate what was tags.

Let me start by saying I am not trying to be critical, this is a great idea, and an awesome plugin. It also not something I could do and I appreciate you making it for all the forum users.

I don't think I articulated what I meant by custom field very well, I was going on too little sleep. I wasn't talking about something separate from the post like with the Administrator Note plugin, I meant a BBC field specific to the plugin.

Imagine that there was no way to bold text, and someone made a plugin to do it. But the trigger was that the first letter of the word was capitalized, so Bold automatically becomes Bold. The problem then becomes how to use capitalization without triggering the bold formatting by adding extra symbols or spaces before or after capitalized words. That bold plugin would be completely opt-out functionally, casting too wide a net and forcing posters to reformat their posts to avoid getting caught in it.

Ideally, you would want that plugin to be opt-in, specifically targeted to what you wanted made bold. Hence the [b][/b]
The # symbol isn't some arcane thing rarely used, it's commonplace, especially in conjunction with numbers. You don't want every time a poster posts "we're #1" to have a click-able search-link for the number "1", or have to reformat a large amount of text if they are copy/pasting it from somewhere else because it has a lot of #'s in it. My thought was to have a bbc for hashtags, like:

[hashtags]#example #likethis[/hashtags]
#words inside of it would become click-able links when posting, And any #'s outside of that would be ignored and treated as just text.

Is that doable?

[Wormopolis]

yeah I have used custom tags before.. I think my goal on this one was to NOT have to resort to them. making it more similar to facebook or twitter where you literally just type them and they convert (except it still requires the necessary submission process before converting).

everyone keeps finding more and more example of when they DONT want hashtags.. I might have to resort to going back to using [#] like the very first version had. or maybe making it where you could surround content with [nohash][/nohash] and it wouldnt convert it upon submission.

[Ishy]

Nov 13, 2014 8:42:46 GMT -8 Wormopolis said:

yeah I have used custom tags before.. I think my goal on this one was to NOT have to resort to them. making it more similar to facebook or twitter where you literally just type them and they convert (except it still requires the necessary submission process before converting).

everyone keeps finding more and more example of when they DONT want hashtags.. I might have to resort to going back to using [#] like the very first version had. or maybe making it where you could surround content with [nohash][/nohash] and it wouldnt convert it upon submission.

I think setting it up as [#]hashnamehere would be perfect! I don't mind having to add an extra two symbols to differentiate hash and not hash to prevent this but making it so people have to put a whole [nohash] tag around the content they don't want hash's in would be a bit much. Most people wouldn't think to do that when posting their templates and it would just make more sense for people to post it when they do want it rather than when they don't.

[adminabp]

Nov 13, 2014 8:42:46 GMT -8 Wormopolis said:

yeah I have used custom tags before.. I think my goal on this one was to NOT have to resort to them. making it more similar to facebook or twitter where you literally just type them and they convert (except it still requires the necessary submission process before converting).

everyone keeps finding more and more example of when they DONT want hashtags.. I might have to resort to going back to using [#] like the very first version had. or maybe making it where you could surround content with [nohash][/nohash] and it wouldnt convert it upon submission.

Nov 13, 2014 9:49:30 GMT -8 Ishy said:

I think setting it up as [#]hashnamehere would be perfect! I don't mind having to add an extra two symbols to differentiate hash and not hash to prevent this but making it so people have to put a whole [nohash] tag around the content they don't want hash's in would be a bit much. Most people wouldn't think to do that when posting their templates and it would just make more sense for people to post it when they do want it rather than when they don't.

I think the opt-in is so much better than an opt-out. Constantly trying to explain to new members they need to wrap any text with a # in it with [nohash][/nohash] tags or else it will convert to a #hashtag would be a PITA. I gave this plugin a try when I first made my forum back in the spring because I saw clear potential uses for my forum, but removed it after only a few days because it was converting too many things not intended to be #hashtags into #hashtags. On a comic book discussion forum people use # before issue numbers all the time, it's literally the standard way issues are listed.

Then I saw the new #hashcloud plugin which looks very cool and I though I'd give this plugin another try to see if it worked any differently after several months of potential changes. Right now if I had the new #hashcloud plugin installed on my forum, literally everything listed in it would just be numbers.

Either [#] with each word or [#]#example #likethis[/#] to do more than one would be great. Since, unless I'm mistaken, any custom BBC would only work on a webpage with the plugin running to add it; it would be easy enough to put in a custom BBC button using another plugin that does that or if you want have this plugin have a button that adds it itself like ColorSmear does. I think I would prefer [#]#example #likethis[/#] simply because you could type as many #hashtags in a  row as you want and then simply highlight the text, click a BBC button(either added by this plugin or another one) and have that whole section wrapped. People understand wrapping formatting code tags around things all the time on message boards, from urls to text, #hashtags really doesn't need to be any different.

But yeah, I think we really need to have more control over what is getting converted. I get wanting it to be exactly like Twitter etc., but this is a message board; maybe better to imitate and adapt that functionality in a way that is more compatible with how people normally use message boards than an exact copy that causes problems?

[Wormopolis]

the tray button is still something I havent mastered. the one for colorsmear doesnt even work right but I was trying to make an attempt. the testing version of colorsmear has a working button, but I ran into an issue getting it to work for IE8 so I have held back on releasing it until I can find a script that works.

So I guess what I will do, is have it require [#]hasword if you want a tag. each tag will need a [#] in front of it. any existing posts that already HAVE hashtags will still display as normal. if you edit an older post, it will convert existing tags to have [#] in front of it. if you DONT want them to become hashes, just change it to # and upon submit it wont convert again.

[Ishy]

I think that would be perfect!

[adminabp]

I agree, that would be perfect! Thank you so much Wormo!

[Wormopolis]

v1.2.0 submitted

changed it so hashtag has to have [#] in front of it to eliminate accidental hashtags. apparently all the regexp in the world couldnt stop it.

[Ishy]

Curious, how long does it take for the updates to appear in the Plugin Library? Because it still says its version 1.1.7.

[Wormopolis]

That is up to the librarian. I would think normal office hours would bring them around

[adminabp]

New version is in and it is working wonderfully!

Taking the new Hashcloud out for a spin now, too.

[adminabp]

Discovered a minor problem. I was trying to explain how to use this in a post on my forum, and when trying to type a demonstration, discovered it will convert the [#] even inside a codebox. It doesn't make a click-able link there, but it does convert [#] into [HASH] even inside the box.

It also adds the hashtag used in the codebox to the hashcloud plugin, and that is as a click-able link.

[Ishy]

You could try [*#*] and tell them to remove the asterisks. That's what I do when I add a code box within a code box so it doesn't convert.

[Wormopolis]

yeah I cant really seperate out things from inside a code box without resorting BACK to the regexp everyone said wasnt working. you can also use the nested bbcode method:

[#[b][/b]]

and the parser wouldnt show the bold tags