Reasons why we switched to WordPress and quit flarum
-
@Sala I’ve spent some time this morning reviewing your WordPress configuration. The issue of the duplicated
h1tag is being caused by AnsPress - you’ll no doubt recall I warned against using this “plugin” (if you can call it that - it’s terrible) herehttps://sudonix.com/topic/358/fresher-in-nodebb-install/6?_=1674640646763
AnsPress is well-known in WordPress circles for being one of those plugins you’d avoid at all costs. I used it once - never again. It causes far too many issues, and provided you don’t mind your site suffering as a result in terms of performance, bugs, and the like, then ok. In relation to SEO, see the below
https://anspress.net/questions/question/seo-issues/
This was reported in October 2022, and it’s still not fixed.
From my own independent review, I also see the following issues
The most damaging of these is content being served on both non-www and www URLS, which needs to be fixed ASAP. You’ll note that the
h1heading appears twice (which you’re already aware of)
However, aside from SEO, I see far more important issues that you need to resolve first
- TTFB (Time to First Byte) - the page is incredibly slow to load - in some cases, it takes 2-3 seconds before any content is shown. This is a killer in itself as more than one second loading time is considered far too high.
- 301 redirects are missing - in this case, you should have a global redirect so that the content is being served from the same domain at all times.
The bottom line here, and the “fix” is to remove AnsPress. Clearly, this isn’t palatable from your perspective as there is significant investment on your side. I know from previous discussions that AnsPress was shipped with the theme you are using, but it’s a below-par plugin in terms of performance and stability.
You’ll see below my attempts to get AnsPress working as far back as 2017 - I promptly gave up, because it was such a mess
https://theme.co/forum/t/anspress-plugin-with-x-pro-integrity-stack/14015
And finally, one very well respected WordPress resource (wpcrafter.com) parted ways with AnsPress in 2018 for similar reasons, which he clearly stated
At this point, I would weigh up the investment in AnsPress and seriously consider removing it.
@phenomlab I created Reasons why we switched to WordPress and quit flarum bing index issues and backlinked to one of @Hari posts in Sudonix. Looking hot
By the way i tried to resolve many issues, including ttfb now its
-
@phenomlab I created Reasons why we switched to WordPress and quit flarum bing index issues and backlinked to one of @Hari posts in Sudonix. Looking hot
By the way i tried to resolve many issues, including ttfb now its
Flarum also has security issues
This might be a little unfair on them seeing as they responded to this specific issue and remediated it. Currently, to my knowledge, there are no other vulnerabilities identified, and based on this, I don’t think it’s fair to assume there are.
As you know, I’m not a fan of flarum by any means given it’s complete lack of out of the box GDPR compatibility, but I wouldn’t state this omission if it were to be included in the core.
-
Flarum also has security issues
This might be a little unfair on them seeing as they responded to this specific issue and remediated it. Currently, to my knowledge, there are no other vulnerabilities identified, and based on this, I don’t think it’s fair to assume there are.
As you know, I’m not a fan of flarum by any means given it’s complete lack of out of the box GDPR compatibility, but I wouldn’t state this omission if it were to be included in the core.
@phenomlab the problem is that the issue has been around for quite some time. All versions below the patched one had this security loophole. So it’s important to state it. If it took 5 years to know it, let newbies be aware that it’s a playground for serious developers or just a batch to toy with your wallet and dreams.
-
@phenomlab the problem is that the issue has been around for quite some time. All versions below the patched one had this security loophole. So it’s important to state it. If it took 5 years to know it, let newbies be aware that it’s a playground for serious developers or just a batch to toy with your wallet and dreams.
@Sala you’re making points here which are hard to argue - and I certainly won’t refute then as they are well known (and well suffered certainly by me directly).
There’s also the time it took to reach “stable” - 5 years. Given the arrival of Blomstra, it was clear from the start in terms of the intention to monetize, and it seems to be a focal point.
The final comment from me would be around keeping the core minimal. Both GDPR and SEO capacities should both be an out of the box experience when they are not. It seems that flarum has taken the stance that the core will be a framework to hand other things on - those “things” being in the form of extensions.
Keeping the core “lean” is another way of distancing yourself so there isn’t the need to commit to what should be base (and free) functionality or develop and then allow poorly written extensions to hook into the core and effectively slow it down.
Community extensions should not have to bridge the gap between what is a usable product and one that is effectively useless in today’s evolving market.
Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…
-
undefined phenomlab marked this topic as a regular topic on 22 Feb 2023, 12:05
-
undefined phenomlab moved this topic from WordPress on 22 Feb 2023, 12:12
-
@phenomlab the problem is that the issue has been around for quite some time. All versions below the patched one had this security loophole. So it’s important to state it. If it took 5 years to know it, let newbies be aware that it’s a playground for serious developers or just a batch to toy with your wallet and dreams.
@Sala I decided to fork this topic away from the original thread, as I think this deserves a discussion in it’s own right. I’ll be adding more comments here to further bolster the points I made above.
-
@Sala you’re making points here which are hard to argue - and I certainly won’t refute then as they are well known (and well suffered certainly by me directly).
There’s also the time it took to reach “stable” - 5 years. Given the arrival of Blomstra, it was clear from the start in terms of the intention to monetize, and it seems to be a focal point.
The final comment from me would be around keeping the core minimal. Both GDPR and SEO capacities should both be an out of the box experience when they are not. It seems that flarum has taken the stance that the core will be a framework to hand other things on - those “things” being in the form of extensions.
Keeping the core “lean” is another way of distancing yourself so there isn’t the need to commit to what should be base (and free) functionality or develop and then allow poorly written extensions to hook into the core and effectively slow it down.
Community extensions should not have to bridge the gap between what is a usable product and one that is effectively useless in today’s evolving market.
@phenomlab said in Reasons why we switched to WordPress and quit flarum:
It seems that flarum has taken the stance that the core will be a framework to hand other things on - those “things” being in the form of extensions.
Keeping the core “lean” is another way of distancing yourself so there isn’t the need to commit to what should be base (and free) functionality or develop and then allow poorly written extensions to hook into the core and effectively slow it down.That’s interesting you say this, because this is exactly the stance that NodeBB has taken as well. Perhaps not overtly so, but if you ask me directly, that’s my usual go-to line.
That said, I suppose the difference lies in what we perceive as necessary in terms of “batteries included”. It essentially boils down to what proportion of people would want feature X? If it’s something higher than say, 80%, then that’s a pretty good reason to include it out-of-the-box.
SEO and GDPR were two things specifically that we decided must be included… I mean, who doesn’t want better ranking on search engines?
-
@phenomlab said in Reasons why we switched to WordPress and quit flarum:
It seems that flarum has taken the stance that the core will be a framework to hand other things on - those “things” being in the form of extensions.
Keeping the core “lean” is another way of distancing yourself so there isn’t the need to commit to what should be base (and free) functionality or develop and then allow poorly written extensions to hook into the core and effectively slow it down.That’s interesting you say this, because this is exactly the stance that NodeBB has taken as well. Perhaps not overtly so, but if you ask me directly, that’s my usual go-to line.
That said, I suppose the difference lies in what we perceive as necessary in terms of “batteries included”. It essentially boils down to what proportion of people would want feature X? If it’s something higher than say, 80%, then that’s a pretty good reason to include it out-of-the-box.
SEO and GDPR were two things specifically that we decided must be included… I mean, who doesn’t want better ranking on search engines?
@julian said in Reasons why we switched to WordPress and quit flarum:
That said, I suppose the difference lies in what we perceive as necessary in terms of “batteries included”. It essentially boils down to what proportion of people would want feature X? If it’s something higher than say, 80%, then that’s a pretty good reason to include it out-of-the-box.
And there lies the exact answer. GDPR and SEO are in my view fundamental basics which should be included with the core product. Interestingly, when I left flarum, they still had no functional GDPR extension and took a somewhat maverick view as to how it should be handled, which as a privacy advocate and security expert by trade, this didn’t sit well with me at all.
They are also marketing Blomstra, their paid service out of Europe where for example, Germany have some of the toughest data protection laws around - yet have no formal GDPR facility. Complete madness.
NodeBB has GDPR and SEO out of the box, amongst a whole array of other utilities which makes it light years ahead of flarum. Even with all this extra functionality, NodeBB easily outperforms flarum mostly due to being nodejs based against PHP - and it’s never slow.
I totally understand the concept of a lean core, but when that comes at the cost of negating what should be a baseline for any forum to be able to operate, it’s the wrong model and will cause damage in the long run. Sure, you can’t accommodate everything, and I’m no fan of bloat, but going from flarum to NodeBB was literally night and day in terms of the overall experience alone.
Flarum has an extensive community, but with so much reliance on third party extensions and a product that took 5 years to leave beta, it’s future is questionable in my view.
-
@julian said in Reasons why we switched to WordPress and quit flarum:
That said, I suppose the difference lies in what we perceive as necessary in terms of “batteries included”. It essentially boils down to what proportion of people would want feature X? If it’s something higher than say, 80%, then that’s a pretty good reason to include it out-of-the-box.
And there lies the exact answer. GDPR and SEO are in my view fundamental basics which should be included with the core product. Interestingly, when I left flarum, they still had no functional GDPR extension and took a somewhat maverick view as to how it should be handled, which as a privacy advocate and security expert by trade, this didn’t sit well with me at all.
They are also marketing Blomstra, their paid service out of Europe where for example, Germany have some of the toughest data protection laws around - yet have no formal GDPR facility. Complete madness.
NodeBB has GDPR and SEO out of the box, amongst a whole array of other utilities which makes it light years ahead of flarum. Even with all this extra functionality, NodeBB easily outperforms flarum mostly due to being nodejs based against PHP - and it’s never slow.
I totally understand the concept of a lean core, but when that comes at the cost of negating what should be a baseline for any forum to be able to operate, it’s the wrong model and will cause damage in the long run. Sure, you can’t accommodate everything, and I’m no fan of bloat, but going from flarum to NodeBB was literally night and day in terms of the overall experience alone.
Flarum has an extensive community, but with so much reliance on third party extensions and a product that took 5 years to leave beta, it’s future is questionable in my view.
@phenomlab there is also a bad link structure for example /d/-32 and /d/33/
If they decide to restructure those links back to normal, so many links would be lost on searches. So it’s either they continue to sit on it and let it look bad, or they force the implementation. We all know that even when you decide to use an old Flarum (and keep the old links), you will somehow be forced to change to the new Flarum because, as time goes on, most extensions will not work and Flarum is not easily editable like WordPress.
-
@phenomlab there is also a bad link structure for example /d/-32 and /d/33/
If they decide to restructure those links back to normal, so many links would be lost on searches. So it’s either they continue to sit on it and let it look bad, or they force the implementation. We all know that even when you decide to use an old Flarum (and keep the old links), you will somehow be forced to change to the new Flarum because, as time goes on, most extensions will not work and Flarum is not easily editable like WordPress.
@Sala If they did change it, they’d have to create a mechanism that generates 301 redirects otherwise, as you say, there would be dead links all over the place. I never fully understood this schematic (apart from the obvious being “d” = discussion), but it’s clear they took this route to shorten the overall URL.
Either way, it’s ugly from the cosmetic approach at the least.
Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…
-
@Sala If they did change it, they’d have to create a mechanism that generates 301 redirects otherwise, as you say, there would be dead links all over the place. I never fully understood this schematic (apart from the obvious being “d” = discussion), but it’s clear they took this route to shorten the overall URL.
Either way, it’s ugly from the cosmetic approach at the least.
@phenomlab It’s not my place to judge whether
/d(or/tin Discourse) is better or worse than other implementations, I just personally consider that part of a site’s overall API, and — without even considering SEO value — a single letter endpoint makes little sense from a readability perspective.That said, if their router allows regex, it’s fairly simple to have it serve up HTTP 301/308 on the old route
It also suffers from the same problem we have… that we’ve hardcoded
/topicand/category(among other routes), and it’s English, yet we live in a multi-lingual world
-
@phenomlab It’s not my place to judge whether
/d(or/tin Discourse) is better or worse than other implementations, I just personally consider that part of a site’s overall API, and — without even considering SEO value — a single letter endpoint makes little sense from a readability perspective.That said, if their router allows regex, it’s fairly simple to have it serve up HTTP 301/308 on the old route
It also suffers from the same problem we have… that we’ve hardcoded
/topicand/category(among other routes), and it’s English, yet we live in a multi-lingual world@julian said in Reasons why we switched to WordPress and quit flarum:
It also suffers from the same problem we have… that we’ve hardcoded /topic and /category (among other routes), and it’s English, yet we live in a multi-lingual world
Yes, and this is always going to be a downside. However, I think the URL itself is generally accepted to be in English, but the content isn’t.
-
@phenomlab I created Reasons why we switched to WordPress and quit flarum bing index issues and backlinked to one of @Hari posts in Sudonix. Looking hot
By the way i tried to resolve many issues, including ttfb now its
@Sala I remember a year ago when I was on the Flarum forum, crying like a baby without realizing how terrible their ecosystem was, despite having a beautiful theme. Now, we’ve transitioned to SiForum and created a custom theme that looks exactly like Flarum. We’ve replaced the composer with WPDiscuz, added a block for related discussions on the discussion page, and created related category pages for each category. The search function works wonderfully, and with the help of redirection and SEO plugins, I now have complete control over my site. Plus, Google now recognizes all of my pages. I feel alive and fulfilled.
-
@Sala I remember a year ago when I was on the Flarum forum, crying like a baby without realizing how terrible their ecosystem was, despite having a beautiful theme. Now, we’ve transitioned to SiForum and created a custom theme that looks exactly like Flarum. We’ve replaced the composer with WPDiscuz, added a block for related discussions on the discussion page, and created related category pages for each category. The search function works wonderfully, and with the help of redirection and SEO plugins, I now have complete control over my site. Plus, Google now recognizes all of my pages. I feel alive and fulfilled.
@Hari thanks. For anyone looking for the SiForum theme, you can find that here
-
You should except something like this slowing down your flarum
-
@Sala that’s pretty hard to read, but with that many extensions, no wonder it’s slow.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (ether email, or push notification). You'll also be able to save bookmarks, use reactions, and upvote to show your appreciation to other community members.
With your input, this post could be even better 💗
RegisterLog in
