BTW. This is OC
v.1.5.x here! I just hope, you are in no hurry !?
.....
You could remove all not used Languages, in all the sections, where whole bunches of languages are part of, in the INSTALL-, and Javascript- Subsections, usually, and do the same with all those Language PIC's, never used.
-
Then, remove unused Content, related to COUNTRIES, ZONES, Languages, and currencies, from your INSTALL DB, like:
Code: Select all
(1, 'Afghanistan', 'AF', 'AFG', '', 0, 1),
(2, 'Albania', 'AL', 'ALB', '', 0, 1),
(3, 'Algeria', 'DZ', 'DZA', '', 0, 1),
(4, 'American Samoa', 'AS', 'ASM', '', 0, 1),
(5, 'Andorra', 'AD', 'AND', '', 0, 1),
e.t.c.
Code: Select all
(1, 1, 'Badakhshan', 'BDS', 1),
(2, 1, 'Badghis', 'BDG', 1),
(3, 1, 'Baghlan', 'BGL', 1),
(4, 1, 'Balkh', 'BAL', 1),
(5, 1, 'Bamian', 'BAM', 1),
e.t.c.
possibly also some of this Section:
Code: Select all
INSERT INTO `oc_zone_to_geo_zone` (`zone_to_geo_zone_id`, `country_id`, `zone_id`, `geo_zone_id`, `date_added`, `date_modified`) VALUES
(1, 222, 0, 4, '0000-00-00 00:00:00', '0000-00-00 00:00:00'),
(2, 222, 3513, 3, '0000-00-00 00:00:00', '0000-00-00 00:00:00'),
(3, 222, 3514, 3, '0000-00-00 00:00:00', '0000-00-00 00:00:00'),
(4, 222, 3515, 3, '0000-00-00 00:00:00', '0000-00-00 00:00:00'),
(5, 222, 3516, 3, '0000-00-00 00:00:00', '0000-00-00 00:00:00'),
e.t.c.
JUST LEAVE your Country, Zone, and Language files, by USE of their DEFAULT ID-Numbers, i.E:
Code: Select all
(204, 'Switzerland', 'CH', 'CHE', '', 0, 1),
plus:
Code: Select all
(3095, 204, 'Aargau', 'AG', 1),
(3096, 204, 'Appenzell Ausserrhoden', 'AR', 1),
(3097, 204, 'Appenzell Innerrhoden', 'AI', 1),
(3098, 204, 'Basel-Stadt', 'BS', 1),
(3099, 204, 'Basel-Landschaft', 'BL', 1),
(3100, 204, 'Bern', 'BE', 1),$
e.t.c.
Technically at least. the only remaining problem would be, that the installation routine already contains some Sample- Data, on Products, Countries, Currencies, e.t.c., probably resulting in an install Conflict, if some values do not longer exist, required to finish a working Installation.
I would therefore start, by cleaning out an existing DB, on a server, by use of the MySql-Admin, from Products, Countries, Zones, and so on, then, download it's content, then, change an Install DB, to reflect/match the Content, really used, and so, it would 'shrink' a new DB by about 2'500 never ever used Content-Lines, just standing in the way of others, trying to do an efficient Job. But this would be some work to do, in any case!
Some Extensions exist already, to clean OUT all Demo Data from a running Shop!
But they do NOT Remove any DB-PRESETS, Countries, Zones, e.t.c., like mentioned above, from a DB.
When it comes to FONTAWESOME, (it's heavy on load, and data!) you could 'externalize' it in full, to be called, when used, from another Site. This would also save some Space, and Workload, and later, if everything works, you may work a little on your Header.tpl Linking, and in other Sections, partly by Use of VqMods, to cookie-free externally http-link you Scripts, Stylesheets, and Images. This would then power up the overall Performance to the Peak.
When it comes to unused Payment / Shipping Extensions, most could be removed, from the Theme-, Controller-, Model-, and Language- Subsections, with the Exeption of possibly Amazon and Authorize.net related Stuff. Also, that OpenBay/Ebay Stuff should better not be touched, for some reasons, still unfamiliar to me.
But all this
should NEVER be tried by a Coder/DB-NEWBIE, for those, it's much easier to install an OC in the regular way, and later CLEAN OUT a DB, from unused Products, Countries, Zones, e.t.c., by removing those, selectivly, from a Running Shop.
Just, at first, always create a full OC-BACKUP, including the DB, otherways, one possibly has to start from scratch again, if something breaks...
And better DO NOT ADD any Mod's, or Themes, anything, before a Cleanout has been done successfully.
And later, check every single Extension, and/or Theme, if it does include anything, just beeing carried as Ballast again, before blindly upload such Extensions to the Server.
To give you some ideas on this...
But it all would make little sense, if you later upload 1+MB Images, they will kill any attempt, to have an efficient Shop.
Ernie