EZP-24566: Add "Rich Text" field to Almighty content type in demo bundle #174
Conversation
|
clash82
force-pushed
the
almighty-richtext
branch
from
b32dace
to
f343b91
Compare
|
clash82
changed the title
|
@clash82 Difficult rebase on this one? :) ping me on when you think this can be done considering your agenda with @SylvainGuittard. Just need to know as I plan to add a tag after this is in. |
clash82
force-pushed
the
almighty-richtext
branch
from
f343b91
to
e0eae55
Compare
|
|
@andrerom sorry for that. I had some problems with my eZ installation :) This task was not so easy due to |
clash82
force-pushed
the
almighty-richtext
branch
from
e0eae55
to
31301fd
Compare
|
clash82
changed the title
|
ping @andrerom |
| @@ -608,7 +609,6 @@ INSERT INTO `ezcontentclass_classgroup` VALUES (37,0,3,'Media'); | |||
| INSERT INTO `ezcontentclass_classgroup` VALUES (38,0,1,'Content'); | |||
| INSERT INTO `ezcontentclass_classgroup` VALUES (39,0,1,'Content'); | |||
| INSERT INTO `ezcontentclass_classgroup` VALUES (40,0,1,'Content'); | |||
| INSERT INTO `ezcontentclass_classgroup` VALUES (40,1,1,'Content'); | |||
There was a problem hiding this comment.
should not be here I think
There was a problem hiding this comment.
From what I understand is that second insert value here:
INSERT INTO `ezcontentclass_classgroup` VALUES (40,1,1,'Content');is contentclass_version and since eZ Publish decided to remove unused version (draft?) it's ok. I'm not so familiar with content structure, can someone confirm this?
There was a problem hiding this comment.
You are right, this one is ok.
clash82
force-pushed
the
almighty-richtext
branch
from
31301fd
to
4715352
Compare
|
|
+1, ping @bdunogier / @pspanja |
|
+1 |
EZP-24566: Add "Rich Text" field to Almighty content type in demo bundle
Link to Jira task: https://jira.ez.no/browse/EZP-24566