Recent content by bzcomputers

1. The plan was to leave the mobile menu as is. There isn't the same issue with limited space that the widescreen menu definitely has with numerous main menu and submenu options. 2. I currently only use horizontal separators for menu tiers that have to be collapsed into another tier because of...

This single change to use the template system for css and js has reduced the on-page code by 80+% (nearly 300 lines of code are now being cached). Performance should be a lot better now. I do see that there are still a lot on inline styles being used and one on-page <script> being referenced...

I think the CSS/LESS application and coding could use some rework. Using a CSS <style> block has some downfalls. It is currently non-cacheable separately from the page itself, which means it is unnecessarily increasing every page size and in turn causing slight performance impacts on every page...

This issues likely existed before with your installation of XenForo 2.2. XenForo made some upgrades to its installation checks for 2.3 to make them more robust to better identify missing php functions and options that could have gone unfound and unreported during previous installations. I'm...

You should just be able to adjust width to max-width. [data-template="thread_view_type_article"] { .message--article { max-width: 600px; margin: 0 auto; } }

I'd like to switch to using this add-on from another. The only thing missing that I require is the ability to show sub-nodes in columns. Is this something you would be interested in adding? For instance I set... Column Count: 3 And additional css is applied. Similar to... .node .node-columns...

@Siropu - Assuming you are not maintaining a huge device database somewhere for applying "Device Criteria", what are the actual hardcoded cut-offs for screen sizes for Desktop, Tablet and Mobile Phone?

I use that exact format all the time in custom PHP code for XF 2.3 without issue. Do you have a sample PHP code block or a testing page I could see the issue in action?

Gotcha. The simplest solution would be to eliminate the conditional altogether and just use... <i class="fal fa-globe" data-xf-init="icon"></i> This should work fine in both 2.2 and 2.3+.

have you tried... <xf:if is="$xf.versionId < 2030000">

Then technically the only difference is they would fill in the title after they fill in the thread message. Not seeing an issue. Edit: I also assume this would be an "option" that can be easily turned off (possibly by node or universally) for those that find no use for it. Which is how most AI...

For sysadmin on a 27" screen you will not be able to distinguish the difference in PPI for a 4K vs 5K screen. At a viewing distance of about 24" (you likely will not be any closer), both displays will have a higher resolution than the human eye can perceive. The benefits of the more expensive 5K...

I think the idea of using AI to write thread titles can be extremely useful for SEO and onsite searches. I also think if implemented correctly it will be very well received by most users. I think by default the thread title box should be locked. The user should just input their thread message...

Whether you can, and whether you should are two different things. I would look at this as a time to upgrade PHP if at all possible. Hardened versions of older software have a time and place, but remember these hardened versions have only gotten security updates for many years. PHP 8.0+ has been...

Google search console will not give you any of this data. Is there a reason you don't use Google Analytics? It sure makes it a lot easier to know what your site is actually doing - content performance, conversion rates, user behavior - just shooting blind without it or another equivalent analytics.