New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow store owners to specify featured products #976
Comments
It looks like the featured product should not come from those marked not to appear on the homepage, but I've twice seen such products up in the featured product box, but this solution of having a more select pool to draw from seems good. |
Products marked as 'featured' can appear in the featured product box whether or not they are marked to appear on the homepage. In other words, the featured products are completely independent from those that appear on the homepage, and this is intentional. If you only want products that are marked as both featured and homepage to appear, you can change the following line:
|
Implemented with 9b5ce31. Lets see how we get on with this. Thanks Brian! :) |
Seem to work well from my testing. Awesome. :) |
Glad to help! :) |
Issue #976 - new products 'featured' by default
With this code in place - are ALL items supposed to be marked by default as Featured in database? Mine are. |
Also, the current Latest Products are NOT marked as such in the admin Product listing page. |
Yes because thats how it worked before. All products were featured in the random product. Now on add you can choose to uncheck and not feature.
I'll check this. Did you make the database changes or just update the files? |
From my testing it works fine. Make sure you run these SQL changes:
|
OK - I had already run some of the SQL changes for 6.1.0, so just added the "new" ones on the bottom of the list - but now I see the new Featured ones are at the top of the list now. After running the latest-featured one, it does have the Latest marked now as it should. But as far as having ALL marked as Featured automatically, I'm not sure I agree with your logic. Yes, that's the way it was before - but that's the very thing that was wrong with it the old way. We have close to 5k listings. If I didn't know how to change the 1 to 0 via cPanel I'd be tearing my hair out to get just the ones I wanted to be Featured. I actually quit using the Featured stock code a long time ago because it didn't allow me to feature what I wanted to feature. I made my own side box. |
@Dirty-Butter My initial implementation had 'featured' set to 0 by default for the very reasons you state, but Al requested that we not change the default behavior. To achieve your desired results, revert the changes made in commit 828e277, either manually or via git command |
Yup. Historically CubeCart has always taken the featured products as a random one that is enabled. It's great to have this feature but it should still work the old way until the merchant chooses otherwise. |
I see your reasoning that you want to leave it as it was - otherwise a store owner would have an empty Featured box and not necessarily understand why. |
You can run a database query;
|
Perhaps this is something we can include in the release notes along with an explanation of how featured vs latest works? And yeah, I totally agree with your decision to maintain consistency - I was just being selfish with my first implementation ;) |
Since I don't actually use the Featured box, it's not a problem for me - but I think providing an explanation of how Featured works in 6.1.0 would be very helpful, with the database query suggested for those who want to zero all out to begin with. |
This is a feature requested by a client that I think makes a lot of sense. Currently the 'featured product' box just displays a random product out of the entire inventory, but I imagine most store owners would actually want to choose which products are featured, as that box is prime screen real estate.
I've uploaded a branch of my implementation that I'd be happy to create a PR for if acceptable, as well as another branch with a tweak to make the selection code much more efficient.
The text was updated successfully, but these errors were encountered: