Laravel aimeos - Integrity constraint violation issue - laravel

I`m new to Larvel Aimeos. I have used the following command to setup Aimeos.
composer create-project aimeos/aimeos myshop
But I`m stuck on the following issue while installing the same.
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-pr
oduct-custom-8' for key 'unq_msattr_sid_dom_cod_tid'
Any ideas on how to fix this?

There was a problem with the duplicate custom price attribute when installing the demo data. This has been fixed in a new Aimeos core release yesterday, so please try again

I think you are using this project https://github.com/aimeos/aimeos-laravel
So if you wanna to install the same project again you should create a new database to connect within your config/database.php file.
Or don't install the dummy data php artisan aimeos:setup --option=setup/default/demo:1 that the project required because it's already created.

Related

Command "october:migrate" is not defined

I must add table to existing octobercms project and added migration but it is not migrating. what may be problem? when I type php artisan october:migrate I faced with this problem
Command "october:migrate" is not defined.
Did you mean one of these?
october:down
october:env
october:fresh
october:install
october:mirror
october:passwd
october:up
october:update
october:util
php artisan october:up will only migrate the database
php artisan october:update will update the application files, plugins and migrate the database.
Check out this thread on the official forum
https://octobercms.com/forum/post/artisan-migrate
I had a similar issue: https://github.com/octobercms/october/issues/5589
It looks like the october:migrate would be available once you updated to the version 2.
It is a paid one.

Deleted migration files getting executed : Laravel application

I hace deleted some migration files. but when i execute php artisan migrate command, error in the old migration file is showing.
[Illuminate\Database\QueryException]
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint
(SQL : alter table cushbu_notifications add constraint
cushbu_notifications_art_id_foreign foreign key (art_id)
references cushbu_arts (id) on de lete cascade)
Now i don't have migration file for cushbu_notifications, instead i created a new migration file for cushbu_user_notifications.I deleted the cushbu_notifications table from database, also the corresponding entry from migrations table.
After manually deleting migration files, clear cache by below command, and then migrate
php artisan cache:clear
then
php artisan migrate
remove the entry from the migration table. and also remove references if that used in another migrations file.
Deleting migration files manually will not remove them from the Laravel cache. You can remove them by executing this.
php artisan optimize

Magento integrity constraint violation: 1062 on creating configurable product

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-81' for key 'UNQ_CATALOG_PRODUCT_SUPER_ATTRIBUTE_PRODUCT_ID_ATTRIBUTE_ID', query was: INSERT INTO `catalog_product_super_attribute` (`product_id`, `attribute_id`) VALUES (?, ?)
Hi,
I'm getting the above error when trying to add a configurable product to my 1.9.2 CE installation. I have checked the database and this isn't actually a duplicate entry. I've tried resetting all the catalog product tables, including auto increments but the error persists.
I have also tried clearing all caches, reindexing and disabling all third party modules (although none of these should be affecting the product saving).
The only mention of this error I can find online is due to people writing custom product save code, but this is using the core functionality.
Does anybody know how I can fix this please?
Many thanks

Magento New installation - Table 'eav_entity_type' already exists

I'm trying to install Magento 1.8, however I got stucked in configuration step.
I got the following message: 500 Internal Server Error
Looking log file I could verify the following:
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'eav_entity_type' already exists"
But, here is the problem because it is a new installation and this table does NOT exist.
My Products versions are: W32 (test environment) PHP 5.4 MySQL 5.6.14 Magento 1.8.1.0, IE 9 FF 25.0.1 Chrome 31.0.1650
Could you please help me? Thanks a lot.
Login to your database using phpMyAdmin and make sure there are no tables in there.
If there are, drop the user/table and re-create it anew and re-try the install wizard.
Just delete all tabels or re-create databbase, and start installation again.
Today I finally got it. I did a totally new installation on Debian amd64. I installed only LAMP softwares and probably the FastCGI was avoiding to get success. It is necessary to confirm this.

( ! ) Fatal error: Uncaught exception 'Exception Occured while migrating joomla 1.5 to 2.5

I'm trying to migrate my joomla website from 1.5.26 to 2.5. While migrating the joomla website through jupgrade extension, it is showing me "Migrating undefined". So, i've on the migration error in jupgrade extension then it shows me the following error which are related to the j25_users table.
Please have alook at the following error:-
( ! ) Fatal error: Uncaught exception 'Exception' with message 'Unknown column 'subscribe' in 'field list' SQL=INSERT INTO `j25_users` (`id`,`name`,`username`,`email`,`password`,`usertype`,`block`,`sendEmail`,`registerDate`,`lastvisitDate`,`activation`,`params`,`subscribe`) VALUES ('62','ChhathPoojaAdmin','admin','info#vivid-techno.com','36b6db909a7471b4e6fdf31b4eec641e:UELuOKlpIjy0jqPf36I8Kzj8uNElGBf9','Super Administrator','0','1','2010-06-27 16:18:02','2013-01-21 12:36:40','','{\"admin_language\":\"en-GB\",\"language\":\"en-GB\",\"editor\":\"xstandard\",\"helpsite\":\"\",\"timezone\":\"UTC\"}','1')' in C:\wamp\www\jdchhath\administrator\components\com_jupgrade\includes\jupgrade.class.php on line 347
Any Guess, how to solve it?
Upgrading your old joomla website to latest joomla version can be hectic as it could make you to feel so angry. The answer of my solution was that the subscribe column was not in the latest joomla version that makes it problem to upgrade my website to latest version. So i inserted myself the column table "subscribe" in my #__users table and please note that don't delete the old database tables which has been created by the jupgrde even if it is unsuccessful.That's it and you are done. If you are encounting any other problems related to database then first of all make sure that columns or tables are exist or not in your database. If jupgrade extensions creates any new database other than these tables jupgrade_categories,jupgrade_menus,jupgrade_modules,jupgrade_steps than don't delete it from my opinion.Just add the new columns or table in the newly created tables by jupgrade

Resources