problem in fresh install dataBase

[spiriralph]

Dear Sir

I install a fresh CMSMS ver 1.11.7
PHP Version 5.3.13
MySQL server version: 5.0.91
Server API CGI/FastCGI & Apache/2

after installing I go to PhpMyAdmin
select all tables and select check table
all tables are Ok but recieve this message:

Problems with indexes of table `cms_content`
PRIMARY and INDEX keys should not both be set for column `content_id`
Problems with indexes of table `cms_events`
PRIMARY and INDEX keys should not both be set for column `event_id`
Problems with indexes of table `cms_modules`
PRIMARY and INDEX keys should not both be set for column `module_name`
Problems with indexes of table `cms_module_news`
More than one INDEX key was created for column `start_time`
Problems with indexes of table `cms_module_search_items`
More than one INDEX key was created for column `module_name`
Problems with indexes of table `cms_userprefs`
PRIMARY and INDEX keys should not both be set for column `user_id`

what is the problem in new fresh installing of CMSMS 1.11.7 & what I must do with this problem?
with best regards

[Jo Morg]

I tried to reproduce it and all the tables passed the test without warnings.
In my tests
MySQL: 5.5.27;
PHP: 5.4.7;
CMSMS: recent full install CMS Made Simple™ 1.11.7 “Genovesa”;

I'm not sure if it may be related to your MySQL version but I would assume not. CMSMS should be working fine on any MySQL 5.x version, if I'm not mistaken.

If you could provide more data it might be easier to pinpoint the problem.

In the mean time try a checksum of your installation and see if there are errors, and check for any yellow or red warnings on your system information.
HTH

[spiriralph]

I DownLoad a new files
cmsmadesimple-1.11.7-full.tar.gz
cmsmadesimple-1.11.7-full-checksum.dat
from http://www.cmsmadesimple.org/downloads/

and upload them to my web site

Perform Validation give me this errors:
463 Files failed md5sum check:

[Jo Morg]

and upload them to my web site

And how did you do that? Via ftp?
If so there is a chance that some file got corrupted during upload.
Nevertheless try to use the tips of this section.
If at all possible you should try going via CPanel, it is more reliable.
HTH

[spiriralph]

thank you
there is FTP problem WinSCP

but after checking checkSum

I try to instal the CMS MS 1.11.7 ("no installing sample content and templates") and I receive the same problem with tables when try to check data base

Problems with indexes of table `cms_content`
PRIMARY and INDEX keys should not both be set for column `content_id`
Problems with indexes of table `cms_events`
PRIMARY and INDEX keys should not both be set for column `event_id`
Problems with indexes of table `cms_modules`
PRIMARY and INDEX keys should not both be set for column `module_name`
Problems with indexes of table `cms_module_news`
More than one INDEX key was created for column `start_time`
Problems with indexes of table `cms_module_search_items`
More than one INDEX key was created for column `module_name`
Problems with indexes of table `cms_userprefs`
PRIMARY and INDEX keys should not both be set for column `user_id`

[Jo Morg]

If you could provide more data it might be easier to pinpoint the problem.

In the mean time try a checksum of your installation and see if there are errors, and check for any yellow or red warnings on your system information.
HTH

You still didn't check and pasted here your system information...
I suspect that there might be a misconfiguration on your server MySQL server, MySQL database, and or tables. I just tested another, different CMSMS install, with the same configuration as I posted before... still no errors, no warnings. You should also try to contact your hoster, as it seams that the error seems atypical...

On a side note: did you actually delete the database that was originally causing the troubles? Did you try to create a new one?

[spiriralph]

yes I delete the DB deletr files in sub folder and extract tar from server to sub folder and run install.php check check sum and finished installing? go to phpmyadmin select all tables -> "chek table" find problems select all tables optimize all ok then check all tables -> "check table" the problems are there

CMS Version 1.11.7
CMSMailer 5.2.1
CMSPrinting 1.0.4
FileManager 1.4.3
MenuManager 1.8.5
MicroTiny 1.2.5
ModuleManager 1.5.5
News 2.12.12
Search 1.7.8
ThemeManager 1.1.8
php_memory_limit
process_whole_template
max_upload_size 20000000
url_rewriting none
page_extension
query_var magus
image_manipulation_prog GD
auto_alias_content true
locale
default_encoding utf-8
admin_encoding utf-8
set_names true
debug false
timezone Europe/Moscow
set_names true
set_names

Current PHP Version (phpversion) 5.3.13
md5 function (md5_function) On (True)
GD version (gd_version) 2
tempnam function (tempnam_function) On (True)
Magic quotes in runtime (magic_quotes_runtime) Off (False)
Is E_STRICT disabled in error_reporting (E_STRICT)
Is E_DEPRECATED disabled in error_reporting (E_DEPRECATED)
PHP Effective Memory Limit (memory_limit) 32M
Maximum Execution Time (max_execution_time) 120
PHP output_buffering (output_buffering) On
PHP Safe Mode (safe_mode) Off (False)
File uploads (file_uploads) On (True)
Maximum Post Size (post_max_size) 20M
Maximum Upload Size (upload_max_filesize) 20M

Server API (server_api) cgi-fcgi
Server Database (server_db_type) mysql (mysqli)
Server Database Version (server_db_version) 5.0.91
Check database access levels (server_db_grants) found a "grant all" statement that appears to be suitable
Server Software (server_software) apache/2
Server Operating System (server_os) linux 3.2.44 on x86_64
Timezone Offset (tz_offset) 0

[spiriralph]

which KEY is not correct? what must be the original

CREATE TABLE `cms_content` (
`content_id` int(11) NOT NULL,
`content_name` varchar(255) default NULL,
`type` varchar(25) default NULL,
`owner_id` int(11) default NULL,
`parent_id` int(11) default NULL,
`template_id` int(11) default NULL,
`item_order` int(11) default NULL,
`hierarchy` varchar(255) default NULL,
`default_content` tinyint(4) default NULL,
`menu_text` varchar(255) default NULL,
`content_alias` varchar(255) default NULL,
`show_in_menu` tinyint(4) default NULL,
`collapsed` tinyint(4) default NULL,
`markup` varchar(25) default NULL,
`active` tinyint(4) default NULL,
`cachable` tinyint(4) default NULL,
`id_hierarchy` varchar(255) default NULL,
`hierarchy_path` text,
`prop_names` text,
`metadata` text,
`titleattribute` varchar(255) default NULL,
`tabindex` varchar(10) default NULL,
`accesskey` varchar(5) default NULL,
`last_modified_by` int(11) default NULL,
`create_date` datetime default NULL,
`modified_date` datetime default NULL,
`secure` tinyint(4) default NULL,
`page_url` varchar(255) default NULL,
PRIMARY KEY (`content_id`),
KEY `cms_index_content_by_content_alias_active` (`content_alias`,`active`),
KEY `cms_index_content_by_default_content` (`default_content`),
KEY `cms_index_content_by_parent_id` (`parent_id`),
KEY `cms_index_content_by_hierarchy` (`hierarchy`),
KEY `cms_index_content_by_idhier` (`content_id`,`hierarchy`)
) TYPE=MyISAM;
KEY `cms_index_content_by_idhier is not correct?

CREATE TABLE `cms_userprefs` (
`user_id` int(11) NOT NULL,
`preference` varchar(50) NOT NULL,
`value` text,
`type` varchar(25) default NULL,
PRIMARY KEY (`user_id`,`preference`),
KEY `cms_index_userprefs_by_user_id` (`user_id`)
) TYPE=MyISAM;
PRIMARY KEY is not correct?

[Dr.CSS]

May I ask why you are checking the DB? does CMSMS not install, do you have errors on front end/backend, or .......?

[Jo Morg]

I still think you should try to contact your hoster, as it seams that the error seems atypical. I also did a search on this forum and there was only one old report about a similar issue, but that apparently did not affect the use of CMSMS.
It is NOT Recommended that you modify any core files as you loose support by the core developers...

[spiriralph]

I don't know how to explane them (Hosters) about this Problems with DB index primery key

yes have a problem with my previouse site, the DB crashes and I don't know what I must to do and try to find the reason of crash. so I try install a new fresh one. but i find this problems with tables!!!!

errors like this:
20130803T033950: dommaga.ru/index.php
PHP Fatal error: Attempt to connect to database gadanij_maga on dommaga@edelveiysru.ipagemysql.com failed in /hermes/bosoraweb032/b524/ipg.edelveiysru/dommaga/lib/adodb.functions.php on line 61

they can't help me and saying that CMS creates to many connection with DB and so on ....

[Jo Morg]

I just confirmed that the message is related to PhpMyAdmin, and doesn't affect CMSMS regular use.

yes have a problem with my previouse site, the DB crashes and I don't know what I must to do and try to find the reason of crash. so I try install a new fresh one.

This is an entirely different question. You can open a new topic, about that and provide as much info as possible.

[spiriralph]

Dear Sir
to solve my problem with my DB, MySql server & Tables
first I install an Empty Fresh CMS MS
check is there any problems
yes there is problems with tables
I asked how can I solve this Problems
You asked me
but problems are there
the PRIMARY KEY is not correct in ' cms_userprefs' table?
or KEY `cms_index_content_by_idhier' from _content table?
and so on...
may be I delete THIS Keys from DB and others

No one wants to hack the core source code

Problems with indexes of table `cms_content`
PRIMARY and INDEX keys should not both be set for column `content_id`
Problems with indexes of table `cms_events`
PRIMARY and INDEX keys should not both be set for column `event_id`
Problems with indexes of table `cms_modules`
PRIMARY and INDEX keys should not both be set for column `module_name`
Problems with indexes of table `cms_module_news`
More than one INDEX key was created for column `start_time`
Problems with indexes of table `cms_module_search_items`
More than one INDEX key was created for column `module_name`
Problems with indexes of table `cms_userprefs`
PRIMARY and INDEX keys should not both be set for column `user_id`

second I will install contents
.....

after All if I recieve in the future DB connection error or overload I creates a new post for that error