HIKASHOP ESSENTIAL 60€The basic version. With the main features for a little shop.
HIKAMARKETAdd-on Create a multivendor platform. Enable many vendors on your website.
HIKASERIALAdd-on Sale e-tickets, vouchers, gift certificates, serial numbers and more!
MARKETPLACEPlugins, modules and other kinds of integrations for HikaShop
-- url of the page with the problem -- : Back-end display
-- HikaShop version -- :2.3.1
-- Joomla version -- :2.5.17
-- PHP version -- : 5.3.28
-- Browser(s) name and version -- : Firefox 30.0
-- Error-message(debug-mod must be tuned on) -- : N/A
After the recent upgrade to HikaShop 2.3.1, I have encountered several problems both front and back-end. These manifest in both display and functionality, which is a problem on a live site - we don't appreciate visible errors and functional difficulties which have to be rectified in public view.
1. The upgrade installation caused the creation/reselection of associated modules, which means that each standard menu listing has a second module which displays immediately after the selected module. I have had this problem before and have resolved it by clearing links from the Menu item to any 'Associated module'. But upgrades seem to reconnect associated module links - how can I prevent this happening?
2. Products now ALL appear listed on the back-end Products/'Product category' page - previously the only items to appear on that page were new entries which had not yet been linked to a category listing. Once added to a category, items disappeared from the 'Product category' page and then only displayed under the selected category listing/s.
Because products now appear in both listings, uncategorised products are now 'lost' on the Products/'Product category' page if they are not placed in a category immediately on input. Furthermore, the 'Category' listing pages no longer include the custom fields previously installed, one of which is important for product identification/editing. The custom fields do, however, still appear on the 'Product category' page, except for the item 'Order/Save' column. How do I get the products/custom fields to display as before?
3. We have a search module which acts on those same 'missing' custom fields, and products added since the upgrade are not found by the search process. There is clearly an issue with the custom fields, any ideas about what might have caused these errors?
4. What is the value of selecting a field under the 'Core' table heading? This info is absent from your on-line Help.
5. Whilst there is undoubted value in the provision of the Changelog for each new release, would it not be possible to provide the updated 'View' files separately, so that existing customisations can be added to the new View file code BEFORE the update is installed. That would avoid losing those custom features on live sites while the new 'View' files have customisations edited back in. The alternative is that customised View files get more and more outdated as releases progress.
6. Where can the 'Back-end Category Listing' column widths be adjusted?
Thanks for your help.
Please Log in or Create an account to join the conversation.
Hi,
1. The creation and reselection of the associated modules ?
I am sorry but I will need details to understand what you are talking about.
2. There is no change in the view.
Please check that the filters dropdown have correct values ( Brand / all / Products / Direct sub elements )
If you are displaying "all sub elements", some elements can't be loaded correctly, like the custom fields which are link to specific categories.
3. Fixing point 2 should help you for this point.
4. The "core" custom fields are custom fields created by HikaShop itself. It is custom fields that you can't remove.
We display the information so you can know that the field is an HikaShop "default / core" field.
5. Since HikaShop 2.3.1, we display the list of modified files.
You can see the link in the changelog.
So you can see the content of this views in the HikaShop package directly, and modified your views like you want.
But for website with a lot of customization, it is always recommend to perform an update in a pre-prod website. To check it before the production.
6. You can adjust them using CSS. There is nothing in the code to specify a width, so you're free to set it.
Regards,
Please Log in or Create an account to join the conversation.
I have made further checks to the site and have found nothing which would give rise to the problems as related to your comments.
I DO have a test site set up to try to avoid problems on upgrade (though I have consistent back-end messages to add this to my HikaShop account page - and presumably pay an additional license fee), but I did not expect to have any errors, because my edits are all made either in the CSS or view files. But having an 'original' version has enabled me to make some comparative screen shots.But for website with a lot of customization, it is always recommend to perform an update in a pre-prod website. To check it before the production.
There IS a change in the content displayed - compare h5bfa01d.jpg below, which is taken from my test (original) site and shows no products listed under the top level 'Product categories' (products were listed only under their related categories) with h765dac6.jpg, which shows ALL products listed under the top level after the v2.3.1 update, including the headers for selected custom fields. However, h2b5c3ac.jpg shows that the updated category product lists display none of the selected custom field headers set up in the original version (see h6623324.jpg below) and shown under the main Product category listing after upgrade.There is no change in the view.
I am sure the search module is working properly, but I cannot see why the custom fields (eg. h1145ab3.jpg) are not appearing or functioning as expected.Fixing point 2 should help you for this point.
Please Log in or Create an account to join the conversation.
Hi,
1. If you don't have a products listing associated module attached to a category listing, it basically means that you'll have a list of category and when you click on a category, it will display the sub categories if any, but it will never display any product. There is no point in having a category listing menu without such associated module. That's why this message appears, and it has been so since 2 years ago, so it was there even before the 2.0.0.
2. As Jerome said, there is no change in the view.
The only thing that changed is that we changed the default value of the sub element filter dropdown on the top right corner of the listing so that it is set to "all sub elements" instead of "direct sub elements" by default in order to make it easy for beginners which not always understand why they don't see their products when arriving on the products listing page because the products are ine sub categories. But you can just change the dropdown if you want to have it the other way around.
Custom product field columns restricted to categories won't display on the products listing in "all sub elements" mode because products from several categories are displayed at the same time.
3. No one reported such issue with the search system or the filter system. Please provide more information. Which search doesn't work on which page ? Can you do a screenshot of the configuration of the custom field ? Can you do a screenshot of the options of the filter or the search plugin ?
5. The files are included. When you do an override, your modified file is copied to the template. When you update HikaShop, the original file is updated. So you have both files on your website.
If you want to compare them, that's totally possible directly on your website.
For example, the file components/com_hikashop/views/product/tmlp/listing.php (which is from the latest version of HikaShop installed), has its override stored in templates/YOUR_TEMPLATE/html/com_hikashop/product/listing.php (the one you see when you edit the view).
We try as much as possible to be backward compatible so that overridden view files still work with new versions of HikaShop. But HikaShop has a lot of options, and users customize the files in a lot of different ways so it's totally possible that it can break the override. That's why we recommend to first test the update on a pre-prod website, especially if you've customized HikaShop a lot.
And if you find issues, then yes, you will have to merge the modifications of the new version with the modifications you made.
6. From what you're saying, it doesn't look like your customizations have anything to do with that. An easy way to test that is to rename the folder templates/YOUR_TEMPLATE/html/com_hikashop temporarily so that all the overrides get deactivated and see if it helps. If it doesn't change anything, then the problem is not with your overrides.
Please Log in or Create an account to join the conversation.
Thanks nicolas, you have given me the actual source of all the problems I detailed above.
When I changed the 'new' default back to "direct sub elements", all the above problems were resolved. I also changed the same option under the 'Configuration' tab Modules main default options. However, when I made any changes and saved them, or logged out and back in again, the drop-down option on the Products/Product category page had reverted to the default "all sub elements" and the errors and problems with custom fields had returned.2. As Jerome said, there is no change in the view.
The only thing that changed is that we changed the default value of the sub element filter dropdown on the top right corner of the listing so that it is set to "all sub elements" instead of "direct sub elements" by default . . .
Yes, but how can I make the "direct sub elements" option permanent? The situation where the working (non-default) preference has to be reselected after every 'save' and/or login is not satisfactory and surely could not have been the intention?But you can just change the dropdown if you want to have it the other way around.
Please Log in or Create an account to join the conversation.
Or alternatively show me how to adapt 'my' site to the new default option. The site has NO sub-categories anyway, so surely this option should not affect the set up so drastically.
Thank you.
Please Log in or Create an account to join the conversation.
Hi,
No, that is the exact intention. To have it set to all sub elements by default. In most cases, that's the preferred default value for most cases.
We didn't add any option to change the default behavior as we already have too much options in the configuration. However, we added a hidden one to change that. You'll have to add an entry with the namekey "sub_products_display_all" and the value 0 in the table hikashop_config of your database via your phpmyadmin and that will set the default value of that dropdown to "direct sub elements".
Please Log in or Create an account to join the conversation.
Thankyou nicolas, that worked perfectly! Now for the 2.3.2 upgrade . . .
PS. . . . which completed without a problem! Thanks again, nicolas for the above information. I'm still a little concerned that my site works by means contrary to the majority of others, but, hey, maybe I'll just count my blessings!!
Please Log in or Create an account to join the conversation.
