Terms and Conditions missing StoreView, can't edit #6356
Assignees
Labels
Comments
|
Hi! Unfortunately I can't reproduce your problem. Have you tried clearing browser cache after deployment/install/update? Or if you have added/removed any of your stores/websites did you run reindex? |
|
I've deleted the browser cache and re-ran the indexer: It's a bit weird they all just run 00:00:00. After checking the backend I get a message In the debug.log I've found this: Any hints on this? I found this: https://community.magento.com/t5/Installing-Magento-2/Cache-invalidate/m-p/36269/highlight/true#M1368 referring to this saying it should be fixed with the/a next update: #4362 (comment) So indexing via cron is working but I'm getting an invalid cache when running the |
|
That is ok, indexer may invalidate cache. So, is your problem solved? |
|
The indexer problem is solved but the original problem with the missing columns and the error in the terms and conditions still exists. |
|
That is strange, can I get your db dump? |
|
Do you only need some specific tables or the complete dump? |
|
Just a quick note, got this when trying to import my dump on a different server:
Any ideas how this could happen and how to fix it? These are the first 100 lines of my dump: -- MySQL dump 10.13 Distrib 5.6.32, for Linux (x86_64)
--
-- Host: localhost Database: mg_gk_verpackungen
-- ------------------------------------------------------
-- Server version 5.6.32
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `admin_passwords`
--
DROP TABLE IF EXISTS `admin_passwords`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `admin_passwords` (
`password_id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Password Id',
`user_id` int(10) unsigned NOT NULL DEFAULT '0' COMMENT 'User Id',
`password_hash` varchar(100) DEFAULT NULL COMMENT 'Password Hash',
`expires` int(10) unsigned NOT NULL DEFAULT '0' COMMENT 'Expires',
`last_updated` int(10) unsigned NOT NULL DEFAULT '0' COMMENT 'Last Updated',
PRIMARY KEY (`password_id`),
KEY `ADMIN_PASSWORDS_USER_ID` (`user_id`),
CONSTRAINT `ADMIN_PASSWORDS_USER_ID_ADMIN_USER_USER_ID` FOREIGN KEY (`user_id`) REFERENCES `admin_user` (`user_id`) ON DELETE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=utf8 COMMENT='Admin Passwords';
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `admin_passwords`
--
LOCK TABLES `admin_passwords` WRITE;
/*!40000 ALTER TABLE `admin_passwords` DISABLE KEYS */;
INSERT INTO `admin_passwords` VALUES (1,1,'XXX:XXX:1',1476873775,1469097775),(2,1,'XXX:DDD:1',1476873788,1469097788),(3,2,'XXX:XXX:1',1477323885,1469547885),(4,3,'XXX:XXX:1',1477324022,1469548022),(5,3,'XXX:XXX:1',1477324199,1469548199),(6,2,'XXX:XXX:1',1477553927,1469777927),(7,2,'XXX:XXX:1',1477908334,1470132334),(8,2,'XXX:XXX:1',1478613455,1470837455),(9,2,'XXX:XXX:1',1478613485,1470837485),(10,1,'XXX:XXX:1',1479995480,1472219480);
/*!40000 ALTER TABLE `admin_passwords` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `admin_system_messages`
--
DROP TABLE IF EXISTS `admin_system_messages`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `admin_system_messages` (
`identity` varchar(100) NOT NULL COMMENT 'Message id',
`severity` smallint(5) unsigned NOT NULL DEFAULT '0' COMMENT 'Problem type',
`created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'Create date',
PRIMARY KEY (`identity`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Admin System Messages';
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `admin_system_messages`
--
LOCK TABLES `admin_system_messages` WRITE;
/*!40000 ALTER TABLE `admin_system_messages` DISABLE KEYS */;
/*!40000 ALTER TABLE `admin_system_messages` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `admin_user`
--
DROP TABLE IF EXISTS `admin_user`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `admin_user` (
`user_id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'User ID',
`firstname` varchar(32) DEFAULT NULL COMMENT 'User First Name',
`lastname` varchar(32) DEFAULT NULL COMMENT 'User Last Name',
`email` varchar(128) DEFAULT NULL COMMENT 'User Email',
`username` varchar(40) DEFAULT NULL COMMENT 'User Login',
`password` varchar(255) NOT NULL COMMENT 'User Password',
`created` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'User Created Time',
`modified` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'User Modified Time',
`logdate` timestamp NULL DEFAULT NULL COMMENT 'User Last Login Time',
`lognum` smallint(5) unsigned NOT NULL DEFAULT '0' COMMENT 'User Login Number',
`reload_acl_flag` smallint(6) NOT NULL DEFAULT '0' COMMENT 'Reload ACL',
`is_active` smallint(6) NOT NULL DEFAULT '1' COMMENT 'User Is Active',
`extra` text COMMENT 'User Extra Data',
`rp_token` text COMMENT 'Reset Password Link Token',
`rp_token_created_at` timestamp NULL DEFAULT NULL COMMENT 'Reset Password Link Token Creation Date',
`interface_locale` varchar(16) NOT NULL DEFAULT 'en_US' COMMENT 'Backend interface locale',
`failures_num` smallint(6) DEFAULT '0' COMMENT 'Failure Number',
`first_failure` timestamp NULL DEFAULT NULL COMMENT 'First Failure',
`lock_expires` timestamp NULL DEFAULT NULL COMMENT 'Expiration Lock Dates',
PRIMARY KEY (`user_id`),
UNIQUE KEY `ADMIN_USER_USERNAME` (`username`)
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8 COMMENT='Admin User Table';
/*!40101 SET character_set_client = @saved_cs_client */;
|
|
Hello @jwittorf |
|
This dump was indeed planned to go to a second development server with MySQL server 5.5.49 Can/should I send you a current dump from live via email or something like that? |
|
@jwittorf Magento will worked properly only with Mysql version 5.6.5 or higher |
|
Thanks for pointing that out in the comment before, I'll try it with a different server. Therefore this should not effect the initial problem, on the 5.6.* servers (as stated in the issue above) the problem still occurs. So you need a dump? |
|
@jwittorf have you external extensions installed? |
|
I've got:
They're installed on development, too but that installation is fine. |
|
We cant replicate your bug, maybe this bug appear due to your environment |
|
#6062 is not reproduced as well. Have you migrated your database from magento 1? What is your terms and condition content? Maybe it contains some special symbols? |
|
We are closing this issue because it hasn’t been updated in more than two weeks. If you can still reproduce this issue, please create a new GitHub issue report. |
|
Just as a heads up for everybody stumbling over this issue, seems to be related to #7822 Found this here: #7519 (comment)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm having troubles editing the terms and conditions on my production server. The development version is fine, I guess something went wrong during deployment/install/update.
The column "StoreViews" is missing in the list view of conditions on the production server. Additionally when adding a new condition I don't see the multi-select field to set a StoreView.
The database allthough has the same columns and entries.
It's the same issue as: #6062
I'm getting:
I've checked the ouput and added this before the
return:I actually got back an
array(1) { [0]=> string(1) "0" }There seem to be no problems with the frontend but I and/or my client can't edit the agreements in the backend.
Preconditions
Steps to reproduce
Expected result
1 List view
2 Add new condition
3 Edit existing condition
Actual result
1 List view
2 Add new condition
3 Edit existing condition
The text was updated successfully, but these errors were encountered: