While developing Breadcrumb NavXT 5.4, I spent some time investigating the compatibility issues between Breadcrumb NavXT and BuddyPress. Within Breadcrumb NavXT, every attempt is made to use the WordPress API, when possible, to maximize the compatibility with other plugins such as BuddyPress. However, this is not always enough, and the findings of this investigation are presented in this article.
What You Need
These are the plugins and versions used when performing the testing reported on within this article:
BuddyPress – At the time this article was written, 2.5.0 was the latest available version and was the version tested against.
Breadcrumb NavXT – Tested against a development release of 5.4.0.
Out of the box, group and user/member archives work in Breadcrumb NavXT 5.4.0.Unfortunately, the design of BuddyPress does not incorporate much of the standard WordPress content organization facilities. Hence, out of the box support for BuddyPress in Breadcrumb NavXT leaves much to be desired.
What Doesn’t Work
While user/member and group pages are detected correctly, the breadcrumb for the user and group archives/directory is missing. Additionally, none of the sub-components of the user/member and group pages are represented in the breadcrumb trail.
Breadcrumb NavXT BuddyPress Extensions is a free, add on plugin for Breadcrumb NavXT that fixes many of the shortfalls in BuddyPress support. It will fill in the missing breadcrumb to the group and user/member archives/directories when on a group or user/member page. Additionally, it will fill in the correct breadcrumb trail when in a sub-component of a user/member or group page. It is a simple activate and you’re good to go plugin—no configuration required. For non-English language sites, note that you will need to use the included .POT file in the languages directory to create your own translation set to get ‘Members’ and ‘Groups’ to translate to your language.
A topic that frequently comes up in the support forums is how to have a breadcrumb representing a category link to a Page (instance of the Page post type) rather than a category archive. Since this is not natively supported by WordPress, Breadcrumb NavXT does not natively support it. However, there is a filter that can facilitate this behavior.
The presented solution is a simplistic example for a single category. However, it can be extended for multiple categories, or taxonomy terms. Finally, rather than being hard-coded, the IDs could come from a term_meta field.
After placing this code into your site specific plugin, you will need to update two portions of it. Replace MYCATID with the ID of the category you want to change the link on, and replace PAGEID with the page you wish for the breadcrumb to link to. That’s it. Simple, right?
When Dell released the XPS 15 9550, they also announced a Thunderbolt docking station to take advantage of the 9550’s Thunderbolt 3 port. Dell referred to it as the TB15. However, one does not simply purchase the TB15, it comes packaged with a power brick. The 450-AEVM is a TB15 packaged with a 240W power brick. A package with a 180W power brick also exists.
When the last generation of XPS 13 laptops came out with the infinity display, I eagerly awaited an update to the XPS 15 that offered the same minimal bezel design. The Dell XPS 15 9550 is said machine. I had been looking for a 14″ laptop back when looking to replace my Vostro 1400. While I settled for the XPS 15 9530 in the last go around, the new XPS 15 9550 is best described as a 14″ laptop with a 15″ screen.
After acquiring a Broadwell generation Core i3 NUC (the NUC5i3RYK to be exact) and installing Linux, KDE/X.Org would lockup and crash frequently. Checking dmesg, the following messages appeared:
[drm] stuck on render ring
[drm] GPU HANG:…
From the dmesg report, it is clear the crashes were caused by the GPU hanging. After further inspection of the dmesg logs, it appears this is due to a bug between Intel’s graphics and IOMMU drivers. The easiest way to work around this is to disable Intel IOMMU support.
Since I had compiled IOMMU support into my kernel, removing IOMMU support involved a kernel recompile. When configuring your kernel using menuconfig, make sure that “Support for Intel IOMMU using DMA Remapping Devices” under “Device Drivers > IOMMU Hardware Support” is unchecked. This is equivalent to ensuring that INTEL_MMU = n in your .config file. For the NUC, that was all that was required to keep the GPU driver from crashing and taking X.Org and KDE down with it.