[Skip to main content](#vessel-content) # Profile for Lumiga ## [![Lumiga's Avatar](https://www.hikashop.com/media/kunena/avatars/resized/size144/users/avatar31479.png)](/forum/user/31479-lumiga "View Lumiga's Profile") **[ Offline](/forum/user/31479-lumiga)** - **User Type:** User - **Register Date:** 03 Mar 2014 - **Last login:** 1 week 10 hours ago - **Time Zone:** UTC +1:00 - **Local Time:** 21:41 - **Posts:** 637 - **Profile views:** 510 - **Thank you received:** 26 - **Location:** [Rotterdam](https://maps.google.com?q=Rotterdam) - **Gender:** Male - **Medals:** Hikaserial Subscription Hikashop Multisite > Kind regards, > Lumiga - Posts # Lumiga's recent posts (637 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/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372938) | [I am encountering an error when trying to install HikaShop](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372938 "-- HikaShop version -- : 6.5.0 -- Joomla version -- : 6.1.1 -- PHP version -- : 8.3 Hello HikaShop support, I am encountering an error when trying to install HikaShop for the first time on a Joomla website. This is a fresh installation with no previous HikaShop data present. Error messages shown after installation attempt: 1. Warning: Table 'ID470049_DemoAllUnited.r1e6l_hikashop_config' doesn't exist 2. Error: Error installing component Could you please advise what might be causing this and what the recommended steps are to resolve it? Thank you in advance. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 4 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") 3 months 3 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:11 Views:460 | [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 3 days ago | | [](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372912) | [Update from 6.5.0 to 6.5.2 language file nog working any more](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372912 "-- HikaShop version -- : 6.5.2 -- Joomla version -- : 6.1.2 -- PHP version -- : 8.3 Hi Support, After updating HikaShop from 6.5.0 to 6.5.2, the translations are no longer loading anywhere in the back-end. Instead of the normal texts we now see the raw language keys everywhere (for example SHOW_FOOTER, IMAGE_POPUP_MODE, USE_CHOSEN, and even the update notice itself shows as UPDATE_LANGUAGE / LOAD_LATEST_LANGUAGE). A screenshot is attached. The important point: the Dutch language file is definitely present and installed. We have verified this: - In HikaShop > System > Configuration > Languages, Dutch (nl-NL) is listed as installed. When we open it with the Edit icon, the full list of translated strings is shown, so the file exists and is filled. - Via FTP the file nl-NL.com_hikashop.ini is present and not empty, in both /language/nl-NL/ and /administrator/language/nl-NL/. - The files and folders have the correct read permissions. What we have already tried, without any result: - Reinstalled the HikaShop 6.5.2 package over the existing installation. - Clicked "Load latest from server" for the Dutch language and saved. - Cleared the Joomla cache. So the nl-NL file is present, but HikaShop keeps showing the untranslated keys after the update. Could you tell us what can cause the language file not to be loaded, and how to solve it? Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 3 months 6 days ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372915 "Hi, The update only update the en language file, and it does it automatically on the server side, so a modSecurity should have no influence over it. Other languages are not included and need to be updated manually via the "Load latest version from our server" button of the language file edit screen. This manually process goes through the browser, and thus ModSecurity can block it. But blocking it shouldn't result in the file already there being deleted. So, in short, I'm still not clear on how this could have happened.") 3 months 5 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:3 Views:328 | [Last Post](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372915 "Hi, The update only update the en language file, and it does it automatically on the server side, so a modSecurity should have no influence over it. Other languages are not included and need to be updated manually via the "Load latest version from our server" button of the language file edit screen. This manually process goes through the browser, and thus ModSecurity can block it. But blocking it shouldn't result in the file already there being deleted. So, in short, I'm still not clear on how this could have happened.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 5 days ago | | [](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372902) | [Update from 6.5.0 to 6.5.2 language file nog working any more](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372902 "-- HikaShop version -- : 6.5.2 -- Joomla version -- : 6.1.2 -- PHP version -- : 8.3 Hi Support, After updating HikaShop from 6.5.0 to 6.5.2, the translations are no longer loading anywhere in the back-end. Instead of the normal texts we now see the raw language keys everywhere (for example SHOW_FOOTER, IMAGE_POPUP_MODE, USE_CHOSEN, and even the update notice itself shows as UPDATE_LANGUAGE / LOAD_LATEST_LANGUAGE). A screenshot is attached. The important point: the Dutch language file is definitely present and installed. We have verified this: - In HikaShop > System > Configuration > Languages, Dutch (nl-NL) is listed as installed. When we open it with the Edit icon, the full list of translated strings is shown, so the file exists and is filled. - Via FTP the file nl-NL.com_hikashop.ini is present and not empty, in both /language/nl-NL/ and /administrator/language/nl-NL/. - The files and folders have the correct read permissions. What we have already tried, without any result: - Reinstalled the HikaShop 6.5.2 package over the existing installation. - Clicked "Load latest from server" for the Dutch language and saved. - Cleared the Joomla cache. So the nl-NL file is present, but HikaShop keeps showing the untranslated keys after the update. Could you tell us what can cause the language file not to be loaded, and how to solve it? Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 3 months 6 days ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372915 "Hi, The update only update the en language file, and it does it automatically on the server side, so a modSecurity should have no influence over it. Other languages are not included and need to be updated manually via the "Load latest version from our server" button of the language file edit screen. This manually process goes through the browser, and thus ModSecurity can block it. But blocking it shouldn't result in the file already there being deleted. So, in short, I'm still not clear on how this could have happened.") 3 months 5 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:3 Views:328 | [Last Post](/forum/25-install-update/910729-update-from-6-5-0-to-6-5-2-language-file-nog-working-any-more#372915 "Hi, The update only update the en language file, and it does it automatically on the server side, so a modSecurity should have no influence over it. Other languages are not included and need to be updated manually via the "Load latest version from our server" button of the language file edit screen. This manually process goes through the browser, and thus ModSecurity can block it. But blocking it shouldn't result in the file already there being deleted. So, in short, I'm still not clear on how this could have happened.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 5 days ago | | [](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372865) | [Missing List of all the files changed between the 6.5.0 and the previous version](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372865 "-- HikaShop version -- : 6.5.2 Hi HikaShop team, We are missing the list of all files changed between version 6.5.1 and 6.5.2 and the previous version. It's now hard to find out which files have changed. We hope you can deliver this quickly. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 3 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372865 "Okay, understandable if it's a different build every day. I need to get used to doing this a different way, but it's a good idea to do this with AI. I'm going to build an application that does this...") 3 months 1 week ago by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") | Replies:3 Views:257 | [Last Post](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372865 "Okay, understandable if it's a different build every day. I need to get used to doing this a different way, but it's a good idea to do this with AI. I'm going to build an application that does this...") by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") 3 months 1 week ago | | [](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372824) | [Missing List of all the files changed between the 6.5.0 and the previous version](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372824 "-- HikaShop version -- : 6.5.2 Hi HikaShop team, We are missing the list of all files changed between version 6.5.1 and 6.5.2 and the previous version. It's now hard to find out which files have changed. We hope you can deliver this quickly. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 3 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372865 "Okay, understandable if it's a different build every day. I need to get used to doing this a different way, but it's a good idea to do this with AI. I'm going to build an application that does this...") 3 months 1 week ago by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") | Replies:3 Views:257 | [Last Post](/forum/25-install-update/910716-missing-list-of-all-the-files-changed-between-the-6-5-0-and-the-previous-version#372865 "Okay, understandable if it's a different build every day. I need to get used to doing this a different way, but it's a good idea to do this with AI. I'm going to build an application that does this...") by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") 3 months 1 week ago | | [](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372527) | [I am encountering an error when trying to install HikaShop](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372527 "-- HikaShop version -- : 6.5.0 -- Joomla version -- : 6.1.1 -- PHP version -- : 8.3 Hello HikaShop support, I am encountering an error when trying to install HikaShop for the first time on a Joomla website. This is a fresh installation with no previous HikaShop data present. Error messages shown after installation attempt: 1. Warning: Table 'ID470049_DemoAllUnited.r1e6l_hikashop_config' doesn't exist 2. Error: Error installing component Could you please advise what might be causing this and what the recommended steps are to resolve it? Thank you in advance. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 4 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") 3 months 3 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:11 Views:460 | [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 3 days ago | | [](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372428) | [I am encountering an error when trying to install HikaShop](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372428 "-- HikaShop version -- : 6.5.0 -- Joomla version -- : 6.1.1 -- PHP version -- : 8.3 Hello HikaShop support, I am encountering an error when trying to install HikaShop for the first time on a Joomla website. This is a fresh installation with no previous HikaShop data present. Error messages shown after installation attempt: 1. Warning: Table 'ID470049_DemoAllUnited.r1e6l_hikashop_config' doesn't exist 2. Error: Error installing component Could you please advise what might be causing this and what the recommended steps are to resolve it? Thank you in advance. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 4 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") 3 months 3 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:11 Views:460 | [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 3 days ago | | [](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372412) | [I am encountering an error when trying to install HikaShop](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372412 "-- HikaShop version -- : 6.5.0 -- Joomla version -- : 6.1.1 -- PHP version -- : 8.3 Hello HikaShop support, I am encountering an error when trying to install HikaShop for the first time on a Joomla website. This is a fresh installation with no previous HikaShop data present. Error messages shown after installation attempt: 1. Warning: Table 'ID470049_DemoAllUnited.r1e6l_hikashop_config' doesn't exist 2. Error: Error installing component Could you please advise what might be causing this and what the recommended steps are to resolve it? Thank you in advance. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 4 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") 3 months 3 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:11 Views:460 | [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 3 days ago | | [](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372397) | [I am encountering an error when trying to install HikaShop](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372397 "-- HikaShop version -- : 6.5.0 -- Joomla version -- : 6.1.1 -- PHP version -- : 8.3 Hello HikaShop support, I am encountering an error when trying to install HikaShop for the first time on a Joomla website. This is a fresh installation with no previous HikaShop data present. Error messages shown after installation attempt: 1. Warning: Table 'ID470049_DemoAllUnited.r1e6l_hikashop_config' doesn't exist 2. Error: Error installing component Could you please advise what might be causing this and what the recommended steps are to resolve it? Thank you in advance. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 4 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") 3 months 3 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:11 Views:460 | [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 3 days ago | | [](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372325) | [I am encountering an error when trying to install HikaShop](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372325 "-- HikaShop version -- : 6.5.0 -- Joomla version -- : 6.1.1 -- PHP version -- : 8.3 Hello HikaShop support, I am encountering an error when trying to install HikaShop for the first time on a Joomla website. This is a fresh installation with no previous HikaShop data present. Error messages shown after installation attempt: 1. Warning: Table 'ID470049_DemoAllUnited.r1e6l_hikashop_config' doesn't exist 2. Error: Error installing component Could you please advise what might be causing this and what the recommended steps are to resolve it? Thank you in advance. Kind regards, Lumiga") Category: [Install & Update](/forum/25-install-update "Having an installation or update issue? You will probably find some help here.") Topic started 4 months 1 week ago, by [Lumiga](/forum/user/31479-lumiga "View Lumiga's Profile") [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") 3 months 3 days ago by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") | Replies:11 Views:460 | [Last Post](/forum/25-install-update/910616-i-am-encountering-an-error-when-trying-to-install-hikashop#372940 "Hello, Your test isolates it perfectly, and we have reproduced it here. It is a bug on our side, and it has nothing to do with the database, the host or ModSecurity. Thank you for the very detailed tests, they are what allowed us to find it. The trigger is a leftover com_hikashop folder on the site. Joomla decides between a fresh install and an update by looking at the folders, not at the database: in ComponentAdapter::checkExtensionInFilesystem(), if components/com_hikashop, administrator/components/com_hikashop or api/components/com_hikashop already exists, and the extension provides an update() method in its install script, which HikaShop does, Joomla routes the installation as an update. And for the "update" route, InstallerAdapter::parseQueries() does not run the SQL file declared in the manifest, which is the file that creates the tables of HikaShop. So no table is created, HikaShop then queries its configuration table, the query fails, and Joomla aborts with the two messages you get. That is why a really fresh Joomla works and a restored one does not: the restore brings back the folders of HikaShop while the tables are gone, and deleting the rows of the extensions table does not remove those folders. So to answer your questions: - What decides fresh install versus update: the presence of the component folder on disk, decided by Joomla before our install script even runs, not anything of ours in the database. - What the Akeeba restore changes: nothing it does wrong. It simply puts the files back, and the empty database then no longer matches them. - A debug switch: not needed here, the fix removes the problem. We fixed it: HikaShop now creates its missing tables itself in that situation, instead of stopping. We reproduced your exact case on a Joomla 6.1 site with the com_hikashop folders present and no HikaShop table, and the installation now goes through. So you can download the install package on our website and install it on yours and then the problem should not happen. Alternatively, delete the com_hikashop folders before installing: components/com_hikashop, administrator/components/com_hikashop, api/components/com_hikashop, and media/com_hikashop, then install the package again. That works with the version you already have.") by [nicolas](/forum/user/63-nicolas "View nicolas's Profile") 3 months 3 days ago | [](/forum/topics/feed/mode-topics?format=feed&type=rss) Time to create page: 0.087 seconds [Powered by](/forum/credits) [Kunena Forum](https://www.kunena.org)