Content management as it is meant to be
https://forum.cmsmadesimple.org/
Yes, you're correct from what I see, I think it was probably a bug introduced a while back or something. The modified date works well, so it's probably a one line fix..... either way this is a minor bug.Wiedmann wrote: Hi,
from what I see, there will be nothing written to the column "create_date" in the table "content_props" if I add a new page/block. Is there a reason for this?
Regards,
Carsten
CMS Made Simple 1.2.4
If you look at the adodb data dictionary documentation, indicates that that is telling the databaase library what type of table to create. I don't think adodb_lite supports this, and enforces only MyISAM, but the full adodb does.creation from new tables:
What's the reason for "$taboptarray = array('mysql' => 'TYPE=MyISAM');" in "schema.php" or module installations? (Of course, with my setup this have no effect...)
This seems to work fine for me:"module_templates":
in the table "module_templates" you want have an index over 2 columns. Is this index necessary for you? Because this index can't be created on all installations, and your setup script have no knowledge about this situation (instead it writes: DONE and all success).
Code: Select all
mysql> show create table cms_module_templates;
+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create Table |
+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| cms_module_templates | CREATE TABLE `cms_module_templates` (
`module_name` varchar(200) default NULL,
`template_name` varchar(200) default NULL,
`content` text,
`create_date` datetime default NULL,
`modified_date` datetime default NULL,
KEY `module_name` (`module_name`,`template_name`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 |
+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.03 sec)This happens just after each fresh installatin with sample data.Yes, it should be the highest number from the content_props.content_id something must be a little messed up in your installation.
I know... adodb_lite supports this too. Let me ask in other words: Why want you have MyISAM? Add the moment this as also 2 other issues:If you look at the adodb data dictionary documentation, indicates that that is telling the databaase library what type of table to create.
For you... Well, not all people on the world are using latin1 as charset for the server. If someone is using utf8 as default charset the index can't be created, because the (resulting) index length is to long.This seems to work fine for me:
Well, the fix is easy:Yes, it should be the highest number from the content_props.content_id something must be a little messed up in your installation.
Well, after looking through the code (BTW: I love well documented code...):The modified date works well, so it's probably a one line fix.....