As per title, I've implemented a Featured Content Handler for the content type cas_ad.
This means that process of featuring/unfeaturing CAS content is now 100% handled by the Core XF Featured Content Handler.
You can use the Core XF Featured Content Widget Definition to create featured content widgets for CAS content (or mixed content). Display is controlled by Core XF, not CAS.
You can also continue to use the CAS Featured Ads Widget Definition to create Features Ads widgets for CAS content and display that content in CAS layout types.
CAS Index. Featured Ads are still being displayed the same (based on CAS options).
CAS Category pages. Featured Ads are still being displayed the same (based on CAS options).
Note: You can disable the CAS options and instead, create widget(s) from the Featured Content Widget Definition and display those on CAS Index/Category pages (which is what XFRM does).
There is unfortunately some feature loss. The Auto Feature system has been sunsetted (at least for now). It is not compatible with the Core XF Featured Content handler (and frankly, that kind of functionality needs to be part of the abstract handler).
This means that process of featuring/unfeaturing CAS content is now 100% handled by the Core XF Featured Content Handler.
You can use the Core XF Featured Content Widget Definition to create featured content widgets for CAS content (or mixed content). Display is controlled by Core XF, not CAS.
You can also continue to use the CAS Featured Ads Widget Definition to create Features Ads widgets for CAS content and display that content in CAS layout types.
CAS Index. Featured Ads are still being displayed the same (based on CAS options).
CAS Category pages. Featured Ads are still being displayed the same (based on CAS options).
Note: You can disable the CAS options and instead, create widget(s) from the Featured Content Widget Definition and display those on CAS Index/Category pages (which is what XFRM does).
There is unfortunately some feature loss. The Auto Feature system has been sunsetted (at least for now). It is not compatible with the Core XF Featured Content handler (and frankly, that kind of functionality needs to be part of the abstract handler).
Upvote
0
