[Skip to main content](#vessel-content) # Profile for badcoder ## [![badcoder's Avatar](https://www.hikashop.com/media/kunena/core/svg/person.svg)](/forum/user/7931-badcoder "View badcoder's Profile") **[ Offline](/forum/user/7931-badcoder)** - **User Type:** User - **Register Date:** 22 Jun 2012 - **Last login:** 11 years 5 months ago - **Time Zone:** UTC +0:00 - **Local Time:** 13:30 - **Posts:** 40 - **Profile views:** 183 - **Thank you received:** 1 - **Gender:** Unknown - **Birthdate:** Unknown - Posts # badcoder's recent posts (40 messages ) All Since last visit 4 Hours 8 Hours 12 Hours 24 Hours 48 Hours Week Month Year All Since last visit 4 Hours 8 Hours 12 Hours 24 Hours 48 Hours Week Month Year | [ ](#forumbottom) | Subject | Replies / Views | Last Post | [ ](#forumtop) | |---|---|---|---|---| | [](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972) | [Problems following update to HikaShop](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "-- 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.") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 12 years 3 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") 12 years 3 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:7 Views:746 | [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 12 years 3 months ago | | [](/forum/25-install-update/869663-problems-following-update-to-hikashop#164837) | [Problems following update to HikaShop](/forum/25-install-update/869663-problems-following-update-to-hikashop#164837 "-- 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.") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 12 years 3 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") 12 years 3 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:7 Views:746 | [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 12 years 3 months ago | | [](/forum/25-install-update/869663-problems-following-update-to-hikashop#164779) | [Problems following update to HikaShop](/forum/25-install-update/869663-problems-following-update-to-hikashop#164779 "-- 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.") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 12 years 3 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") 12 years 3 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:7 Views:746 | [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 12 years 3 months ago | | [](/forum/25-install-update/869663-problems-following-update-to-hikashop#164685) | [Problems following update to HikaShop](/forum/25-install-update/869663-problems-following-update-to-hikashop#164685 "-- 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.") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 12 years 3 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") 12 years 3 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:7 Views:746 | [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 12 years 3 months ago | | [](/forum/25-install-update/869663-problems-following-update-to-hikashop#163815) | [Problems following update to HikaShop](/forum/25-install-update/869663-problems-following-update-to-hikashop#163815 "-- 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.") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 12 years 3 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") 12 years 3 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:7 Views:746 | [Last Post](/forum/25-install-update/869663-problems-following-update-to-hikashop#164972 "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!!") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 12 years 3 months ago | | [](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124041) | [Blank page, fatal errors after Hika 2.2.1 update.](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124041 "-- url of the page with the problem -- : soundsquitereasonable.com/ 'Search Our Stock' from 'Main Menu'. Site presently hidden by password protected splash page. Will PM access if required. -- HikaShop version -- : 2.2.1 -- Joomla version -- : 2.5.14 -- PHP version -- : 5.3.26 -- Browser(s) name and version -- : Firefox 23.0.1 -- Error-message(debug-mod must be tuned on) -- : Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . . . . . /administrator/components/com_hikashop/classes/field.php on line 2118 I recently updated a site to Hika 2.2.1, but the update has brought about fatal errors, causing the site to disappear behind blank pages when HikaShop is called. These problems happen every time I run the update when HikaShop has a new release. I have made edits to several views for layout purposes and to display custom fields (address_template, category_listing_image_title, checkout_cart, checkout_listing_price, product_cart, product_listing_image_title, product_listing_price, product_show, product_show_default), and two of these, 'product_listing_image_title' and 'product_listing_price', showed up when I activated Joomla debug. I copied my edited version of each and installed the update default file, but the error sites just changed to other view files, and files from elsewhere in the Hika structure. The latest error messages are detailed below - please advise where I can find the view files shown (I don't recognise the '/tmpl/' in the filepaths) and how the files listed elsewhere than the 'views' folder came to cause errors, since I haven't edited any of them. This was the first error message from the Categories Listing link - Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . . . . . /administrator/components/com_hikashop/classes/field.php on line 2118 Errors also showed up from each the Product Category listing links, so I replaced the view files listed above by the default views. Now I get the errors detailed below from (a) php 'display errors' and (b) when Joomla debug is also running: Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . . Category listing (Search Our Site) (a) . . . /public_html/templates/siteground-j16-40/html/com_hikashop/product/cart.php on line 327 (b) . . . /public_html/administrator/components/com_hikashop/classes/field.php on line 2118 (Product listing) 45Singles (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (Product listing) 45 EPs (a) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (Product listing) 12" Singles (a) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (Product listing) 33 Albums (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (Product listing) CD Albums (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_price.php on line 73 (Product listing) CD Singles (a) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (Product listing) 78 Records (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (Product listing) Memorabilia (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_price.php on line 73 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 Assuming I can get the site correctly functioning again, what can I do to prevent these problems happening at the next update? Thankyou. PS. FYI: Under 'How to know if it comes from that (for update issues)?' in the HikaShop FAQ, the option "Use AJAX when possible for add to cart buttons" is not under the 'Checkout' tab of the HikaShop 'Configuration', but in 'Advanced settings' under the 'Main' tab of the same section. :-)") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 13 years 1 month ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124041 "Thanks Jerome, sorted!! For the sake of any others who may encounter the same problem, the memory limit referred to above is not the web space allocated to your site, but the limit expressed in your site's php.ini file. PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with an error message similar to this: "Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . ." This is usually the result of the PHP script trying to load a large file, or files, into memory all at once, but it is possible to increase the memory limit to avoid this problem. To do this, open the php.ini file in your site's root folder and add, or edit, the following line: memory_limit=32M The default is 32M (32 megabytes), so you should replace the '32' with whatever value is appropriate (eg. '64'). If you are using PHP 5.0+, you may also need to check for user.ini files in the same directory which may be overriding your settings (eg. 'php5.ini'). If this does not resolve the problem, you can also increase the web server memory limit by editing, or creating if it does not exist, the ".htaccess" file in the same root folder, and adding the following line: RLimitMem max Both php.ini and .htaccess files should be created in plain text (eg. Notepad on Windows or TextEdit in Plain Text mode on Mac) to avoid any formatting information being saved. Editors such as WordPad, MS Word, and TextEdit in its default Rich Text mode will produce unreadable files. Cheers all.") 13 years 1 month ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:2 Views:1079 | [Last Post](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124041 "Thanks Jerome, sorted!! For the sake of any others who may encounter the same problem, the memory limit referred to above is not the web space allocated to your site, but the limit expressed in your site's php.ini file. PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with an error message similar to this: "Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . ." This is usually the result of the PHP script trying to load a large file, or files, into memory all at once, but it is possible to increase the memory limit to avoid this problem. To do this, open the php.ini file in your site's root folder and add, or edit, the following line: memory_limit=32M The default is 32M (32 megabytes), so you should replace the '32' with whatever value is appropriate (eg. '64'). If you are using PHP 5.0+, you may also need to check for user.ini files in the same directory which may be overriding your settings (eg. 'php5.ini'). If this does not resolve the problem, you can also increase the web server memory limit by editing, or creating if it does not exist, the ".htaccess" file in the same root folder, and adding the following line: RLimitMem max Both php.ini and .htaccess files should be created in plain text (eg. Notepad on Windows or TextEdit in Plain Text mode on Mac) to avoid any formatting information being saved. Editors such as WordPad, MS Word, and TextEdit in its default Rich Text mode will produce unreadable files. Cheers all.") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 13 years 1 month ago | | [](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124031) | [Blank page, fatal errors after Hika 2.2.1 update.](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124031 "-- url of the page with the problem -- : soundsquitereasonable.com/ 'Search Our Stock' from 'Main Menu'. Site presently hidden by password protected splash page. Will PM access if required. -- HikaShop version -- : 2.2.1 -- Joomla version -- : 2.5.14 -- PHP version -- : 5.3.26 -- Browser(s) name and version -- : Firefox 23.0.1 -- Error-message(debug-mod must be tuned on) -- : Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . . . . . /administrator/components/com_hikashop/classes/field.php on line 2118 I recently updated a site to Hika 2.2.1, but the update has brought about fatal errors, causing the site to disappear behind blank pages when HikaShop is called. These problems happen every time I run the update when HikaShop has a new release. I have made edits to several views for layout purposes and to display custom fields (address_template, category_listing_image_title, checkout_cart, checkout_listing_price, product_cart, product_listing_image_title, product_listing_price, product_show, product_show_default), and two of these, 'product_listing_image_title' and 'product_listing_price', showed up when I activated Joomla debug. I copied my edited version of each and installed the update default file, but the error sites just changed to other view files, and files from elsewhere in the Hika structure. The latest error messages are detailed below - please advise where I can find the view files shown (I don't recognise the '/tmpl/' in the filepaths) and how the files listed elsewhere than the 'views' folder came to cause errors, since I haven't edited any of them. This was the first error message from the Categories Listing link - Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . . . . . /administrator/components/com_hikashop/classes/field.php on line 2118 Errors also showed up from each the Product Category listing links, so I replaced the view files listed above by the default views. Now I get the errors detailed below from (a) php 'display errors' and (b) when Joomla debug is also running: Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . . Category listing (Search Our Site) (a) . . . /public_html/templates/siteground-j16-40/html/com_hikashop/product/cart.php on line 327 (b) . . . /public_html/administrator/components/com_hikashop/classes/field.php on line 2118 (Product listing) 45Singles (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (Product listing) 45 EPs (a) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (Product listing) 12" Singles (a) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (Product listing) 33 Albums (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (Product listing) CD Albums (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_price.php on line 73 (Product listing) CD Singles (a) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_div.php on line 79 (Product listing) 78 Records (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/quantity.php on line 66 (Product listing) Memorabilia (a) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_price.php on line 73 (b) . . . /public_html/components/com_hikashop/views/product/tmpl/listing_img_title.php on line 99 Assuming I can get the site correctly functioning again, what can I do to prevent these problems happening at the next update? Thankyou. PS. FYI: Under 'How to know if it comes from that (for update issues)?' in the HikaShop FAQ, the option "Use AJAX when possible for add to cart buttons" is not under the 'Checkout' tab of the HikaShop 'Configuration', but in 'Advanced settings' under the 'Main' tab of the same section. :-)") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 13 years 1 month ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124041 "Thanks Jerome, sorted!! For the sake of any others who may encounter the same problem, the memory limit referred to above is not the web space allocated to your site, but the limit expressed in your site's php.ini file. PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with an error message similar to this: "Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . ." This is usually the result of the PHP script trying to load a large file, or files, into memory all at once, but it is possible to increase the memory limit to avoid this problem. To do this, open the php.ini file in your site's root folder and add, or edit, the following line: memory_limit=32M The default is 32M (32 megabytes), so you should replace the '32' with whatever value is appropriate (eg. '64'). If you are using PHP 5.0+, you may also need to check for user.ini files in the same directory which may be overriding your settings (eg. 'php5.ini'). If this does not resolve the problem, you can also increase the web server memory limit by editing, or creating if it does not exist, the ".htaccess" file in the same root folder, and adding the following line: RLimitMem max Both php.ini and .htaccess files should be created in plain text (eg. Notepad on Windows or TextEdit in Plain Text mode on Mac) to avoid any formatting information being saved. Editors such as WordPad, MS Word, and TextEdit in its default Rich Text mode will produce unreadable files. Cheers all.") 13 years 1 month ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:2 Views:1079 | [Last Post](/forum/25-install-update/862112-blank-page-fatal-errors-after-hika-2-2-1-update#124041 "Thanks Jerome, sorted!! For the sake of any others who may encounter the same problem, the memory limit referred to above is not the web space allocated to your site, but the limit expressed in your site's php.ini file. PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with an error message similar to this: "Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 122880 bytes) in . . ." This is usually the result of the PHP script trying to load a large file, or files, into memory all at once, but it is possible to increase the memory limit to avoid this problem. To do this, open the php.ini file in your site's root folder and add, or edit, the following line: memory_limit=32M The default is 32M (32 megabytes), so you should replace the '32' with whatever value is appropriate (eg. '64'). If you are using PHP 5.0+, you may also need to check for user.ini files in the same directory which may be overriding your settings (eg. 'php5.ini'). If this does not resolve the problem, you can also increase the web server memory limit by editing, or creating if it does not exist, the ".htaccess" file in the same root folder, and adding the following line: RLimitMem max Both php.ini and .htaccess files should be created in plain text (eg. Notepad on Windows or TextEdit in Plain Text mode on Mac) to avoid any formatting information being saved. Editors such as WordPad, MS Word, and TextEdit in its default Rich Text mode will produce unreadable files. Cheers all.") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 13 years 1 month ago | | [](/forum/4-how-to/82591-import-invisible#108159) | [Import invisible?](/forum/4-how-to/82591-import-invisible#108159 "I recently completed a website which included HikaShop e-commerce . . . and then an 'administrative error' by my web host resulted in the deletion of my entire account! I have begun the rebuild (with...") Category: [How to?](/forum/4-how-to "If you didn't find the answer on our documentation neither on existing posts, please ask your question here.") Topic started 13 years 5 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/4-how-to/82591-import-invisible#108159 "Thank you, nicolas! :blush:") 13 years 4 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:8 Views:900 | [Last Post](/forum/4-how-to/82591-import-invisible#108159 "Thank you, nicolas! :blush:") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 13 years 4 months ago | | [](/forum/4-how-to/82591-import-invisible#107855) | [Import invisible?](/forum/4-how-to/82591-import-invisible#107855 "I recently completed a website which included HikaShop e-commerce . . . and then an 'administrative error' by my web host resulted in the deletion of my entire account! I have begun the rebuild (with...") Category: [How to?](/forum/4-how-to "If you didn't find the answer on our documentation neither on existing posts, please ask your question here.") Topic started 13 years 5 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/4-how-to/82591-import-invisible#108159 "Thank you, nicolas! :blush:") 13 years 4 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:8 Views:900 | [Last Post](/forum/4-how-to/82591-import-invisible#108159 "Thank you, nicolas! :blush:") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 13 years 4 months ago | | [](/forum/4-how-to/82591-import-invisible#105669) | [Import invisible?](/forum/4-how-to/82591-import-invisible#105669 "I recently completed a website which included HikaShop e-commerce . . . and then an 'administrative error' by my web host resulted in the deletion of my entire account! I have begun the rebuild (with...") Category: [How to?](/forum/4-how-to "If you didn't find the answer on our documentation neither on existing posts, please ask your question here.") Topic started 13 years 5 months ago, by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") [Last Post](/forum/4-how-to/82591-import-invisible#108159 "Thank you, nicolas! :blush:") 13 years 4 months ago by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") | Replies:8 Views:900 | [Last Post](/forum/4-how-to/82591-import-invisible#108159 "Thank you, nicolas! :blush:") by [badcoder](/forum/user/7931-badcoder "View badcoder's Profile") 13 years 4 months ago | [](/forum/topics/feed/mode-topics?format=feed&type=rss) Time to create page: 0.077 seconds [Powered by](/forum/credits) [Kunena Forum](https://www.kunena.org) [](#top)