I would need to downgrade back to 7.8.x from 7.9.0. The SuiteP-style is just too BIG, so i want to get back to the previous version with the more compact styles.
I screwed upp my db-backup, but i have a copy of all files. What i wanted to doublecheck is that has there been any changes to the db-structure? I’m trying to do a check in the differences between tags v7.8.4 and v7.9.0, but incase i miss it i would appreciate if someone would have an ansver 
When you say you have a backup of “all files”, is that all files on the server, or all SuiteCRM files? Because the DB is also stored in files on the server, you could recover from that.
If not, then I would say there are database differences in 7.9.0 for sure, things were added related to emails. I’m not sure if anything was removed; I mean, if you’re lucky the old system is still there. I read something about this, but I’m not 100% sure if it will work in a downgrade.
A downgrade like you’re trying to achieve is a difficult and risky operation… I wish you good luck, but I’m afraid you will find it difficult.
There are posts around these forums explaining how to reduce spacing in SuiteP. And you can change the colors by editing SASS and recompiling CSS.
I mean that i have backed up the suitecrm-files, not the mysql-db.
I got it solved out. I installed a new test-db with the previous version i was running, and from this i did a diff from the schema. The changes are not big, a couple of new fields, extending field’s lenghts and a new table. This will be easy to change and delete, so i’ll go back to the previous.
I will possibly upgrade again, but not now. I simply don’t like the SuiteP look.
Is there a sql script that could be shared so those who want to downgrade till all the stuff gets worked out?
7.9 not terribly useful in the present form.
Here is the diff of the schema between 7.8.3 and 7.9.0
--- suitecrm_7.8.3.sql 2017-06-02 19:18:07.000000000 +0300
+++ suitecrm_7.9.0.sql 2017-06-02 19:18:17.000000000 +0300
@@ -23,7 +23,7 @@
`deleted` tinyint(1) DEFAULT '0',
`assigned_user_id` char(36) DEFAULT NULL,
`account_type` varchar(50) DEFAULT NULL,
- `industry` varchar(50) DEFAULT NULL,
+ `industry` varchar(100) DEFAULT NULL,
`annual_revenue` varchar(100) DEFAULT NULL,
`phone_fax` varchar(100) DEFAULT NULL,
`billing_address_street` varchar(150) DEFAULT NULL,
@@ -817,6 +817,14 @@
KEY `idx_aos_contracts_parent_id` (`parent_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;
+DROP TABLE IF EXISTS `aos_contracts_cstm`;
+/*!40101 SET @saved_cs_client = @@character_set_client */;
+/*!40101 SET character_set_client = utf8 */;
+CREATE TABLE `aos_contracts_cstm` (
+ `id_c` char(36) NOT NULL,
+ PRIMARY KEY (`id_c`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+/*!40101 SET character_set_client = @saved_cs_client */;
DROP TABLE IF EXISTS `aos_contracts_documents`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
@@ -1676,7 +1684,7 @@
KEY `idx_case_name` (`name`),
KEY `idx_account_id` (`account_id`),
KEY `idx_cases_stat_del` (`assigned_user_id`,`status`,`deleted`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;
DROP TABLE IF EXISTS `cases_audit`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
@@ -1823,6 +1831,16 @@
KEY `idx_contacts_cases` (`contact_id`,`case_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;
+DROP TABLE IF EXISTS `contacts_cstm`;
+/*!40101 SET @saved_cs_client = @@character_set_client */;
+/*!40101 SET character_set_client = utf8 */;
+CREATE TABLE `contacts_cstm` (
+ `id_c` char(36) NOT NULL,
+ `company_c` varchar(255) DEFAULT NULL,
+ `contactlanguage_c` text,
+ PRIMARY KEY (`id_c`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+/*!40101 SET character_set_client = @saved_cs_client */;
DROP TABLE IF EXISTS `contacts_users`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
@@ -2209,11 +2227,16 @@
`mailbox_id` char(36) DEFAULT NULL,
`parent_type` varchar(100) DEFAULT NULL,
`parent_id` char(36) DEFAULT NULL,
+ `orphaned` tinyint(1) DEFAULT '0',
+ `last_synced` datetime DEFAULT NULL,
+ `uid` varchar(255) DEFAULT NULL,
+ `category_id` varchar(100) DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `idx_email_name` (`name`),
KEY `idx_message_id` (`message_id`),
KEY `idx_email_parent_id` (`parent_id`),
- KEY `idx_email_assigned` (`assigned_user_id`,`type`,`status`)
+ KEY `idx_email_assigned` (`assigned_user_id`,`type`,`status`),
+ KEY `idx_email_cat` (`category_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;
DROP TABLE IF EXISTS `emails_beans`;
@@ -2317,7 +2340,7 @@
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `folders` (
`id` char(36) NOT NULL,
- `name` varchar(25) DEFAULT NULL,
+ `name` varchar(255) DEFAULT NULL,
`folder_type` varchar(25) DEFAULT NULL,
`parent_folder` char(36) DEFAULT NULL,
`has_child` tinyint(1) DEFAULT '0',
@@ -3866,7 +3889,7 @@
KEY `idx_tracker_userid_itemid_vis` (`user_id`,`item_id`,`visible`),
KEY `idx_tracker_monitor_id` (`monitor_id`),
KEY `idx_tracker_date_modified` (`date_modified`)
-) ENGINE=InnoDB AUTO_INCREMENT=38 DEFAULT CHARSET=utf8;
+) ENGINE=InnoDB AUTO_INCREMENT=538 DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;
DROP TABLE IF EXISTS `upgrade_history`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
To me it looks that it’s just to recover the suitecrm-directory with your 7.8.x backup. The difference is some longer fields, a new table, and these two changes:
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;-) ENGINE=InnoDB AUTO_INCREMENT=38 DEFAULT CHARSET=utf8;
+) ENGINE=InnoDB AUTO_INCREMENT=538 DEFAULT CHARSET=utf8;So these should be editable with eg PhpMyadmin or similar…
If there is something else that might break, then i would apreciate some hints on what to check
You can check the upgrade scripts inside the upgrade package from 7.8.3 to 7.9, and see what else it’s doing.
This is all very risky territory…
yeah - I don’t think I would give it a shot. I’ve added a bunch of content since the upgrade, although I’ll have to let it rest till an update comes out.
Yes, us early adopters are finding this out.
The email client doesn’t even have the ability to reply or forward messages let alone the issues with Suite-P…
It appears to me the Suote-P was a hasty decision to move to a Bootstrap frontend framework which ended up breaking a few things including the ability through layout def files to change the number of columns in the view so you could move from the 1980’s 800x600 screen resolution 2-column format into an interface layout that was more closer to the 21st century.
Here’s my suggestions… First, make a copy of your entire system before upgrading and test test test before you upgrade your production system.
Second, at the bottom of the page download the modified theme. Sales Agility should actually just adopt these changes as the stock theme in my opinion. This helps somewhat with making the interface so so bloated. I’ve also been able to modify the CSS file to have 4 columns instead of 2 in the detail view but it creates issues in the edit view so I may just have to live with 2-columns for consistency.
The Suote-P Theme is a very curious decision to me. It is like someone in the development team is obsessed with making the interface appear “newer” with the Bootstrap look at the expense of a less efficient UI layout. Many of us are very disappointed just like you. This UI is excellent for an 8" tablet as opposed to a 24" desktop monitor, it’s a joke. I’m sure improvements will be made and we just need to be patient. But I would have greatly preferred the new version was backward compatible with Suite-R theme which we tweaked very well.