Hashtags

[deleted]

@010101
I don't get any errors.
Anyway, thanks again for all hard work!

010101

@[deleted] and @Aleram - The latest version (3.1) should fix what you are experiencing. 😄

Aleram

010101 Yes it works!
Thank you very much for the work done! )

[deleted]

Sorry, but v3.1 doesn't work for me. I will try again.

Aleram

[deleted] Can you link to the page?

010101

[deleted] I’d have to take a look at your site and see if I see anything that could be causing it. Now that it is working for both me and @Aleram it’s going to be even harder to troubleshoot. If I could visit your forum I could view the page source and at least see if the right JavaScript is loading or not.

010101

Version 3.3 is here! 🥳

Fixed a bug (sometimes a single lone hashtag was not converting)

... and that is all that is new with 3.3. But, 3.0 brought:

Compatible with all languages
Ignores punctuation (it did before but, making it compatible with all languages meant re-doing this part as well as the following feature)
Ignores hashtag if something precedes it (which helps to avoid html and markup conflicts)

To update you may try the regular update command (see first post of this thread), but sometimes depending on caches and other factors that does not work for me personally. You may instead deactivate and remove the old version completely using composer remove zerosonesfun/hashtags and then reinstall with composer require zerosonesfun/hashtags. Then of course reactivate the extension. 🙂

If you have issues with this extension I can try to help but at a minimum I need a link to a post at your forum which has hashtags. This allows me to view your source code where I am able to confirm if the latest version got installed or not. Plus, I might see something else which could help to solve your issue. Thank you!

[deleted]

@010101 version 3.3 solved problem! 😁
Hope to see more extensions from you!

P.S. Noticed that hashtags are not working with words in lists

010101

[deleted] Good to hear! Not working in lists is a “feature.”

The code purposely will not create a linked hashtag if it is up against markdown or HTML. I don’t recall 100%, but I think I added this feature because long ago this extension was conflicting with another one. And it was because it was conflicting with some dynamically added HTML that the other extension was adding.

In short, you can only have hashtags either alone on their own line, or within a normal sentence. 🙂

[deleted]

010101 In short, you can only have hashtags either alone on their own line, or within a normal sentence. 🙂

All clear. Thanks, man!

djalmasi

The hashtags not working with FoF Formating. Because i got this message

Hozzászólás keresése ugyan ilyen jelöléssel c#c0392b; color: white;\' class=\'uncited\'>
'+app.translator.trans('fof-secure-https.forum.removed')+' | '+app.translator.trans('fof-secure-https.forum.show')+'

');$(this).hide();" onload="$(this).next().empty();" class="securehttps-replaced" src="https://djalmasi.hu/privat/fulltimehosting/01.png" title="" alt=""> Loading Image

010101

djalmasi More information is needed. This does not show how/why this would be the hashtags extension. I see the fof secure https extension may be having trouble loading an image?

clarkwinkelmann

djalmasi 010101 I suspect this is an issue with Secure HTTPS, which inserts HTML with a HEX color (background-color: #c0392b;) as well as some URL-encoded quotes (&#92) that might be interpreted as hashtags by this extension.

In fact, I'm pretty sure the way this extension is implemented will break if there's a # character in any HTML attribute or script tag (with the required spacing around it), since the code performs a replace on the raw HTML instead of the text parts.

djalmasi

010101
If i turning on the Hashtags, somehow the code complicated. Certain words preceded by a # sign. And so the automatic code converter gets stuck and can't perform automatic image loading.
I attached a video. (Sorry for the background noise, I forgot to turn off the microphone.)

010101

djalmasi I’ve been busy, just taking a look at your video. It’s too blurry. I cannot tell what you’re trying to do. I assume it is an image URL that happens to have a “#” in it? Is that what’s happening? So you are posting something like:

https://www.website.com/#image.png

djalmasi

clarkwinkelmann Thank you. Then I'll try to get help there.

clarkwinkelmann

djalmasi the problem is definitely this extension, because it's replacing raw HTML where it shouldn't.

Another way to reproduce without Secure HTTPS is to insert an image alt text with a hashtag, like

An image ![Nice #description](http://lorempixel.com/400/200)

djalmasi

clarkwinkelmann In fact, this script should be improved if I understand correctly.

clarkwinkelmann

010101 see my post above. In @djalmasi case the # is added by Secure HTTPS itself as part of its HTML, so it will basically happen anytime Secure HTTPS replaces an image. In my simpler example clarkwinkelmann the # is added by myself as part of an alt image attribute.

I doubt this can be fixed just by editing the regular expression. It's impossible to "parse" HTML via a regular expression to isolate text nodes vs markup.

My suggested solution without re-writing how the whole extension works would be to "walk" down the HTML nodes and run the regex on each text node that's inside a paragraph, instead of altering the innerHTML of the whole paragraph.

clarkwinkelmann

djalmasi yes, this extension is super basic. If you look at the source on GitHub you will see it performs a regular expression replace on the innerHTML value of paragraphs, which is not a very good practice. But apart from breaking formatting under some circumstances like these, I don't think there's any easy XSS.

The ideal implementation would be as a TextFormatter custom tag, but it's more advanced for developers.

010101

Hey there folks! This is probably fixable by adjusting the regular expression. In fact, a regular expression I used in the past might have prevented this, but I recently re-did the regular expression so that other languages would work. I guess we all have our opinions but with the perfect regular expression the way this is coded is fine.

« Previous Page Next Page »