@Madchatthew I’d always post for the reasons I stated above. It’s useful information and could save someone else the headache.

@Sala yes please.

@phenomlab yes it’s a different theme. The other one was not offering much on editable sidebar. It was like flarum hahah

@Sala the only way you can achieve this is to use a robots.txt file and disallow access to those links.

@Sala Just checked your site. This should work .bs-blog-post .title, .bs-blog-post .title a { color: #ffffff; } It’s worth noting the existing CSS, which uses variables like the below color: var(--head-color); These come under the :root section as below :root { --head-color: #212121; --stext-color: #000; --text-color: #718096; --wtext-color: #fff; --bg-color: #fff; --box-color: #fff; --border-color: #e2e8f0; --wrap-color: #eff2f7; } You can easily override these by using the CSS I provided at the top of this post, or you can change the underlying colours defined in the variables. However, taking this route may mean other objects are styled in the same way, which may not be the desired result.

Yes, I am aware that if users are given the option to enter alt text, some may do so in an abusive manner. For the time being, we’ve adjusted the php script to generate the alt automatically, thus there are no longer any SEO problem with alt images.

I found it here, ins elements can not have aria elements

@phenomlab It looks good, but not anymore. I’ve already lost so much time. Now it’s time to move on

@Sala I’ve spent some time this morning reviewing your WordPress configuration. The issue of the duplicated h1 tag 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) here https://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 [image: 1674648697142-81a553b7-acac-43ab-baeb-13d956c41d5f-image.png] 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 h1 heading appears twice (which you’re already aware of) [image: 1674648806743-8065709b-6664-4a50-9cd4-2ca1e9dbe756-image.png] 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 https://anspress.net/questions/question/very-serious-issue-with-upgrade-to-v4-1-9-multiple-emails-being-sent-out-to-everyone/ [image: 1674650179187-262370bb-7d2b-499e-9d89-fac759b1e42d-image.png] At this point, I would weigh up the investment in AnsPress and seriously consider removing it.

@Hari Glad to see this went so well, and that you’ve finally departed the Flarum ecosystem

@Sala I will likely need admin access to your site for this.

@phenomlab yes that’s the problem with these J’s, I will try my best , If I find something better I will share. Thanks

@phenomlab thank you for information.

@hari the cache level for woocommerce should always be bypass. Any caching of woocommerce will cause you serious issues and will result in the checkout process not functioning correctly. This does mean that the overall experience will be slower (depending on geographic location) although CF is known to cause significant issues hence the need to bypass. If you want to cache as much as possible, then set rules to bypass caching on the cart and account pages etc.

@phenomlab said in WordPress installation: @jac that plugin is for single sign on between WordPress and NodeBB. The plugin you really need is this Brilliant, that does look good!

@phenomlab a seperate site mate.

@jac That won’t matter. You just redirect at nginx or apache level and it’ll work. The generally accepted standard though is to use a subdomain.