So, you go through all the time and effort to make your RM look nice and neat and use the built in Prefix function to make it easier for your users to find specific item categories.
You use them to do something like differentiate different software versions of the same (in this case) catalog, since some will have the same name since they are of the same object
You don't have the ability in XFRM to create sub-resources in the entry itself based upon software needed (like a Linux version, Windows version, etc) because the XFRM itself is limited in that ability. And putting the software it is for in the file name defeats the very purpose of the prefixes.
So, you also want to create a discussion thread (using the built in function designed for that) for those resources that are distinctly listed on the XFRM page using yet another default function that was designed for that.
But what do you get?
You get a discussion node with duplicate discussion threads and no prefixes shown.
Apparently XenForo is unable to use existing prefixes that you took the time to create and then replicate them into the thread that XenForo script creates in a forum node.
To a simple person like me, it would seem this would be a basic process that would (and should) have been obvious. But if you want those to have prefixes... you better get ready to manually recreate all the prefixes again in the forum node ACP area and then go through and manually apply them anytime a new resource is added.
The alternative (so it doesn't look like
) is to hide that category/node from the node list and then only have it accessible via the discussion button on the resource listing itself. This is currently what I did as the alternative of having them all viewable could quickly confuse a user.
But that kind of defeats the purpose of discoverability. Folks that might not take the time to look in the resources add-on may instead find it in the discussion thread.
This is one of the many "simple" things I've bagged on XenForo about. And honestly... they probably do not care as they will call it an "edge case use". The "edge case use" is probably more the few folks that actually use XFRM on their sites.
I think it is an actual limitation in the way they coded their script, because this weakness carries across to several other add-ons.
EDIT:
And it's a long existing limitation from back in the very early days (over a decade ago) of XenForo. Surprised by now it hasn't dawned on any core developer type to streamline the ability to share prefixes between content types.
Maybe that will come about in the 2525 (Zaeger & Evans reference for those not into older music) release versions. Should be about Xenforo 6 or so?
You use them to do something like differentiate different software versions of the same (in this case) catalog, since some will have the same name since they are of the same object
You don't have the ability in XFRM to create sub-resources in the entry itself based upon software needed (like a Linux version, Windows version, etc) because the XFRM itself is limited in that ability. And putting the software it is for in the file name defeats the very purpose of the prefixes.
So, you also want to create a discussion thread (using the built in function designed for that) for those resources that are distinctly listed on the XFRM page using yet another default function that was designed for that.
But what do you get?
You get a discussion node with duplicate discussion threads and no prefixes shown.
Apparently XenForo is unable to use existing prefixes that you took the time to create and then replicate them into the thread that XenForo script creates in a forum node.
To a simple person like me, it would seem this would be a basic process that would (and should) have been obvious. But if you want those to have prefixes... you better get ready to manually recreate all the prefixes again in the forum node ACP area and then go through and manually apply them anytime a new resource is added.
The alternative (so it doesn't look like
) is to hide that category/node from the node list and then only have it accessible via the discussion button on the resource listing itself. This is currently what I did as the alternative of having them all viewable could quickly confuse a user.But that kind of defeats the purpose of discoverability. Folks that might not take the time to look in the resources add-on may instead find it in the discussion thread.
This is one of the many "simple" things I've bagged on XenForo about. And honestly... they probably do not care as they will call it an "edge case use". The "edge case use" is probably more the few folks that actually use XFRM on their sites.
I think it is an actual limitation in the way they coded their script, because this weakness carries across to several other add-ons.
EDIT:
And it's a long existing limitation from back in the very early days (over a decade ago) of XenForo. Surprised by now it hasn't dawned on any core developer type to streamline the ability to share prefixes between content types.
Maybe that will come about in the 2525 (Zaeger & Evans reference for those not into older music) release versions. Should be about Xenforo 6 or so?
Last edited:
