should be fixed.I think so far everything is great...code tags are a bit messy though, as seen in one of my threads:
https://forums.freebsd.org/threads/php-fpm-and-nginx-starting-to-have-troubles.64642/#post-377122
Thank you for the hard work with the forum upgrade
should also be fixed.It is good that there are improvements of added thread, bug and ports manpages icons.
Navigation is a little bit more difficult on a mobile phone, and the icons of file name and ports manual page are counter-intuitive, especially on mobile. If possible, it would be better if the Prevent text parsing, HTML Anchor and Deleted icons were grouped closer together, and had a separation from the icons used for referencing man pages, code, commands, etc.
They seem to be removed from the mobile display, and not the desktop. I see how theshould also be fixed.
inline
code tag is better than the highlight tag that I used for its purpose.My guess is that you're aware of using https://validator.w3.org/ to test markup code? With the amount of HTML, CSS and Javascript code here, I realize how much more tedious that is.
This page alone has 69 HTML errors and warnings and 7 CSS errors with 444 warnings.
I tried with FF 29.0.1 and those features work just fine.Hi guys. It seemed that your forum works with Chromium based browser only. When I use Firefox I can't use multiquote and format my code as a specific language, like BASH.
Your version of FF is very old. I'm using FF 58.0.2.I tried with FF 29.0.1 and those features work just fine.
Hi guys. It seemed that your forum works with Chromium based browser only. When I use Firefox I can't use multiquote and format my code as a specific language, like BASH.
Your version of FF is very old. I'm using FF 58.0.2.
So I tried with 58.0.2 on mac and it works just fine too.Your version of FF is very old. I'm using FF 58.0.2.
Should be fixed.They seem to be removed from the mobile display, and not the desktop.
Thanks.First: Thank you for upgrading.
Minor complaint: When replying to a post, or editing a post, sometimes a lot of "[" bgcolor = xxx "]" and "[" /bgcolor "]" show up out of nowhere, and the end up being displayed in the post. I can edit the post and hunt them down manually, but that's a hassle. What makes it slightly more interesting is that the editor automatically adds closing tags at the end, so if in hunting them down I miss a few, there is a slew of "[" /bgcolor "]" at the end of the post, requiring another pass over it.
I'm using Chrome 64.0.... on MacOS.
Did I mention thank you for upgrading, and for dealing with all the minor complaints?
[BGCOLOR=transparent][/BGCOLOR][BGCOLOR=transparent]Do you have a specific example of where it happens?[/BGCOLOR]
OK and you just clicked the Reply button, wrote your text and clicked Post reply button and this happened?And it just happened again when quoting your post! See above. Not going to edit it this time, so you can see it.
Sorry, overlooked your question. Exactly: Click reply, there were no "bgcolor" visible in the editor window, wrote my reply, hit "post reply" button.OK and you just clicked the Reply button, wrote your text and clicked Post reply button and this happened?
Thats quite strange indeed. Didnt happen to me yet and nobody else have reported this before. What browser are you using? Could you maybe try with a different one?Sorry, overlooked your question. Exactly: Click reply, there were no "bgcolor" visible in the editor window, wrote my reply, hit "post reply" button.
Now I wonder what extraneous text will show up in this reply. Perhaps something about flying purple elephants?
That's kind of what I said, but perhaps I didn't figure to the extent of massive.The problem is, that's not danger@'s code. That's XenForo code and if you've taken a look at it cleaning it up is a massive job.
Use www/bluefish or an html editor that automatically points out errors like unclosed tags (I forgot if bluefish does that).
Validating it cuts down on a lot of work of finding errors.Validate it? According to drhowarddfine that is a job unto itself:
I didn't bother running it myself. No point.
Doesn't happen all the time. I'll switch from Chrome to Firefox for this forum after this post. And honestly, if I'm the only person who has this problem, just ignore it; it can always be edited away.Thats quite strange indeed. Didnt happen to me yet and nobody else have reported this before. What browser are you using? Could you maybe try with a different one?
It is not bad, but it introduce some "side-effects", for example, a friend of mine, also a forum administrator,back in the time when we were building this forum we have of course evaluated several forum software packages including SMF, vB, phpBB etc and it was concluded that XF was the best option for us.
FF 58.0.2 on MXLinux has this issue, on FreeBSD I use Chromium so I don't know.So I tried with 58.0.2 on mac and it works just fine too.