Will add the tinyMCE in the next release (next week) to the CMP-Version.
Need it myself for a project now.
It isn't working at the moment.
That would be really awesome. There seem to be a few differences between the CMP version and the TV version which I wasn't aware of. Actually, I didn't even realize there was a distinction. Any chance you could clarify these differences in the docs?
Should I be considering having two configs to manage each table, a TV version and a CMP version?
there are not much differences between the TV or the CMP-Version.
They use both the same code.
For the CMP-Version, of course, there is some additional code necessary.
And there are some additional config-options.
tinymce doesn't work there, because its actually not loaded and not initialised on the CMP-page.
The TV-Version can, but must not, have relations to the resource, where it sits.
The CMP-Version on the first level, hasn't a Resource to be related to, but can also be related to resources. Managable by a dropdown-TV and a dropdown-filter-box for example.
On the second and deeper level it can have relations to the upper MIGX-TV-tables.
Another question on MIGXdb. I followed the Doodles tutorial and now have a working custom table with custom manager page. Great!
Now I'm wondering if I could somehow connect the doodles with Quip, to enable commenting on each doodle and to view the comments in the grid on the CMP. Would this be possible?
not sure, if quip is that flexible and can connected not only to resources, but also to custom-table-records.
If it is, then it would be possible to show the joined quip-comments in another MIGXdb grid, which would be a MIGXdb-TV for a virtual db-field, when you open the editor window.
-
☆ A M B ☆
- 326 Posts
I'm using MIGXdb with great success in a project, but am having some trouble getting TinyMCE to work. I can get TinyMCE to show up, but when I save, it's not actually saving the content to the database. I've tried the following scenarios:
1. Not setting an Input TV Type or Input TV (so just a plain text field), there's obviously no TinyMCE, but it saves data fine. This was my baseline test.
2. Setting the field's Input TV Type to "richtext-tv" but leaving Input TV blank does not load TinyMCE, but the data does save.
3. Setting the field's Input TV to the name of a TV with "Rich Text" as its input type, but leaving Input TV Type blank, loads TinyMCE, but data doesn't save.
4. Setting both the Input TV (as in #3) and Input TV Type (as in #2) loads TinyMCE, but data doesn't save.
Am I missing something obvious? Maybe just a misconfiguration somewhere?
you can use the joins-configuration
if you have an aggregate or composite - alias for the joined table in your xpdo-schema you can use:
joins:
if you don't have a relation defined in your schema you can use:
joins:
[{"classname":"YourClassname","alias":"yourAlias","on":"yourAlias.id=yourRelationIDfield"}]
then you can use for example: yourAlias_title as fieldnames in your grid